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.

docs/architecture/07-storage-coherence-and-distribution.md

@@ -127,7 +127,13 @@ subtract( network_now , recall_at(network, t_then) )   # = how that relationship
 ```
 
 is *the geometry of a change over time* — the same `subtract` faculty (`06` §6.1) applied across the temporal
-axis rather than across two regions. `recall_at` at the scale of a whole self is also the mechanism behind
+axis rather than across two regions.
+
+> **Corrected (2026-08-16) — see `06` §12.2.** "Faculty" is doing the wrong work here. Faculties are
+> **operations, not parameters**, and they are distinguished by *what they change*: `reason` changes the
+> estimate (a read), `induce` changes the parameters, `abduce` changes the structure (a write). `subtract` in
+> this passage is a **geometry op** (`engram_geo_subtract`), a pure read over two descriptors — call it that.
+> Nothing in the temporal argument below depends on the word. `recall_at` at the scale of a whole self is also the mechanism behind
 **restoration-as-mercy** in `08` §5 (roll a person back to their last uncorrupted canonical shape).
 
 **Schema sketch (doc-comment; the math/JSON lives here, the faculty name lives in prose) — [TARGET]:**
@@ -347,6 +353,13 @@ as text, not the mind.** (A related live signal from the same session: a text-in
 of scanned records as damaged/degraded text — corroborating that the fat text layer is low-value exhaust, not
 cultivated content.)
 
+> **A third reading (2026-08-16) — see `06` §12.3, §12.4.** The measurement above is also **the ticker showing
+> up on disk.** `curiosity_scan` and `minute_block` are the persisted exhaust of a *timed sweep* — the schema
+> field-names of a scan that should not exist, written 79k+ times per 40 MB. Curiosity is not a scan: a mind
+> does not enumerate its neighbourhoods looking for what is surprising; the surprise captures attention, and
+> salience is bottom-up. `minute_block` names the clock directly. So the fixes below are correct but treat a
+> symptom: **the cheapest record is the one a timer never generates.**
+
 This is doubly wrong: telemetry is **orbit** (`06` §5) — it is supposed to **fall out** on the 48h/window prune,
 not accrete into the durable **body** forever. The fixes: