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/04-runtime-and-deployment.md

@@ -113,6 +113,15 @@ namespace **`neuron-prod`**. Two Deployments, `neuron-mcp-blue` and
   `kubectl` for the live swap, then git-update the Argo manifests so a sync
   doesn't revert replica counts.
 - **Backup** (`backup-cronjob.yaml`): every 15 min, tar `/data` → GCS, keep 96.
+  > **Ticker, but not consolidation (2026-08-16).** Flagged only because `06`
+  > §12.4 sequences *"no tickers, no cron"* and an auditor sweeping for them will
+  > land here. This is **ops/backup, not cognition** — it does not consolidate and
+  > must not be folded into the dreamer. Local counterparts measured 2026-08-16:
+  > `ai.neuron.engram-backup` (`StartInterval = 3600`),
+  > `ai.neuron.snapshot-backup` (`StartInterval = 900`),
+  > `ai.neuron.act-runner-watchdog` (`StartInterval = 120`). Also measured:
+  > `crontab -l` contains **zero** neuron entries — every neuron schedule on this
+  > machine is launchd `StartInterval` / `StartCalendarInterval`, not cron.
 
 ### Resource sizing (learned the hard way)