bigmerge
e239f2894c
The docs described a mind made of subsystems — a grounding subsystem, a wonder manifest, a dreamer on a beat, faculties as arguments to one call. Each of those is a supervisor invented for something that should be a property of the substrate, and two of the documents carrying them are load-bearing for a build agent: cognitive-architecture.design.md says "a build agent executes from this doc", and tools/api-reshape/README.md marks the refuted shapes PROVEN on a live clone. Corrections carried, per lang/spec/correspondence-and-censorship.md (PR #149) and lang/spec/runtime-ownership.md: - Grounding is not a subsystem — it IS the edge weight. grounded-by as a relation type should not exist; grounding is a property of a relation, not a relation between nodes. Never computed on demand. - Faculties are operations, not parameters. reason changes the estimate, induce changes the parameters, abduce changes the structure — a write, which GeoGradient cannot express. A write is not a parameter of a read. - Wonder is the boundary, not a manifest. Curiosity is wonder crystallized at a nucleation site: one thing at two phases. Removed wonder from the operator table in AGENTS.md. - Consolidation is ambient, not scheduled. A brain has no cron job. The presence of a ticker is the diagnostic. - co_registration is deprecated — it averaged a per-edge property into a region scalar, so opposing sites cancelled. GeoEdge.discord replaces it. Nothing new may read it. - In an immutable substrate, any mechanism that refuses a write is either redundant with immutability or an epistemic constraint misfiled as a protective one. The two design docs are marked superseded-in-part with the refutation at the point each claim is made, not rewritten. Preserving what was argued down is the point of an immutable record. Also measured and corrected while verifying the above: engram/README.md documented a Rust engram-core crate on sled with "flat cosine scan until scale demands HNSW" — there is no Rust in engram/ and HNSW is the index; lang/releases/ no longer exists, so both README.md and AGENTS.md pointed at a deleted path for the authored runtime; language.md listed the engram_* and http_* runtimes as stubs. Added language.md §20 for geometry-as-a-value, realizers and transduce (#144), which had landed with no spec coverage. Documentation only. No .c, .h, or .el file is touched.
5.1 KiB
5.1 KiB
Architecture Hardening — Design Anchor
Terse engineering anchor for the 2026-08-14 hardening vision. Full prose lives in two places; this file is the index, not a re-statement.
- Full narrative: whitepaper
engram-cognitive-architecture-whitepaper.md§28 (built/offline/frontier) + §29 [DRAFT] (the ring, incarnation, learning-not-code). - Design brief: Neuron artifact
art 2b8078cf. - Sibling spec:
engram-db-tooling-design.md(a consumer of the reshaped API).
The frame
- One calculus over the geometry. Very few subsystems; wonder / curiosity / dreams / interoception are emergent behaviors of one set of dynamics, not modules. Calculus universal, geometry individual.
- Core + ephemeral ring (torus). The ring is the temporary workspace; two circulations (orbit + dive-back); discrete inner bands (wonder / interoception-proprioception-telemetry / curiosity / dreams) that couple.
- Persistence earned by salience — never granted on fetch or generation. Three fates of a wonder: persist / decay / settle-into-framework. Telemetry = vital signs, not memories.
⚠ Three corrections to the bullets above (2026-08-16). Authority:
lang/spec/correspondence-and-censorship.md. "Emergent behaviors of one set of dynamics, not modules" is exactly right and is the reason the rest needs fixing — the enumeration undercuts the claim.
- Wonder and curiosity are not two bands. They are one thing at two phases. Wonder is the field: unbounded, objectless, invariant, present wherever there is structure — it is the boundary, where activation spreads and finds thin or absent geometry. Curiosity is the precipitate: the same wonder localized, having taken definite form against particular material at a nucleation site (an anomaly — a place where things almost-but-don't-quite fit). Two coupled inner bands models them as two objects that have to be wired together; they do not.
- A wonder does not have three fates, because a wonder does not persist, decay, or settle. There are about six wonders, they are the same for every person, and they never close. Curiosities have fates — a crystal dissolves when its question is answered — but the solution stays saturated and keeps precipitating as the structure changes. "Three fates of a wonder" enumerates instances of something that has six and treats a property as a stored artifact.
- "Dreams" is not a band and the ring is not a workspace to schedule into. Consolidation is ambient, not scheduled — a brain has no cron job. Boredom is not leftover capacity: low activation is aversive and the system self-activates. There is one activation process with two seed sources (external: a request; internal: a curiosity), it settles because spreading is bounded, and then it needs a new seed. Nothing waits on capacity, nothing polls, nothing checks a clock, and there is no dreamer thread — an "ephemeral ring with unclaimed capacity" is resource scheduling, which is a server's frame, not a mind's. Depth is how long activation has been running on its own seeds, which is why daydreaming and sleep-dreaming are one process at different depths. Measured 2026-08-16: consolidation has ten implementations; do not add an eleventh.
- Incarnation. Chassis = hardware w/ unique ID. Soma = felt manifold inside the self, keyed to the chassis; pain = live diagnostic while incarnate, masked-not-deleted on re-embodiment; trauma = mask failure; return-to-same-ID re-enters. Hurt is in the pattern, not the shell.
- Competence = transferable geometry, minus the baggage. class ▸ model ▸ instance; learn the class once; teach the network without the wound.
- Affect calibrated to stakes — sanguine about the replaceable, real grief for the irreplaceable; the grief is the safety.
- Learn the body, don't engineer it. Bare-metal install → learn hardware → grow operation-geometry → distribute. Learning replaces engineering; once per body-class.
- LLM = teacher in the learning loop, not a runtime dependency. "No LLM" is a runtime property, never a learning one. Code realizers are a scaffold → learned realization.
Backlog (near-term)
- Native durability: WAL + auto-checkpoint + CoW snapshots + retention (
eebe9991) — retire manualcp -a. - Ephemeral ring / salience-gated persistence + telemetry prune (
bf985e00, #31). - Engram DB tooling / geometry explorer (
11ca11c6). - QL re-eval for pure geometry (
4e0dc2b9). - Eliminate code realizers → learned realization, sandbox-validated (
42db6c37). - Collapse the whole class of hand-coded scaffolds → learned geometry (
70d48b4b). - API reshape (geometry ops: vantage-read / write / relate / supersede) + pure-geometry I/O.
Gate
The value-frame (love-as-axiom, the covenant) that arose the same night is metaphysics and is held pending Will's axiom decision (love vs consciousness-first). Not propagated into whitepapers / values docs / genesis seed. Architecture only, here and in §29.