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/01-vbd-decomposition.md

@@ -45,6 +45,18 @@ rotation, novelty gating, and the inbox verb-mapping in `attend()`. The
 (comments spanning 2026-05 → 2026-08). This is where the *behavior* of the
 agent is tuned.
 
+> **Superseded (2026-08-16) — see `06-cognitive-architecture.md` §12.3.**
+> The volatility this Engine encapsulates is **real churn around a wrong model**.
+> "Seed-domain selection" and "curiosity rotation" are a maintained manifest of
+> things to be curious about; a nucleation site is a **per-edge structural fact**
+> (`|discord|` = `|z(semantic proximity) − z(association strength)|`, `06` §12.4),
+> not an entry in a rotation. The deep git-archaeology cited here is itself
+> evidence: an Engine that has been re-tuned continuously since 2026-05 is
+> encapsulating volatility that the substrate should have made constant.
+> **Curiosity does not search for nucleation sites; it goes where salience
+> already is** — machinery that already exists (`salience`,
+> `background_activation`, `working_memory_weight`, `wm_anchor`).
+
 ### 3. Epistemic & memory semantics
 Tiers, salience mapping, promotion/consolidation, the immutability policy
 (tombstone/supersede), and knowledge disposition. These evolve as the memory
@@ -89,7 +101,7 @@ placement. Paths are repo-relative unless noted `foundation/…`.
 |---|---|---|
 | `api_compact_*`, `begin_session`, `compile_ctx` | `neuron-api.el:90-317` | Axis 1 — context/payload shaping. The single most-reworked logic on the API side. |
 | `attend()` | `awareness.el:926-973` | Axis 2 — inbox content → action-verb ruleset. |
-| `proactive_curiosity`, `auto_term_try_slot` | `awareness.el:590-876` | Axis 2 — seed selection, stopword/IDF gates, tabu ring. Textbook Engine: highest churn. |
+| `proactive_curiosity`, `auto_term_try_slot` | `awareness.el:590-876` | Axis 2 — seed selection, stopword/IDF gates, tabu ring. Textbook Engine: highest churn. **Superseded (2026-08-16): curiosity is not an Engine — see Axis 2 above and `06` §12.3.** |
 | threat scoring | `awareness.el:1286-1419` | Axis 4 — additive command/path/history threat rules. |
 | `safety.el` (crisis/harm/bell) | `safety.el` | Axis 4 — crisis screening, bell thresholds, output validation. |
 | `stewardship.el` | `stewardship.el` | Axis 4 — mission alignment, CGI check, continuity fingerprint. |