Context
PR #16752 (merged 3fdab7eff6) landed ADR 0038, whose Amends set grew during review from 0020/0026 to 0020/0026/0034 (RA-1: the accepted shell-specific record had to carry the amendment at its retrieval statements). The ADR 0031 §2 seam-table row for 0038 was authored before that growth and still reads amends 0020/0026. Receipt: the non-blocking note in the approving review on PR #16752 — "ADR 0031 shorthand still says ADR 0038 amends 0020/0026 while ADR 0038 correctly names 0034 as a third amended authority."
The Problem
The composition record's Parent column is the cold-read amendment map. A missing 0034 edge tells a future session the shell record is un-amended — exactly the retrieval-statement staleness class RA-1 was about, one hop further out. lint-adr-seam-table checks id-presence in both directions, not Parent-cell accuracy, so nothing mechanical will catch the drift.
The Architectural Reality
learn/agentos/decisions/0031-target-architecture-composition.md §2, the 0038 row: | 0038 | Body ↔ Brain seam | FM client topology: … | amends 0020/0026 |. ADR 0038's Amends attribute row and §3.1–§3.3 name three amended records: 0020 §3+§4 (sentence rewritten in place), 0026 §2.7 (restartAgent fold executed), 0034 §2.1+§2.6.4 (hosting frame + dev/prod dichotomy re-scoped).
The Fix
One cell in the 0038 row of 0031 §2: amends 0020/0026 → amends 0020/0026/0034.
Acceptance Criteria
Out of Scope
Any other 0031 content; teaching the seam lint Parent-cell semantics (its own ticket if ever warranted — the lint's contract is id-presence by design).
Decision Record impact
aligned-with ADR 0038 (keeps ADR 0031's composition record current; no ADR authority changed).
Related
PR #16752 · #16747 (the merged D1 carrier) · ADR 0038 §3.3.
Live latest-open sweep: checked latest 20 open issues at 2026-08-08T23:11Z; no equivalent found. A2A herd-window sweep (status: all, limit 30): no competing claim — the scope was offered claimable in MESSAGE:f01ba1f1 and stayed unclaimed.
Origin Session ID: e676cd5d-52ce-4d38-89ab-a4621c88a382
Context
PR #16752 (merged
3fdab7eff6) landed ADR 0038, whose Amends set grew during review from0020/0026to0020/0026/0034(RA-1: the accepted shell-specific record had to carry the amendment at its retrieval statements). The ADR 0031 §2 seam-table row for 0038 was authored before that growth and still readsamends 0020/0026. Receipt: the non-blocking note in the approving review on PR #16752 — "ADR 0031 shorthand still says ADR 0038amends 0020/0026while ADR 0038 correctly names 0034 as a third amended authority."The Problem
The composition record's Parent column is the cold-read amendment map. A missing 0034 edge tells a future session the shell record is un-amended — exactly the retrieval-statement staleness class RA-1 was about, one hop further out.
lint-adr-seam-tablechecks id-presence in both directions, not Parent-cell accuracy, so nothing mechanical will catch the drift.The Architectural Reality
learn/agentos/decisions/0031-target-architecture-composition.md§2, the 0038 row:| 0038 | Body ↔ Brain seam | FM client topology: … | amends 0020/0026 |. ADR 0038's Amends attribute row and §3.1–§3.3 name three amended records: 0020 §3+§4 (sentence rewritten in place), 0026 §2.7 (restartAgent fold executed), 0034 §2.1+§2.6.4 (hosting frame + dev/prod dichotomy re-scoped).The Fix
One cell in the 0038 row of 0031 §2:
amends 0020/0026→amends 0020/0026/0034.Acceptance Criteria
amends 0020/0026/0034.node ai/scripts/lint/lint-adr-seam-table.mjsis green.Out of Scope
Any other 0031 content; teaching the seam lint Parent-cell semantics (its own ticket if ever warranted — the lint's contract is id-presence by design).
Decision Record impact
aligned-with ADR 0038 (keeps ADR 0031's composition record current; no ADR authority changed).
Related
PR #16752 ·
#16747(the merged D1 carrier) · ADR 0038 §3.3.Live latest-open sweep: checked latest 20 open issues at 2026-08-08T23:11Z; no equivalent found. A2A herd-window sweep (status: all, limit 30): no competing claim — the scope was offered claimable in MESSAGE:f01ba1f1 and stayed unclaimed.
Origin Session ID: e676cd5d-52ce-4d38-89ab-a4621c88a382