2026-10-16 — A status branch this checkout has never read that holds more than one read covers is shown as doubtful, continuity not verified: more was added than one read covers, the same as a branch read from a mark (spc-2610150728396006 step 3 fix round, build note 24 extended; decided by the facilitator on delegation). A first read that stopped at the walk limit could otherwise bury a live announcement under a thousand ended ones with no sign.

Frontmatter

.abcd/work/decisions/dcn-2610161100416718-a-status-branch-this-checkout-has-never.md
open on GitHub ↗ · commit history ↗

mentions3

• dcn-26101613204576502026-10-16 — A first read of a status branch that runs past the walk limit is shown as doubtful only while something beneath what it read could still stand: when the oldest commit it read does not read as an announcement, or was sent, by the time it carries, less than a day and an hour before the read (the longest life plus C9's one-hour slack), refining dcn-2610161100416718 (spc-2610150728396006 step 3 fix round 2, decided by the facilitator on delegation). Status branches only grow, so every new checkout's first read of a long-lived one passed the limit and showed a doubt for history that had all ended. The bound is the oldest commit's send time rather than its own expiry, since a commit beneath it, sent earlier with a longer life, can outlast it.
• dcn-26101617375712762026-10-16 — A first read of a status branch that runs past the walk limit is always shown as doubtful, continuity not verified, whatever times its commits carry, refining dcn-2610161320457650 and dcn-2610161100416718 (spc-2610150728396006 step 3 fix round 3, on review). Within the bounded walk no signal settles whether a line older than what the read took in can still stand, so the read cannot say that nothing beneath it is live.
• spc-2610150728396006sessions-announce-what-they-are-doing