Shay 9efd5a6143 docs: apply the Wave 0 record amendments that need no ruling (N-1…N-7, H-12)

The corrections derived in 50-execution-plan.md §0, applied where the wrong
claims live. Every amendment is marked [AMENDED N-x] inline so the register
carries its own correction history rather than quietly reading correct.

Gap register — four entries amended:
- G-5  the soak RAN and passed (5000 beats, reboot at 2500, all four gates,
       aed273b1). Retitled: what is owed is the committed artifact, the pinned
       deterministic_digest, and a cadence — not the run. Both prior claims
       withdrawn with their causes: "no suite contains any l10 test" was a
       scan artifact (TEST_SUITES["full"] is a directory), and the pins
       execute twice a day (post-merge + nightly cron).
- G-7  respecified. The proposed meta-check was already satisfied and would
       have shipped green proving nothing — a hollow gate in the entry
       proposing to abolish hollow gates. Now two pins: gate parity, and
       curated-suite membership EXCLUDING full.
- G-8  28 default-off flags of 32 RuntimeConfig booleans, not seventeen.
- G-10 the 16-premise cap was removed by ADR-0264 R5 on 2026-07-26; the ADR
       carries a self-supersession banner directly under the heading Phase 4
       quoted. No engineering prerequisite remains — R-8 alone gates it.
- G-19 note: the 21/25 exposure is already pinned in test_volume_honesty.py,
       so the work is applying the demotions, not discovering them.

Hindrance audit:
- H-12 added — the local smoke suite (23) and smoke.yml (13) have diverged by
       ten files. Counter-evidence stated first: AGENTS.md makes the local run
       the merge gate and it is the superset, so nothing is unguarded. What is
       real is one comment claiming an equality that does not hold, and the
       push that skipped the local gate.
- H-8  gains instance (d), inside the code: two flag docstrings assert a
       production profile CONTINUOUS_LIFE_CONFIG_FLAGS does not have.
- H-1  gains the already-pinned note.

Also: correction note on the 2026-07-25 verification doc (a corrective
document that introduced the error at H-8c), and a staleness banner on
MIND-PHYSICS-BLUEPRINT.md pointing at the taxonomy that dissolved it.

The two ratified-ADR amendments (ADR-0146, ADR-0252) are NOT here — they are
drafted in full in 50-rulings.md R-12 and land on that ruling, because editing
a ratified ADR is Shay's authority even when the edit changes no decision.

Docs only. No runtime behavior, no flag, no test changed.

2026-07-27 17:38:12 -07:00

3.6 KiB

Raw Blame History

CORE Mind-Physics Blueprint

Version: 0.1.0
Date: 2026-05-12
Status: Draft — stale since 2026-05-12; not under active development

Staleness banner — 2026-07-27 (holistic assessment Phase 6). This blueprint has not moved since its authoring date and was one of CORE's five unreconciled macro articulations of its own cognitive cycle. Those five were dissolved into the two-axis taxonomy in docs/assessment/02-layer-taxonomy.md (decision D1) — read that first for the current structural account. What this document uniquely contributed, the allocation/attention physics layer (ADR-0008), was verified live in Phase 2 (generate/stream.py:255-263, use_salience defaults True) and is ungoverned rather than absent; it is registered as G-14 awaiting a one-page ADR. Nothing here is authoritative; it is kept for its intent.

The Three Physics Layers

CORE's cognitive cycle is governed by three physics layers that compose in sequence:

FieldState (populated by ingest layer, ADR-0007)
       │
       ▼
┌─────────────────────────────┐
│   ALLOCATION PHYSICS        │  ADR-0008
│   SalienceOperator          │  curvature → SalienceMap
│   AttentionOperator         │  SalienceMap + Budget → AttentionPlan
│   InhibitionOperator        │  AttentionPlan + FieldState → InhibitionMask
└─────────────┬───────────────┘
              │  foregrounded field regions
              ▼
┌─────────────────────────────┐
│   COMPOSITIONAL PHYSICS     │  ADR-0009
│   BindingOperator           │  co-activation → BindingFrame
│   DigestOperator            │  BindingFrame → FieldState (updated)
│   TrajectoryOperator        │  [BindingFrame] → ReasoningTrajectory
│   ArticulationPlanner       │  Trajectory + Modality → ArticulationPlan
└─────────────┬───────────────┘
              │  structured output plan
              ▼
┌─────────────────────────────┐
│   IDENTITY PHYSICS          │  ADR-0010
│   IdentityCheck             │  Trajectory × IdentityManifold → IdentityScore
│   DriveGradientMap          │  persistent gradient bias on FieldState
│   ExertionMeter             │  cumulative cost → FatigueIndex
└─────────────┬───────────────┘
              │  validated, identity-consistent ArticulationPlan
              ▼
         RENDERER
         (modality-specific surface realization)

Data Flow Summary

Layer	Input	Output	ADR
Ingest	raw source (any modality)	`CandidateGeometricPressure` → `FieldState`	ADR-0007
Allocation	`FieldState`	`AttentionPlan`, `InhibitionMask`	ADR-0008
Compositional	`AttentionPlan`, `FieldState`	`ReasoningTrajectory`, `ArticulationPlan`	ADR-0009
Identity	`ReasoningTrajectory`, `ArticulationPlan`	`IdentityScore`, validated plan	ADR-0010
Renderer	`ArticulationPlan`	surface output (text, code, data)	TBD

Next Steps

Rust acceleration targets: curvature kernel, coherence wave, trajectory delta
IdentityManifold bootstrapping protocol (architect-level, deliberate)
Renderer interface definition (ADR-0011, planned)
Integration tests across the full ingest → allocation → compositional → identity cycle

3.6 KiB Raw Blame History Unescape Escape

CORE Mind-Physics Blueprint

The Three Physics Layers

Data Flow Summary

Next Steps

3.6 KiB

Raw Blame History