3c5084ad2d
Third correction, same session, again from measurement rather than argument. I specified the Phase 2A/2B split as "a table is off-serving only when every caller is proven eval-only," then computed the actual serving import closure: 227 first-party modules from the six real serving entries, and ALL 13 table-owning modules are in it — 13 of 13, including generate/templates.py via pipeline.py -> realizer.py -> templates.py. So the static test I had just written returns "everything is serving" and discriminates nothing. Import-reachable is not call-reachable. Importing a module executes its table literals (pure data) but not its functions. The chain realize_target -> render_step -> _inflect_predicate -> base_form is closed and small enough to verify exhaustively, and realize_target has zero non-eval non-test callers, so §1.2 and §1.4 stand as written. But Python call-reachability is not statically decidable in general. So the arbiter for this arc is EMPIRICAL: make the change, run the 11 pinned lanes, let byte-identity decide. That is stronger than a static claim because it tests behaviour instead of predicting it, and it is what the lane pins already encode as doctrine. Consequence: 2A and 2B are now defined as a RESULT. A change is 2A if the pins come back byte-identical and 2B if they move. Work the changes in order, run the pins, let the split fall out — do not argue a change into 2A. |
||
|---|---|---|
| .. | ||
| adr | ||
| agents/grok | ||
| analysis | ||
| architecture | ||
| 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 | ||
| 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).