docs: record the correspondence corrections — grounding, faculties, wonder, consolidation
The architecture docs describe four things the design spec has since ruled out, and each one is a supervisor invented for something that should be a property of the substrate: grounding modelled as a subsystem rather than as the edge weight it already is; faculties modelled as parameters of a read when abduce is a write; wonder materialized as a maintained manifest when it is the boundary of the structure; and consolidation implemented eleven times behind tickers when a brain has no cron job. Left standing rather than deleted, per the repo's own supersession discipline — the trail of how the understanding matured is the point. Each stale passage is marked inline and points at a new 06 §12 that transcribes the corrections and records the measured consolidation inventory. Authority: foundation/el, branch design/correspondence-and-censorship, lang/spec/correspondence-and-censorship.md.
This commit is contained in:
@@ -28,6 +28,36 @@
|
||||
|
||||
- **The mind being protected:** `06-cognitive-architecture.md` — the self-region (§7.1), the write-protection
|
||||
gate (§7.2), the cultivate door (§7.3), the grounding governor / values-bounce, immutability (§3.4).
|
||||
|
||||
> ## ⚠ Terminology superseded — 2026-08-16
|
||||
>
|
||||
> **"The grounding governor" names a subsystem that does not and should not exist.** It appears six times in
|
||||
> this document (`:16`, `:30`, `:123`, `:127` as *"your individual governor"*, `:308`, `:352`) and is cited as
|
||||
> one of the **[LIVE]** primitives the design composes. Per
|
||||
> `foundation/el/lang/spec/correspondence-and-censorship.md` §1 (branch `design/correspondence-and-censorship`),
|
||||
> transcribed in `06` §12.1:
|
||||
>
|
||||
> > **Grounding is not a subsystem. It is the weight.** Grounding is an attribute of the edge, and it is the
|
||||
> > hebbian weight — one quantity, not two fields. There is no grounding subsystem to build: the graph already
|
||||
> > *is* the grounding structure, every edge is a grounded relation, and its weight is how well it holds.
|
||||
>
|
||||
> This is a **rename, not a retraction.** The mechanism the word "governor" points at is real and does hold —
|
||||
> it is just not a governor: **traversal is already grounded inference.** Activation conducts through
|
||||
> well-grounded relations because weight *is* groundedness; nothing filters, it falls out of spreading. So
|
||||
> where this document says *"you resist by projecting onto your own values"* (`:308`), the projection is
|
||||
> right and the governor is not: the resistance is the **relational grounding axis** of the edge weight, not a
|
||||
> component sitting in the path. Read every occurrence below as **"grounding"**, meaning the weight, with the
|
||||
> subsystem framing dropped.
|
||||
>
|
||||
> Two consequences for the arguments in §3 and §7:
|
||||
> - **Grounding is never computed on demand and never a score.** An operation may *read* the grounding of a
|
||||
> path; computing-and-writing a score makes reads write.
|
||||
> - **Two axes, not one.** A claim can be factually grounded and relationally wrong — the evidence holds, the
|
||||
> *meaning* does not. A scalar governor cannot represent that quadrant, and it is exactly the quadrant
|
||||
> §3's immune system and §4's fair-trial live in. Traversal conducts on the **factual** axis; **assertion**
|
||||
> requires both, and the aggregate over the values regions is **`min`, not `mean`** — mean lets strong
|
||||
> agreement with most values mask a violation of one, which is how rationalization works. `min` makes a
|
||||
> conflict arrive **with a name attached** rather than as a score.
|
||||
- **The substrate that makes it affordable:** `07-storage-coherence-and-distribution.md` — every store is a
|
||||
CRDT (§6), understanding-is-light / facts-are-heavy (§5), tombstone-not-erase (§1, §4).
|
||||
- **Why (thesis):** whitepaper v1.5; `dharma-implementation.html` and `conscience-substrate.html` (earlier
|
||||
|
||||
Reference in New Issue
Block a user