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/00-overview.md

@@ -104,7 +104,7 @@ The full VBD classification is in `01-vbd-decomposition.md`. In one glance:
 | Cognitive API         | `neuron-api.el`                             | Managers + Engines — session/memory/knowledge/graph/cultivation handlers |
 | Request pipeline      | `soul.el` `layered_cycle`                   | Manager — L1 safety → L2 stewardship → L3 imprint                        |
 | Boot + identity       | `soul.el`                                   | Manager — compose layers, seed identity graph, start server + daemon     |
-| Autonomous cognition  | `awareness.el`                              | Manager (`awareness_run`) + Engines (curiosity, attend, threat)          |
+| Autonomous cognition  | `awareness.el`                              | Manager (`awareness_run`) + Engines (~~curiosity~~ †, attend, threat)     |
 | Memory access         | `memory.el`                                 | Resource Accessor over the engram FFI/HTTP                               |
 | Store                 | `engram/server.el` + `el_runtime.c`         | Accessor (HTTP) over the real graph engine                               |
 | Request-layer rules   | `safety.el`, `stewardship.el`, `imprint.el` | Engines                                                                  |
@@ -112,6 +112,17 @@ The full VBD classification is in `01-vbd-decomposition.md`. In one glance:
 | MCP transport         | `mcp-proxy`, `mcp-wrapper`                  | Managers/Accessors — protocol boundary                                   |
 | Build                 | `manifest.el`, `dist/soul.c`, El toolchain  | amalgamation → `soul.c` → binary                                         |
 
+> **† Superseded (2026-08-16) — see `06-cognitive-architecture.md` §12.3.**
+> Curiosity is **not a peer Engine** beside `attend` and `threat`. It is not a
+> component at all: **curiosity is wonder crystallized at a nucleation site** —
+> one thing at two phases, where wonder is the field (unbounded, objectless,
+> invariant, present wherever there is structure) and curiosity is the
+> precipitate (localized, with an object, able to direct activation). What it
+> seeds is the **same** activation process `attend` runs; there is one activation
+> process with two seed sources — external (a request) and internal (a
+> curiosity) — not two processes negotiating for a resource. Modelling it as a
+> peer Engine is what produced the timed `proactive_curiosity` scan documented in
+> `02-components.md §3b`.
 
 ## Reading guide