8f2e238dc7
Fixes the decomposition Phases 2-3 fill and Phase 4 audits against, per Pillar I: criteria before judgment. Five decisions recorded explicitly: - D1 The five unreconciled articulations answer five DIFFERENT questions (what for / what happens today / by what mechanism / judged how / built where) and become axes of one taxonomy rather than competitors. Functional axis = the AGENTS.md north star; structural axis = 7 macro layers (M0 Substrate, M1 Knowledge & Memory, M2 Afferent, M3 Comprehension & Reasoning, M4 Expression & Serving, M5 Learning & Growth, M6 Continuity & Process) + 2 cross-cuts (MG Governance, MV Verification), grouping all 33 system-map zones with straddles recorded honestly. Mind-physics blueprint dispositioned element-by-element (identity/compositional/renderer = superseded by stronger implementations; Allocation Physics and DriveGradientMap = orphans -> Candidate Register). - D2 System-map schema EXTENDED, not replaced: 7-value liveness kept; four missing dimensions added as orthogonal fields — evidence (with would-fail-if-absent sabotage bit), capacity (designed/measured/ceilings), design-vs-build split, fitness (6-value: fit/strained/misplaced/ wrong-solution/superseded-in-place/undetermined). Liveness ⊥ fitness: the 34 organs are live-serving + superseded-in-place, a state no merged enum could express. - D3 Completeness criteria fixed: coverage = evidence-bearing ownership of a functional stage; deferred-with-ruling ≠ missing; pins must run. - D4 Candidate Register: CR-1 attention/allocation (the ~73%-of-turn-time hot path has no owner), CR-2 agenda/drive (mechanisms without a chooser; L10 risks landing as a heartbeat with nothing to want), CR-3 efferent action (needs an explicit deferred-vs-out-of-telos ruling), CR-4 temporal self-location (determinism vs lived time, undesigned). Considered-and-not- registered recorded (sociality, affect, embodiment, self-governance-as- layer) so the boundary is visibly examined. - D5 Assessment output is COMMITTED (reviewable, versioned, visible); system map stays local as a regeneratable navigation index. Staleness handled by verified_at SHA stamps on every card. Phase 2 work order: nine layer cards, priority M6 > M3 > M4 > M5; re-verify every map liveness label; run the stage-coverage audit with evidence; the four zero-subsystem zones scoped honestly and queued first for Phase 3. |
||
|---|---|---|
| .. | ||
| 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).