core/docs
Shay 36cb29a693 docs(assessment): Phase 2 — nine layer cards, verified against code not documents
Fills the taxonomy with evidence. Every liveness label re-verified at
8927c563 rather than inherited from the 2026-06-09 system map. Three
inherited claims did not survive, and every one of them came from a
document while every falsification came from reading code.

CORRECTIONS:

- Phase 0 Finding 0-C was WRONG. The L11 always-on process IS BUILT:
  chat/always_on.py::run_continuous, chat/always_on_daemon.py::run_daemon
  (single-instance lock, SIGINT/SIGTERM stop, load-time identity guard),
  CLI `core always-on`. Landed 2026-06-14 — five days AFTER the system-map
  snapshot that declared no forever entrypoint exists. The real finding is
  sharper: built, with a complete falsifiable soak harness, never run to a
  recorded artifact, and enforced by NO SUITE AT ALL.
- CR-1 attention/allocation is not a missing layer but a live undocumented
  one: generate/stream.py:255-263 runs SalienceOperator -> AttentionOperator
  and gates every generation step; use_salience defaults True. It owns the
  ~73%-of-turn hot path and has no ADR, no card, no layer in any ratified
  articulation. (generate/salience.py COMPOSES core.physics.salience — not
  a duplicate; that false lead is recorded, not propagated.)
- CR-2's components exist: DriveGradientMap and ExertionMeter are both
  constructed in chat/runtime.py. DriveGradientMap is NEVER READ — textbook
  decoration by the sabotage test. ExertionMeter runs but feeds telemetry
  only; fatigue gates no decision. The claim survives and sharpens: CORE has
  drive objects and no chooser.

STAGE-COVERAGE AUDIT: 7 of 9 covered; non-text ingest uncovered (59
sensorium modules reach no serving path); the cycle's runner claimed-only.

CROSS-CUTTING: F-1 built-and-off is the dominant pattern (17 flags default
False, only deduction_serving ratified ON) with no register of the set or
what would flip it. F-2 enforcement lags capability — orphaned pins are
undetectable because suite tuples are hand-curated. F-3 formation's
six-boundary trust standard is not applied at M2, the surface facing
untrusted user text. F-4 ADR/code contradictions are load-bearing (the
daemon has no ADR while ADR-0146 rejected the daemon shape; ADR-0252's
"34 surface organs" does not reproduce — 18 found). F-5 what is excellent,
stated plainly: the typed learning boundary, selection-not-rewrite, the
non-hardening invariant, fail-closed lane shapes.

No layer is wrong-solution. Two candidates deferred to Phase 4 with
evidence: Wilson/replay independence in licensing, DriveGradientMap.
2026-07-27 15:45:52 -07:00
..
adr docs(adr): ratify ADR-0265 — Accepted, Joshua Shay 2026-07-27 2026-07-27 13:17:57 -07:00
agents/grok
analysis
architecture
assessment docs(assessment): Phase 2 — nine layer cards, verified against code not documents 2026-07-27 15:45:52 -07:00
audit
benchmarks
briefs
curriculum
decisions
evals chore: Refactor CLI and Governance Anchors (#926) 2026-07-03 12:34:56 -07:00
examples
handoff docs(arc): reconcile the arc's records with what the units measured 2026-07-26 12:33:30 -07:00
handoffs
implementation
issues
lab
outreach
paradigm-archive
plans fix(generate): a proposition graph must be able to represent denial (ADR-0265) 2026-07-27 13:08:17 -07:00
research Merge pull request 'Rust parity: cargo green, lane parity unfalsifiable — plus core rust build was broken (plan §6A)' (#124) from fix/rust-build-env-and-parity-report into main 2026-07-26 20:20:16 +00:00
sessions
specs fix(runtime): defer the turn-event sink emission to the serve boundary (R7) 2026-07-26 10:56:03 -07: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 chore: Refactor CLI and Governance Anchors (#926) 2026-07-03 12:34:56 -07:00
3lang-depth-pr-plan.md
admissibility-exemplars.md
ci-optimization.md
conceptualizing_engineering_mastery.md docs(assessment): Phase 0 — ground truth, corpus triage, and the Phase 1 handoff 2026-07-27 15:19:54 -07:00
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
sponsors.md
teaching_order.md chore: Refactor CLI and Governance Anchors (#926) 2026-07-03 12:34:56 -07:00
test-debt-quarantine.md
testing-lanes.md
Whitepaper.md chore: Refactor CLI and Governance Anchors (#926) 2026-07-03 12:34:56 -07:00
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.