core-labs/core
core-labs/core
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity

docs(assessment): re-verify the Wave 0 amendments at main tip, and correct H-8d

Browse source 
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.
This commit is contained in:
Claude 2026-07-28 02:13:59 +00:00
parent 0c11b53083
commit 635f248834
No known key found for this signature in database
3 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/assessment/30-gap-register.md
View file

@ -3,7 +3,7 @@
**Assessor:** Fable 5 (Phase 4) · **Verified at:** `8927c563` (2026-07-27)
**Standing:** This is CORE's first *live* gap register since `docs/gaps.md` closed its 26th entry. Proposal (for ruling): this register supersedes `docs/gaps.md`, which is marked historical; two dead registers plus a live one is worse than one live one.
**Discipline:** A gap is an *absence the telos requires filled* with no explicit deferral ruling. Deferred-with-ruling is not a gap (scripture content is the model). Every entry carries evidence, its **deciding authority**, and a leverage rank. The register decides nothing.
**Amended:** 2026-07-27 at `ed06dd64` (Opus 5, Phase 6). Four entries carried claims that code, workflows, and an ADR's own supersession banner falsify. Each amendment is marked **[AMENDED N-x]** inline and derived in [`50-execution-plan.md`](50-execution-plan.md) §0: **G-5** (the soak ran and passed; the pins run twice a day), **G-7** (the orphan scan was an artifact; the mechanism is respecified), **G-8** (28 flags, not 17), **G-10** (the engineering blocker was discharged 2026-07-26). G-19 gains a note: its exposure is already pinned in-repo.
**Amended:** 2026-07-27 at `ed06dd64` (Opus 5, Phase 6) · **re-verified 2026-07-28 at `797ebad5`** — every amended claim below was re-measured against code at the current tip before landing, and all held (suite sizes 23/13 with the same ten-file delta and no CI-only file; `full = ("tests/",)`; 32 `RuntimeConfig` booleans, 28 off; the daemon flag set unchanged; ADR-0264 §4.1's supersession banner in place; 18 `resolve_promotable_*` organs). Four entries carried claims that code, workflows, and an ADR's own supersession banner falsify. Each amendment is marked **[AMENDED N-x]** inline and derived in [`50-execution-plan.md`](50-execution-plan.md) §0: **G-5** (the soak ran and passed; the pins run twice a day), **G-7** (the orphan scan was an artifact; the mechanism is respecified), **G-8** (28 flags, not 17), **G-10** (the engineering blocker was discharged 2026-07-26). G-19 gains a note: its exposure is already pinned in-repo.
---

4
docs/assessment/31-hindrance-audit.md
View file

@ -5,7 +5,7 @@
Ranked by leverage (cognitive/structural load removed ÷ effort), per the AGENTS.md protocol — not by ease.
**Amended:** 2026-07-27 at `ed06dd64` (Opus 5, Phase 6). **H-12 added** (the two smoke gates have diverged). **H-8 gains a fourth instance**, located inside the source rather than the documents. **H-1 gains a note**: its exposure is already pinned. Derivations in [`50-execution-plan.md`](50-execution-plan.md) §0.
**Amended:** 2026-07-27 at `ed06dd64` (Opus 5, Phase 6) · **re-verified 2026-07-28 at `797ebad5`** (H-12's ten-file delta re-measured and unchanged; H-8d's wording corrected on re-verification — see the entry). **H-12 added** (the two smoke gates have diverged). **H-8 gains a fourth instance**, located inside the source rather than the documents. **H-1 gains a note**: its exposure is already pinned. Derivations in [`50-execution-plan.md`](50-execution-plan.md) §0.
---
@ -61,7 +61,7 @@ Ranked by leverage (cognitive/structural load removed ÷ effort), per the AGENTS
## H-8 · The record contradicts the code at three load-bearing points
**Verdict:** `wrong-solution` as *record-keeping* — divergence that reasoners inherit · **Layers:** governance
**Evidence:** (a) ADR-0146 rejects the daemon shape and places *"cross-process file locking, daemon synchronization, and signal handling"* out of scope; `chat/always_on_daemon.py` ships all three (`fcntl.flock` single-instance lock, SIGINT/SIGTERM, load-time identity guard) and is unowned. (b) ADR-0252's headline "34 organs" has no reproducible basis (18 `resolve_promotable_*` entry organs at the ratification commit *and* at `ed06dd64`; ~32 modules). (c) `architecture-assessment-verification-2026-07-25.md` asserts accrual "is enabled by the production L10 process"; the flag set says otherwise. **(d) — added Phase 6, and it is inside the code.** `core/config.py`'s docstring for `accrue_realized_knowledge` states *"the production L10 process enables it alongside `persist_session_state`"*, and the docstring for `consolidate_determinations` states the same about *"`accrue_realized_knowledge` + `persist_session_state`"*. `CONTINUOUS_LIFE_CONFIG_FLAGS` (`chat/always_on_daemon.py:45-49`) contains neither claim's subject: it forces `persist_session_state`, `consolidate_determinations`, `strict_identity_continuity`, and **not** `accrue_realized_knowledge`.
**Evidence:** (a) ADR-0146 rejects the daemon shape and places *"cross-process file locking, daemon synchronization, and signal handling"* out of scope; `chat/always_on_daemon.py` ships all three (`fcntl.flock` single-instance lock, SIGINT/SIGTERM, load-time identity guard) and is unowned. (b) ADR-0252's headline "34 organs" has no reproducible basis (18 `resolve_promotable_*` entry organs at the ratification commit *and* at `ed06dd64`; ~32 modules). (c) `architecture-assessment-verification-2026-07-25.md` asserts accrual "is enabled by the production L10 process"; the flag set says otherwise. **(d) — added Phase 6, and it is inside the code.** `core/config.py`'s docstring for `accrue_realized_knowledge` states *"the production L10 process enables it alongside `persist_session_state`"*, and the docstring for `consolidate_determinations` states the same about *"`accrue_realized_knowledge` + `persist_session_state`"*. `CONTINUOUS_LIFE_CONFIG_FLAGS` (`chat/always_on_daemon.py:45-49`) forces `persist_session_state`, `consolidate_determinations`, `strict_identity_continuity`, and **not** `accrue_realized_knowledge` — so the first docstring is false outright, and the second is false in its *"alongside `accrue_realized_knowledge`"* clause. *(Stated precisely on the 07-28 re-verification: an earlier draft of this entry said the flag set "contains neither claim's subject," which is wrong — it does contain `consolidate_determinations`. The false clause, in both docstrings, is the one naming the accrual flag as co-enabled. A third comment, on `persist_session_state:283`, makes the same shape of claim and is **true**.)*
**Why it hinders:** demonstrated, not hypothetical — this assessment's own Phase 0 inherited a stale-record error, and the 2026-07-25 doc (itself a *corrective* document) introduced one. Every divergence is a future wrong analysis. Instance (d) is the sharpest: it is one layer *below* the documents, where a reader checking the code against the docs would stop and believe.
**Better home:** four amendments — ADR-0146 addendum owning the daemon (drafted in `50-rulings.md` R-12a); ADR-0252 basis footnote (drafted, R-12b); a correction note on the 07-25 doc; and the two docstrings corrected or the flag added, per R-3.
**Authority:** docs PRs + ruling signatures (R-12 for the two ratified ADRs, R-3 for the docstrings).

2
docs/assessment/40-assessment.md
View file

@ -2,7 +2,7 @@
**Phase 5 synthesis · Fable 5 · 2026-07-27 · verified at `forgejo/main` @ `8927c563`**
**Method:** `docs/conceptualizing_engineering_mastery.md`, applied per `00-scope-and-method.md`. Everything below is traceable to a card or register entry; nothing below is new evidence.
**Amended:** 2026-07-27 at `ed06dd64` (Opus 5, Phase 6) — sizing the execution plan produced seven corrections, four of which touch statements made here. They are applied inline and marked **[AMENDED N-x]**; the derivations are in [`50-execution-plan.md`](50-execution-plan.md) §0. The chain in §8 continues: *nothing in it was ever caught by re-reading documents.*
**Amended:** 2026-07-27 at `ed06dd64` (Opus 5, Phase 6) · **re-verified 2026-07-28 at `797ebad5`** — sizing the execution plan produced seven corrections, four of which touch statements made here. They are applied inline and marked **[AMENDED N-x]**; the derivations are in [`50-execution-plan.md`](50-execution-plan.md) §0. The chain in §8 continues: *nothing in it was ever caught by re-reading documents.*
---