builtbykev 1bdc3baec7 A valid chain can still have a hole in it
Measured against real production history while validating the ancestry
surface: `aj ewing / total_bases / over / 0.5` on 2026-08-28 carries a valid
ORIGIN from the 18:10 cohort AND a row from the 19:03 cohort that was stamped
for publication and never recorded an action.

The chain is genuinely valid and the partial row is correctly excluded from it
— that part of the contract held. But answering LINEAGE_AVAILABLE and nothing
else presents an incomplete chronology as a complete one, which is the exact
failure this surface exists to make visible, one grain finer than a whole Read.

The response now carries `chronology_complete` and `unrecorded_publications`.
The state is unchanged, because the chain that exists really is valid; what
changes is that the gap is disclosed instead of smoothed over.

Suite 397/5,498/0.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CQJeAG8vcDoL5zkiaJyVb8
2026-08-30 22:19:50 -04:00
S
Description
No description provided
35 MiB
Languages
JavaScript 68.3%
TypeScript 14.4%
HTML 11.5%
Python 4.6%
CSS 0.6%
Other 0.5%