core-labs/core
core-labs/core
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity
core/docs/assessment
History
Claude 635f248834
docs(assessment): re-verify the Wave 0 amendments at main tip, and correct H-8d 
PR-1's amendments were derived at ed06dd64. main has since moved (#140, #138),
so every amended claim was re-measured against code at 797ebad5 before landing:

  - TEST_SUITES["full"] == ("tests/",)                        (N-1) holds
  - 5 tests/test_l10_*.py, none marked quarantine or slow      (N-2) holds
  - smoke suite 23 files vs smoke.yml 13, same ten-file delta,
    and zero CI-only files (local is strictly the superset)    (N-3) holds
  - RuntimeConfig: 32 booleans, 28 off, the same 4 on          (N-7) holds
  - CONTINUOUS_LIFE_CONFIG_FLAGS still omits accrual           (N-6) holds
  - ADR-0264 §4.1 self-supersession banner in place            (N-5) holds
  - 18 resolve_promotable_* organs in generate/derivation/     (H-8b) holds

One correction to the amendment itself. H-8d said CONTINUOUS_LIFE_CONFIG_FLAGS
"contains neither claim's subject." It contains one of them: consolidate_
determinations IS forced. The false clause in both docstrings is the one naming
accrue_realized_knowledge as co-enabled, and a third comment on persist_session_
state makes the same shape of claim and is true. The entry now says that, and
says it was caught on re-verification — the same standard §0 holds itself to.

Docs only. No runtime behavior, no flag, no test changed.
2026-07-28 02:55:30 +00:00
..
10-layer-cards docs(assessment): Phase 3 — component descent; the correction chain continues into code 2026-07-27 15:57:36 -07:00
20-component-cards docs(assessment): Phase 3 — component descent; the correction chain continues into code 2026-07-27 15:57:36 -07:00
00-scope-and-method.md docs(assessment): Phase 4 — the gap register and the hindrance audit 2026-07-27 16:04:22 -07:00
01-phase0-ground-truth.md
02-layer-taxonomy.md
03-card-schema.md
04-phase2-findings.md docs(assessment): Phase 2 — nine layer cards, verified against code not documents 2026-07-27 15:45:52 -07:00
05-phase3-findings.md docs(assessment): Phase 3 — component descent; the correction chain continues into code 2026-07-27 15:57:36 -07:00
30-gap-register.md docs(assessment): re-verify the Wave 0 amendments at main tip, and correct H-8d 2026-07-28 02:55:30 +00:00
31-hindrance-audit.md docs(assessment): re-verify the Wave 0 amendments at main tip, and correct H-8d 2026-07-28 02:55:30 +00:00
40-assessment.md docs(assessment): re-verify the Wave 0 amendments at main tip, and correct H-8d 2026-07-28 02:55:30 +00:00
50-execution-plan.md docs(assessment): the pre-push hook makes the same parity claim (R-14, N-3) 2026-07-27 17:37:58 -07:00
50-rulings.md docs(assessment): the pre-push hook makes the same parity claim (R-14, N-3) 2026-07-27 17:37:58 -07:00
README.md 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

README.md

docs/assessment/ — The Holistic Macro→Micro Assessment (2026-07-27)

A read-only, evidence-bearing assessment of CORE's cognitive-cycle design versus implementation fulfillment, conducted under docs/conceptualizing_engineering_mastery.md at forgejo/main @ 8927c563. Phases 0–5 change no runtime behavior, fix no defect, and decide nothing — they produce evidence and judgments for ruling. Phase 6 adds the execution plan built on them and the ruling packet they require.

Start here: 40-assessment.md — the synthesis (the verdict, the five frontiers, the recommended attack order). Then 50-execution-plan.md for what follows from it, and 50-rulings.md for what is waiting on a decision. The registers rank the work; the cards are the evidence base.

File / dir Phase What it is
00-scope-and-method.md — Charter, method, rules of engagement, phase/executor table
01-phase0-ground-truth.md 0 Corpus triage, the five unreconciled articulations, system-map recovery
02-layer-taxonomy.md 1 The two-axis taxonomy: 7 macro layers + 2 cross-cuts over 33 zones; the Candidate Register (CR-1…4); completeness criteria
03-card-schema.md 1 The card metadata schema: liveness ⊥ fitness, design ⊥ build, sabotage-tested evidence, verified_at stamps
10-layer-cards/ 2 Nine layer cards (M0–M6, MG, MV), every liveness label re-verified against code
04-phase2-findings.md 2 Stage-coverage audit; corrections to Phase 0; findings F-1…F-5
20-component-cards/ 3 Eight component cards: the four zero-subsystem zones + always-on, derivation organs, surface selection, attention
05-phase3-findings.md 3 Corrections C-1…C-5; findings F-6…F-10; the consolidated Phase-4 seed list
30-gap-register.md 4 The live gap register — 20 entries, 4 tiers, each with evidence + deciding authority (proposes superseding docs/gaps.md); four entries amended in Phase 6
31-hindrance-audit.md 4 Twelve hindrances with fitness verdicts and better homes; five candidates examined and cleared
40-assessment.md 5 The synthesis
50-execution-plan.md 6 The execution plan — five waves + five frontier tracks over every G/H entry, with the dependency gates and the risks. §0 carries seven corrections to the assessment found while sizing it
50-rulings.md 6 The ruling packet — R-1…R-14, each with evidence, options, a recommendation, and the exact diff that follows from each choice. Wave 0's deliverable

Maintenance contract (from §8 of the synthesis): a card whose verified_at falls behind a load-bearing arc is testimony, not evidence. Update cards when their subsystems move, or this directory becomes the next dead instrument it was built to replace.

Standing note: the PR #138 fabrication findings appear throughout as measured & pinned, fix held for ADR + ratification — recorded, never re-discovered, never fixed here, per explicit instruction.