core/docs
Shay c1d08ff9d5 feat(curriculum): sealed-practice producer for curriculum serving (Phase C)
Builds the producer `chat/curriculum_serve_license.py` already named as the
only writer of the ledger it reads — `evals.curriculum_serve.practice.runner
.seal_ledger` — which did not exist. Until now, authoring curriculum could
not earn a license at any volume.

A band's case space is ENUMERATED, not authored: every exam question that
routes to that subject (resolve_domain) whose relation is in that family, one
committed case per distinct query atom. So `committed == distinct` is not a
property the generator maintains, it is the same fact twice — the structural
form of ADR-0264 R9, and why this producer cannot develop the deduction
producer's exposure (CASES_PER_BAND=720 filled from spaces as small as 28).
CASES_PER_BAND=660 follows `evals/determination_estimation` per
DIVISION-OF-WORK §4: a ceiling on committed volume, not a quota.

11 bands, wrong=0, inflation 1.0 everywhere.

THE LEDGER IS DELIBERATELY NOT COMMITTED. The plan's Phase-1 exit criterion
asked for "a real (still-unearned) ledger"; that state is unreachable.
Reliability is commitment precision and a correct UNKNOWN is a commitment, so
conservative_floor(660,660)=0.990046 clears theta_SERVE on non-commitments
alone. Sealing today licenses FOUR bands on evidence that is 99.0%-99.98%
correct non-commitment — which ADR-0262 §5.1 rules unacceptable and which
ClassTally structurally cannot see (no verdict axis). Writing the artifact is
therefore a ratification and belongs to Phase D's explicit human-run verb.
The open outcome-mix ruling is now blocking, not academic.

Two corrections to my own earlier records, both measured:

- ADR-0264 §4.2 sized bands from per-TERM exclusivity; the router's predicate
  is per-PAIR, which is looser. Every ceiling was understated, and
  systems_software_causal is 720 not 630 — flipping it from "cannot reach
  657" to "can". 4 of 11 bands can reach the floor, not 3. Now pinned as
  measured values in BAND_ATOM_SPACE.
- `then` and `therefore` are taught philosophy_theology lemmas AND control
  words of the argument reader (`therefore` is the conclusion marker). 164
  routable atoms refuse compiled_premises_unreadable — coverage misses, never
  wrongs — in the band Phase F retargets to. The vocabulary boundary is not
  screened against the reader's grammar; a pack teaching and/or/not/if would
  open a much larger hole the same way. Recorded, not fixed (§6.5), pinned as
  a two-lemma bound.

Registers curriculum_serve in AUDIT_SOURCES, retiring the declared `None`
that was Phase C's forcing function, and adds the producer to `deductive`.

[Verification]: in-worktree on canonical CPython 3.12.13 with `uv sync
--locked`: smoke 571 (569 + 1 test + 1 parametrization), deductive 310
(291 + 19). Mutation-checked: injecting the deduction padding pattern into
band_cases turns 5 tests red including the R9 audit and the seal guard.
curriculum_serve lane unchanged at n=32 correct=32 wrong=0 anti_recall=5;
all 11 lane SHA pins match; no ledger written, so no serving change.
2026-07-26 09:52:54 -07:00
..
adr test(reliability): volume-honesty invariant + distinct-evidence audit 2026-07-25 16:03:10 -07:00
agents/grok
analysis feat(coherence): grounded-open hedge arm — serve pack surfaces honestly hedged instead of over-refusing (ADR-0254) 2026-07-23 01:27:17 -07:00
architecture
audit
benchmarks
briefs docs(governance): weekly-audit rulings T1/T7/T8/T9 — INV-32/33/34 registration, ADR-0243 fold, residual escalation, path sweep, prune ledger 2026-07-22 19:18:59 -07:00
curriculum
decisions
evals chore: Refactor CLI and Governance Anchors (#926) 2026-07-03 12:34:56 -07:00
examples
handoff docs(handoff): E1/R7 assertion spec + arc status after Phases A and B 2026-07-25 16:11:33 -07:00
handoffs
implementation
issues fix(tests): session-scoped engine-state isolation baseline — close module-scope escape to the live life-store 2026-07-22 20:32:06 -07:00
lab
outreach
paradigm-archive
plans docs(handoff): E1/R7 assertion spec + arc status after Phases A and B 2026-07-25 16:11:33 -07:00
research feat(curriculum): sealed-practice producer for curriculum serving (Phase C) 2026-07-26 09:52:54 -07:00
sessions
specs feat(provenance,teaching): close the lateral gaps the assessment actually found 2026-07-25 04:51:15 +00:00
workbench docs(governance): weekly-audit rulings T1/T7/T8/T9 — INV-32/33/34 registration, ADR-0243 fold, residual escalation, path sweep, prune ledger 2026-07-22 19:18:59 -07:00
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 chore: Refactor CLI and Governance Anchors (#926) 2026-07-03 12:34:56 -07:00
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 chore: Refactor CLI and Governance Anchors (#926) 2026-07-03 12:34:56 -07:00
sponsors.md
teaching_order.md
test-debt-quarantine.md
testing-lanes.md
Whitepaper.md
Yellowpaper.md Lane 4: Registry Consolidation (language_packs to packs) 2026-07-04 15:11:28 -07:00

CORE Documentation Index

This is the central index for all documentation in the CORE project.

Canonical Root Documents

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>.md convention).
  • research/ - Raw research notes and preliminary findings.
  • lab/ - Experimental content (Warning: Not ratified; must not be referenced as authoritative in production PRs).

External

  • outreach/ - External communications and messaging.
  • zig/ - Scoped documentation for the Zig language components.