d0bedfc198
Wave 1 — delete — run before more Wave 2 enforcement, correcting the method inversion this arc had been committing: the plan sequences scrub -> DELETE -> enforce, and Wave 1 was ruling-blocked while Wave 2 was not, so enforcement landed first on structures deletion might have removed. PR-3 (R-7 ruled A) docs/gaps.md and docs/audit/substrate-liveness-ratchet.md carry historical banners that name H-9's own mechanism as the reason they exist: an instrument that looks authoritative converts "I should check" into "I already checked". The ratchet's seven OPEN items — W-003, W-005, W-007, W-008, W-009, W-017, W-018, every one L10-chained — migrated into G-5 WITH their dependency chains, because that reasoning is the ratchet's lasting contribution and its status column is not. One deliverable could not be executed as written and is recorded rather than claimed: L12 has NO in-repo generator to drop it from. The system map is local and gitignored (D5 — a regeneratable index carrying no authority), so the phantom existed only there and in one taxonomy row. That row now records the ruling instead of the flag. PR-3b — new, and it corrected its own author Added when PR-4's two ratchets made the question unavoidable: what exactly are they policing? Measured: 21 curated suites, 9 holding exactly ONE file, 12 holding <=4, and 2 reachable from any gate. I proposed cutting ~11. The evidence supported FOUR. cognition, teaching, packs and algebra are named in AGENTS.md's own pre-merge-gate instruction; fast, pulse and proof in the CLI's help text; phase5, phase6, adr-0024, math and formation in READMEs and ADRs. Deleting those breaks documented commands — worse than the sprawl. Taking the 4 the evidence supports, rather than the 11 I had already said out loud, is the whole point. Deleted: refusal, margin, rotor, inner-loop. Zero --suite references anywhere in code, docs, ADRs, workflows or CLI help. Per-phase ADR-0024 aliases offered so reviewers could run a phase independently; nothing ever did. All seven of their files remain covered by adr-0024 — verified BEFORE the cut — so nothing was orphaned and no coverage moved. 21 -> 17 suites. Pin 3's gate-unreachable gap 19 -> 15 BY DELETION, which costs no gate time at all, versus promotion which costs it every run. An alias nobody calls is not a curation decision; it is one more name that has to be kept true, and two ratchets were policing these. Registers: H-9 CLOSED, PR-3 and PR-3b marked LANDED, G-5 carries the seven migrated items, the taxonomy's L12 row records the ruling. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Wcw2pnMBwyvmNyQg4uPEt4 |
||
|---|---|---|
| .. | ||
| adr | ||
| agents/grok | ||
| analysis | ||
| architecture | ||
| assessment | ||
| audit | ||
| benchmarks | ||
| briefs | ||
| curriculum | ||
| decisions | ||
| evals | ||
| examples | ||
| handoff | ||
| handoffs | ||
| implementation | ||
| issues | ||
| lab | ||
| outreach | ||
| paradigm-archive | ||
| plans | ||
| research | ||
| sessions | ||
| specs | ||
| workbench | ||
| zig | ||
| 3lang-depth-pr-plan.md | ||
| admissibility-exemplars.md | ||
| ci-optimization.md | ||
| conceptualizing_engineering_mastery.md | ||
| core-rd-base-prompts.md | ||
| ethics_packs.md | ||
| EVAL_AUDIT_2026-05-20.md | ||
| eval_methodology.md | ||
| frontier_baselines.md | ||
| gaps.md | ||
| handoff_template.md | ||
| hitl-backpressure.md | ||
| holdout_recipients.txt | ||
| identity_packs.md | ||
| master-plan-post-substrate-audit.md | ||
| memo.html | ||
| model_dependency_size_tally.md | ||
| pack_inventory_2026-05-21.md | ||
| position_paper.md | ||
| PROGRESS.md | ||
| README.md | ||
| recognizer-registry.md | ||
| refusal-taxonomy.md | ||
| reviewers.yaml | ||
| RUST.md | ||
| safety_packs.md | ||
| sponsors.md | ||
| teaching_order.md | ||
| test-debt-quarantine.md | ||
| testing-lanes.md | ||
| Whitepaper.md | ||
| Yellowpaper.md | ||
CORE Documentation Index
This is the central index for all documentation in the CORE project.
Canonical Root Documents
- Whitepaper.md - The CORE architectural and philosophical whitepaper.
- Yellowpaper.md - Technical specifications and mathematical formulation of the CORE engine.
- PROGRESS.md - High-level project progress tracking.
- specs/runtime_contracts.md - Critical invariants and bounds for the runtime execution flow.
Directories
Architecture & Design
- adr/ - Architecture Decision Records (ADRs). The canonical history of all ratified engineering choices.
- architecture/ - High-level architectural documents (e.g., pipelines, schemas).
- analysis/ - Deep dives and master plans for structural changes.
- specs/ - Detailed technical specifications and invariants.
Planning & Progress
- plans/ - Capability roadmaps and implementation plans.
- briefs/ - Project briefs and scoping documents for upcoming work.
- issues/ - Detailed issue analyses and technical reproductions (not standard trackers).
- audit/ - Audit reports and claims ledgers.
Operations & Usage
- examples/ - Usage examples and reference integrations.
- workbench/ - Documentation for the CORE workbench UI and related tooling.
- agents/ - Agent-specific operational guides.
Note regarding
agents/grok/: Operational guide for using Grok 4.3 + Grok Build with CORE. This is not architecture documentation.
Learning & Evaluation
- curriculum/ - Documentation on the teaching/learning order and knowledge progression.
- evals/ - Evaluation methodology and performance criteria documentation.
- benchmarks/ - Benchmark evidence and performance tracking logs.
Historical & Experimental
- sessions/ - Chronological session logs documenting the "decision trail" and intellectual history of major choices.
- handoffs/ - Legacy brief, audit, and investigation notes (historical; the formal HANDOFF mechanism is retired — see AGENTS.md for the current lightweight
session-break-summary-<DATETIME>.mdconvention). - research/ - Raw research notes and preliminary findings.
- lab/ - Experimental content (Warning: Not ratified; must not be referenced as authoritative in production PRs).