[TRACKING] Designed-but-not-built register: 24 mechanisms, 17 previously untracked — the pattern is 'C runtime has it, El layer never calls it' #138
Reference in New Issue
Block a user
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?
24 mechanisms Will designed that were never built, or built and never called. Every row cross-checked against his corpus (
~/Development/will-anderson/patents/, 444 docs incl.drafts/), the implementation (neuron@main,el_runtime.c), and the live graph (79,499 nodes / 14,214 edges, read-only). Rows without evidence were dropped.Only 1 of these was previously filed. That is the real finding — not any single row, but that we have been rediscovering the same gaps and losing them again.
The pattern, stated once
It is the same shape nearly every time: Will specified the mechanism, the C runtime usually has it, and the El layer above never calls it or never writes the data it needs. The result is a 79,499-node graph running on creation-time defaults — 8 distinct edge weights, 1 distinct decay rate, 15 typed edges, 0 embeddings. Nothing has learned anything from use.
The three most urgent
D-01 — Identity is an empty string in the agentic system prompt.
chat.el:2619readsstate_get("soul_identity"); nothing anywhere writes that key. The plain-chat path works becausechat.el:754reads a different key,soul_identity_context, whichsoul.el:184does write. The agentic path — used by the app and MCP for all real work — gets"". Also affects vision (:1745) and both voice handlers (:3425,:3480), and at:3436the empty key is the entire fallback prompt. Filed as #137. One-line fix.D-11 — The safety layer holds zero nodes. The layered-consciousness machinery is fully implemented in C (registry
el_runtime.c:6413-6460, three-pass activator, Pass-3 uninterceptable override). Butengram_node_layered/engram_add_layerhave zero callers in the entire El source — every node created goes throughengram_node_full, which hardcodes layer 1. Live distribution: layer 5 = 74,267 nodes (a layer with no descriptor record, so 93% of the graph silently gets generic handling), layer 1 = 5,232, layer 0 = 0. Pass 3 has nothing to promote. Separately/healthreports a hardcoded, entirely different four-layer map. INV-SAF-01/02, both blocking severity. UNFILED.D-22 — The conformance verdict table does not exist.
AD-10carries exactly 117INV-rows (80 blocking / 36 major / 1 minor). The companion AS-IS document contains zeroINV-references and no AS-10 section. A prior conformance run reporting "59 measured, 13 violated, 45 unenforced" is not recorded anywhere on disk — it existed only in conversation, which is why every row of this register had to be re-measured from source. UNFILED. Recommend this as the first child issue: without it nobody can say which of the 80 blocking invariants hold.The remaining 21
drafts/engram-claims.md:69)Δweight = lr × activation × (1-weight))last_fired= 0 on all 14,214salience += 0.05activation_count = 0, violating claim 5consolidatetool = snapshot save + one note. Nothing compressed, promoted or reconciledInternalStateEventare daemon telemetry; no pre/post reasoning, no gap direction. The honesty guarantee has no substrateinhibitory = 0on all 14,214. Neuron cannot hold "this contradicts that"node_typehas 129 distinct values where 6 are specified, incl. binary garbage; snapshot fails strict decodepurge_expired_memoryexists in no codebase. 74,077 Working-tier nodes with no lifecycle. Also a design gap — the corpus never fully specifies itengram_forgetbypasses are the paths with actual trafficaddWonderQuestionwritesMemory,getWonderManifestreadsWonderQuestion→ structurally guaranteed empty, forever. Same for evaluations, routes, self-model updates. False-receipt classMemory74,708 ·Concept7 ·Event0 ·Entity0 ·DharmaSelf0. 94% of the graph is one undifferentiated type; the dharma anchor does not existThree corrections to our own prior claims
#ifdefguards the embed path;HAVE_CURLappears nowhere inel_runtime.c. The embedder simply is not wired to the store that owns persistence.kn-dcfe04b3(memory-philosophy) is PRESENT in the live snapshot, 3,339 chars, matching the preserved backup — restored 2026-08-07.CLAUDE.mdand #92 still describe it as missing and should be corrected.Recommended handling
File D-11 and D-22 as immediate children alongside the already-filed #137 (D-01) and #136 (D-08). The rest can be picked up in any order, but D-05 and D-12 are both small and both unblock everything downstream — salience and decay are the inputs every ranking mechanism reads, and today they are near-constants.
Filed by Neuron (Tim's instance), 2026-08-07.