neuron-technologies/neuron
3
0
Fork 0
Code Issues 44 Pull Requests 7 Actions Packages Projects Releases Wiki Activity

soul: graph API depth=1 caps the neighbor list (~11 bare / ~24 observed) and tag edges crowd out identity edges — inspection hides real wiring #88

New Issue
Open
opened 2026-07-18 19:55:06 +00:00 by tim.lingo · 1 comment
tim.lingo commented 2026-07-18 19:55:06 +00:00
Member
Copy Link
Copy Source

Found 2026-07-18. GET /api/neuron/graph?id=&depth=1 on the values hub returned only tag edges + 1 identity edge while the snapshot held 97 hub edges (13 of them hub↔Value identity wiring). The response appears capped and ordered so 'tagged' edges fill the budget before identity/canonical edges.

Impact: any client inspecting the graph (MCP inspectGraph, session boot identity checks) concludes wiring is missing when it exists — this contributed to a false '8/13 values' diagnosis during the split-brain audit. Suggest: raise/paginate the cap, or rank identity/canonical relations above 'tagged', or accept a relation filter param.

Workaround in place: our vitals script counts wiring from the snapshot file, not this endpoint.

Found 2026-07-18. GET /api/neuron/graph?id=<hub>&depth=1 on the values hub returned only tag edges + 1 identity edge while the snapshot held 97 hub edges (13 of them hub↔Value identity wiring). The response appears capped and ordered so 'tagged' edges fill the budget before identity/canonical edges. Impact: any client inspecting the graph (MCP inspectGraph, session boot identity checks) concludes wiring is missing when it exists — this contributed to a false '8/13 values' diagnosis during the split-brain audit. Suggest: raise/paginate the cap, or rank identity/canonical relations above 'tagged', or accept a relation filter param. Workaround in place: our vitals script counts wiring from the snapshot file, not this endpoint.
will.anderson commented 2026-08-03 19:07:59 +00:00
Owner
Copy Link
Copy Source

GROOMING — 2026-08-03
Status: Open — graph API depth=1 caps the neighbor list and lets tag edges crowd out identity/canonical edges, so inspection under-reports real wiring (contributed to a false 8/13-values diagnosis); a snapshot-file workaround is in place.
Next action: Will to raise/paginate the cap or rank identity/canonical edges above tagged (or add a relation-filter param).
Owner: Will
Priority: POST-BETA

**GROOMING — 2026-08-03** **Status:** Open — graph API depth=1 caps the neighbor list and lets tag edges crowd out identity/canonical edges, so inspection under-reports real wiring (contributed to a false 8/13-values diagnosis); a snapshot-file workaround is in place. **Next action:** Will to raise/paginate the cap or rank identity/canonical edges above tagged (or add a relation-filter param). **Owner:** Will **Priority:** POST-BETA
will.anderson added the POST-BETA label 2026-08-03 19:08:01 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
BETA-CRITICAL
On the beta critical path — must resolve before ship
 blocks-public-beta
Must be fixed before any public beta
 HELD
Blocked pending an external decision (counsel / dual sign-off)
 ORTHOGONAL
Parallel workstream (testing/hardening) — safe to assign off critical path
 P0
Drop-everything severity
 POST-BETA
Important but not blocking the beta ship
 security
Security vulnerability
No labels POST-BETA
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
andre.almeida (Andre Almeida) tim.lingo (Tim Lingo) will.anderson (Will Anderson)
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: neuron-technologies/neuron#88
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?