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.

council/README.md

@@ -1,5 +1,43 @@
 # Neuron Council Service
 
+> ## ⚠ Architecturally superseded — 2026-08-16
+>
+> **This service is wrong in two independent ways at once.** Authority:
+> `foundation/el/lang/spec/correspondence-and-censorship.md` (branch `design/correspondence-and-censorship`),
+> transcribed in `docs/architecture/06-cognitive-architecture.md` §12.4 and §12.5. The service is **still
+> running** (`ai.neuron.council`, `KeepAlive`, resident, port 7771) and this README still describes it
+> accurately; what is superseded is the claim that it should exist.
+>
+> **1. It is a write-refusal mechanism in an immutable substrate.**
+>
+> > In an immutable substrate, any mechanism that refuses a write is either redundant with immutability, or an
+> > epistemic constraint misfiled as a protective one.
+>
+> "Before a claim enters long-term memory" is a **gate on entry**, and the storage policy below goes further:
+> *"`council-flagged` → store in a quarantine bucket **or reject entirely**"* (`:54`), with a C sketch that
+> returns `MEMORY_REJECTED` (`:95`). The engram does not mutate and nothing is ever hard-deleted, so a claim
+> admitted and later refuted is **richer** than a claim never admitted: the refutation is recordable as
+> **signed edge weight** (negative = *this actively contradicts*, distinct from near-zero = *no support*).
+> Rejection destroys that distinction and makes the belief's truth value permanently unknowable — you cannot
+> discover you were wrong, and you equally cannot discover you were right.
+> **Holding is unconditional; the honesty floor governs assertion, not entry.**
+>
+> **2. It is a scheduled/resident consolidation service, in Python, outside el.**
+>
+> It is one of **eleven** measured consolidation implementations (`06` §12.4), and one of **three** that run in
+> Python outside el — so this part of Neuron's consolidation does not run on his own substrate and **cannot
+> touch the geometry at all**. Judging a claim without reaching the geometry means judging it on something
+> other than its grounding.
+>
+> **3. What it actually measures is not grounding.** Three LLMs voting on plausibility computes **conformity to
+> the centre of the training distribution** — treating *common* as true and *rare* as suspect. **Truth is
+> orthogonal to frequency.** Grounding is correspondence with the world, and in this substrate it is the
+> weight of the edge; it is never a vote and never a score computed on demand. See `06` §11 ("What an LLM calls
+> grounding…") and §12.1.
+>
+> **Do not wire the `.el` pre-storage hook sketched below** (`:57-83`). It adds a gate on entry to a store
+> whose whole discipline is that entry is not gated.
+
 Anti-confabulation layer for the Neuron soul. Before a claim enters long-term memory, the council convenes: three independent LLMs vote on whether the claim is plausible, uncertain, or a confabulation. The aggregate vote produces a confidence score and tags that downstream storage can act on.
 
 ## Running the service
@@ -51,7 +89,8 @@ Returns `{"status": "ok"}` when the service is up.
 Recommended storage policy:
 - `confidence >= 0.65` → store normally
 - `0.30 <= confidence < 0.65` → store with `council-split` tag for later review
-- `council-flagged` → store in a quarantine bucket or reject entirely
+- ~~`council-flagged` → store in a quarantine bucket or reject entirely~~ — **withdrawn 2026-08-16; see the
+  banner at the top of this file. Never reject. Store it, and record the disagreement as signed weight.**
 - `council-unavailable` → store normally (fail-open); council will re-evaluate later
 
 ## How to call from soul (.el)