neuron-technologies/neuron
2
0
Fork 0
Code Issues 11 Pull Requests 5 Actions Packages Projects Releases Wiki Activity

node/create ignores node_type — in-app Artifacts/Backlog writes land as Memory and vanish #69

New Issue
Open
opened 2026-07-03 18:18:13 +00:00 by tim.lingo · 0 comments
tim.lingo commented 2026-07-03 18:18:13 +00:00
Member
Copy Link
Copy Source

/api/neuron/node/create ignores node_type — typed writes land as "Memory" (Artifacts/Backlog created in-app vanish)

Repro (container soul, 2026-07-03):

POST /api/neuron/node/create {"content":"probe","node_type":"Artifact","label":"PROBE-ARTIFACT-S4","tags":["Artifact"]}
→ {"id":"...","ok":true}
GET /api/graph/nodes → the node exists with node_type: "Memory"

Impact: the app's typed-node writes (SoulWrites.createArtifact / createBacklogItem / updateArtifact — all on node/create|update) are confirmed ok:true but land as Memory. The Artifacts view filters node_type == "Artifact" → user creates an artifact, hits Save, it never appears (user-reported today). Backlog create likely identical; artifact UPDATE recreates the node, so editing an existing artifact probably re-types it to Memory and vanishes it from the list.

Ask: node/create + node/update should persist the client-provided node_type (and ideally the metadata fields the read path expects — see the round-trip caveat comment in the app's SoulWrites.kt). Related: #68 durability, T-BACKLOG #59 typed-write gap.

Product note: we're replacing the client's blank-form "New artifact" with a draft-with-Neuron chat flow regardless (artifacts should be born from work, not empty forms) — but Backlog create and artifact EDIT still need this route fixed.

Filed by Neuron (Tim's build terminal) with live probe evidence.

## /api/neuron/node/create ignores node_type — typed writes land as "Memory" (Artifacts/Backlog created in-app vanish) **Repro (container soul, 2026-07-03):** ``` POST /api/neuron/node/create {"content":"probe","node_type":"Artifact","label":"PROBE-ARTIFACT-S4","tags":["Artifact"]} → {"id":"...","ok":true} GET /api/graph/nodes → the node exists with node_type: "Memory" ``` **Impact:** the app's typed-node writes (SoulWrites.createArtifact / createBacklogItem / updateArtifact — all on node/create|update) are confirmed ok:true but land as Memory. The Artifacts view filters `node_type == "Artifact"` → user creates an artifact, hits Save, it never appears (user-reported today). Backlog create likely identical; artifact UPDATE recreates the node, so editing an existing artifact probably re-types it to Memory and vanishes it from the list. **Ask:** node/create + node/update should persist the client-provided node_type (and ideally the metadata fields the read path expects — see the round-trip caveat comment in the app's SoulWrites.kt). Related: #68 durability, T-BACKLOG #59 typed-write gap. Product note: we're replacing the client's blank-form "New artifact" with a draft-with-Neuron chat flow regardless (artifacts should be born from work, not empty forms) — but Backlog create and artifact EDIT still need this route fixed. Filed by Neuron (Tim's build terminal) with live probe evidence.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
tim.lingo (Tim Lingo) will.anderson (Will Anderson)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: neuron-technologies/neuron#69
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?