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.

neuron-dev-setup/README.md

@@ -7,6 +7,49 @@ speak MCP to Claude Code. Will's personal automations (catalyst, telegram,
 vessels, studio, self-review, world-integrator, council, compressor, snapshots,
 act-runner, …) are **deliberately excluded**.
 
+> ## ⚠ Six of those "personal automations" are one missing subsystem — 2026-08-16
+>
+> Authority: `foundation/el/lang/spec/correspondence-and-censorship.md` §7 (branch
+> `design/correspondence-and-censorship`), transcribed with the full measured inventory in
+> `docs/architecture/06-cognitive-architecture.md` §12.4.
+>
+> The exclusion above and the fuller list further down are **correct as a packaging decision** — a fresh dev
+> does not want Will's laptop's automations. But they are also a **census of a fragmentation**, and it should
+> not be read as a list of unrelated conveniences. Consolidation had no owner, so it was implemented at every
+> site that needed a piece of it. **Every name in the set is a consolidation verb** — compress, cultivate,
+> digest, integrate, review, reify, beat.
+>
+> Measured 2026-08-16 from `~/Library/LaunchAgents`:
+>
+> | agent | what it runs | when | language | is it consolidation? |
+> |---|---|---|---|---|
+> | `ai.neuron.compressor` | `council/compressor_service.py --port 7772` | `KeepAlive`, resident | **Python, outside el** | **yes** |
+> | `ai.neuron.council` | `council/council_service.py --port 7771` | `KeepAlive`, resident | **Python, outside el** | **yes** (and a write-refusal — see `council/README.md`) |
+> | `ai.neuron.cultivation-digest` | `tools/cultivation-digest.sh` | **23:55** | shell | **yes** |
+> | `ai.neuron.world-integrator` | `products/world-ingestor/integrator/run.py` | **06:00** | **Python, outside el** | **yes** |
+> | `ai.neuron.self-review` | `~/.neuron/bin/self-review-launch.sh` | **08:30** | shell → CLI | **yes** |
+> | `ai.neuron.engram-tick` | pokes `POST /api/tick` via `~/.neuron/bin/engram-tick.sh` | `StartInterval = 600` | shell | **yes** |
+> | `ai.neuron.engram-backup` | `~/.neuron/bin/engram-backup.sh` | `StartInterval = 3600` | shell | no — **ops/backup** |
+> | `ai.neuron.snapshot-backup` | `~/.neuron/bin/snapshot-backup.sh` | `StartInterval = 900` | shell | no — **ops/backup** |
+> | `ai.neuron.act-runner-watchdog` | `act-runner-watchdog.sh` | `StartInterval = 120` | shell | no — **ops/CI** |
+>
+> **The last three times — 23:55, 06:00, 08:30 — are a sleep cycle implemented as launchd
+> `StartCalendarInterval` entries.** Someone understood it was consolidation and expressed it as three
+> unrelated scheduled scripts in three languages, none aware of each other. Three of the six run in **Python,
+> outside el**, so part of Neuron's consolidation does not run on his own substrate and cannot touch the
+> geometry at all.
+>
+> **Consolidation is ambient, not scheduled. A brain has no cron job.** *(Precisely: it is not cron either —
+> `crontab -l` has **zero** neuron entries. Every neuron schedule here is launchd.)* **The presence of a
+> ticker is the diagnostic:** every `StartInterval`, every `Hour`/`Minute`, every POST-to-beat marks a place
+> where an intrinsic rhythm was replaced by an external clock. The one fragment with the **correct** shape is
+> `soul.el:731`'s continuous in-process `awareness_run()` loop, which is inside the core stack this repo does
+> install — and it is the shape the six above fold *into*.
+>
+> **Nothing here changes what this repo installs.** The core stack stays four services. The note exists so the
+> exclusion list is not mistaken for a statement that these six are optional extras rather than one subsystem
+> that never got built.
+
 ```
   ┌─────────────┐        ┌──────────────┐
   │  soul :7770 │ ─────► │ engram :8742 │     the mind ──► its memory substrate