core/docs
Claude 71542e61ee
fix(cognition): a promoted proposal must not un-mark a sibling's speculative material (H-13)
The speculative-marker cache seeds a subject AND each >=4-char token split from
it, so two independent proposals can claim the same token ("wisdom" from both
`wisdom` and `practical wisdom`). `_forget_speculative_subject` popped the token
outright on COHERENT promotion — regardless of which proposal had seeded it — so
promoting one proposal stripped the marker from another that was still
unreviewed. Unreviewed material was then served WITHOUT the "(speculative, not
yet reviewed)" prefix: the expensive failure direction, on the surface whose
whole job is telling reviewed knowledge from unreviewed.

_speculative_subjects becomes OrderedDict[str, int] — the value is a reference
count. Seeding increments and refreshes LRU position; promotion decrements and
evicts at zero. Seeding and eviction walk the same source list so counts
balance; where they disagree the count stays positive and the subject keeps its
marker, which is the honest direction to fail. An unmatched release floors at
removal and never goes negative, so it cannot borrow against a later proposal's
claim. The LRU cap survives unchanged as a size valve.

Four new pins in tests/test_speculative_subject_lifecycle.py, ALL FOUR OBSERVED
RED BEFORE GREEN — sibling token evicted, marker lost at the served surface,
repeated teaching cleared by one promotion, and count underflow. The eight
pre-existing lifecycle pins pass unchanged.

Also H-8e — expand_relation_closure's docstring claimed "Cycle: if path would
revisit a node, skip", describing a check the code does not perform. The code
was right: termination is structural (monotone growth over a finite triple set),
and a path-revisit skip would REFUSE SOUND transitive derivations, since a
witness path that revisits a node still proves a true fact. The docstring now
says that, and records that `path` is the witnessing step rather than full
ancestry — extending it would move operator_invocation and therefore trace_hash,
so it is deliberately not done here.

Registers updated: H-13 marked FIXED with the ratification note (this changes
served surfaces toward disclosure, restoring ADR-0021 §Articulation's stated
intent rather than extending it); H-8e marked CORRECTED.

Found while fixing it, recorded not acted on: tests/test_speculative_subject_
lifecycle.py — the file pinning this exact behavior — is in NO curated suite,
reachable only through `full`. G-7's mechanism, caught on the pin that would
have caught the defect. Assignment left to PR-4; adding it to TEST_SUITES
["smoke"] alone would widen N-3's ten-file delta and prejudge R-14.

Pre-existing ruff findings in pipeline.py (3 unused imports, 1 E402) confirmed
present before this change and left alone — module-top, not adjacent to the edit.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wcw2pnMBwyvmNyQg4uPEt4
2026-07-28 03:24:20 +00:00
..
adr docs(adr): ratify ADR-0265 — Accepted, Joshua Shay 2026-07-27 2026-07-27 13:17:57 -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 docs: apply the Wave 0 record amendments that need no ruling (N-1…N-7, H-12) 2026-07-27 17:38:12 -07:00
assessment fix(cognition): a promoted proposal must not un-mark a sibling's speculative material (H-13) 2026-07-28 03:24:20 +00:00
audit
benchmarks
briefs
curriculum Lane 4: Registry Consolidation (language_packs to packs) 2026-07-04 15:11:28 -07:00
decisions
evals
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 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 feat(evals): measure the reader/writer construction inventories against each other 2026-07-27 14:11:07 -07:00
research docs(assessment): re-anchor the §5 provenance SHAs to the commits that landed 2026-07-28 03:00:46 +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
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 chore: Refactor CLI and Governance Anchors (#926) 2026-07-03 12:34:56 -07:00
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 chore: Refactor CLI and Governance Anchors (#926) 2026-07-03 12:34:56 -07:00
Yellowpaper.md

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.