engram: expose the geometry so the frame can be verified #156

2026-08-16T20:37:29Z

will.anderson commented

2026-08-16 20:37:29 +00:00

engram_scan_nodes_emb_json has existed as a builtin with no route. The embeddings — the actual positions every distance, angle, membership and grounding is computed from — were unreadable from outside the process.

That is not a missing convenience. Every claim about the coordinate frame was unfalsifiable from the API: whether the space is isotropic, where the centering offset sits, what the origin is, whether a node carries geometry at all. You cannot verify a coordinate system you cannot see — and a frame that cannot be checked is precisely the shape this codebase spent 2026-08-16 removing everywhere else.

GET /api/nodes/emb?limit=&offset= — read-only, paged, no writes.

Measured consequence of having it: the value manifold and the love-component manifold were both decomposed and null-controlled against random node sets from the same graph, and several published claims were retracted because the geometry contradicted them — a reported flat variance spectrum that was 2× uniform, and a pairwise cosine offered as evidence that turned out to be the identity −1/(n−1). None of that was checkable before this route existed.

`engram_scan_nodes_emb_json` has existed as a builtin with **no route**. The embeddings — the actual positions every distance, angle, membership and grounding is computed from — were unreadable from outside the process. That is not a missing convenience. **Every claim about the coordinate frame was unfalsifiable from the API**: whether the space is isotropic, where the centering offset sits, what the origin is, whether a node carries geometry at all. You cannot verify a coordinate system you cannot see — and a frame that cannot be checked is precisely the shape this codebase spent 2026-08-16 removing everywhere else. `GET /api/nodes/emb?limit=&offset=` — read-only, paged, no writes. **Measured consequence of having it:** the value manifold and the love-component manifold were both decomposed and null-controlled against random node sets from the same graph, and several published claims were retracted because the geometry contradicted them — a reported flat variance spectrum that was 2× uniform, and a pairwise cosine offered as evidence that turned out to be the identity −1/(n−1). None of that was checkable before this route existed.

will.anderson added 1 commit 2026-08-16 20:37:32 +00:00

engram: expose the geometry so the frame can be verified

El SDK CI - dev / build-and-test (pull_request) Failing after 11m29s

Details

0389bf9363

engram_scan_nodes_emb_json has existed as a builtin with NO ROUTE. The
embeddings — the actual positions every distance, angle, membership and
grounding is computed from — were unreadable from outside the process.

That is not a missing convenience. It means every claim about the
coordinate frame was unfalsifiable from the API: whether the space is
isotropic, where the centering offset sits, what the origin is, whether a
node carries geometry at all. You cannot verify a coordinate system you
cannot see, and a system whose frame cannot be checked is exactly the
shape this codebase spent 2026-08-16 removing everywhere else.

GET /api/nodes/emb?limit=&offset=. Read-only, paged, no writes.

Measured consequence of having it: the value manifold and the love
component manifold were both decomposed, null-controlled against random
node sets drawn from the same graph, and several published claims were
retracted because the geometry contradicted them. None of that was
possible before this route existed.

will.anderson merged commit 9526bda507 into dev

2026-08-16 20:49:09 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: neuron-technologies/el#156