feat(engram): accumulation layer — new nodes to top of stack, not core-identity #59

Merged

tim.lingo merged 1 commits from feat/accumulation-layer into stage 2026-06-17 18:34:07 +00:00

Conversation 0 Commits 1 Files Changed 1

+24 -2

1 Commits

Author	SHA1	Message	Date
Tim Lingo	18e1ab6db1	feat(engram): add accumulation layer (layer 5) — new nodes default to it, not core-identity ... Implements the accumulation layer from the Layered Consciousness architecture (provisional 64/064,262) and answers the deferred design question. Per the spec and Will's design: new user-facing nodes (memories, knowledge, conversations) are created in an accumulation layer at the TOP of the consciousness stack — the engram the user sees — while the layers below (safety, core-identity, domain, imprint, suit) shape behavior but are hidden from the user. - Adds ENGRAM_LAYER_ACCUMULATION (5) + the layer record in engram_init_layers (activation_priority 50, suppressible, not injectable, transparent=0). - engram_node and engram_node_full now assign new nodes to ENGRAM_LAYER_ACCUMULATION. - ENGRAM_LAYER_DEFAULT stays CORE_IDENTITY ON PURPOSE: it is the fallback for LEGACY nodes loaded from snapshots without a layer_id, so existing data (the originator corpus) is NEVER migrated. New-nodes-only — the immutable-originator rule. This is the foundation for fixing the identity-bleed / customer-isolation issue (user data was landing in Neuron's core-identity layer). The retrieval-side provenance filter (introspection should compile from accumulation, not the originator corpus — Persona 64/036,574) is a follow-on, pending the batch-2 Layered Consciousness + Engram spec docs for exact semantics. Compiles clean. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-17 13:14:57 -05:00