Development record
itd-101 says the offline lint enforces no stale citation entries alongside no broken ones; the docs chapter says staleness only warns and never blocks an ordinary commit
itd-101 says the offline lint enforces no stale citation entries alongside no broken ones; the docs chapter says staleness only warns and never blocks an ordinary commit
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/shipped/itd-101-every-citation-abcd-publishes-is.md:14— "no broken entries, no stale entries, no cited URL without a receipt" - End B:
.abcd/development/brief/04-surfaces/10-docs.md:130— "an ordinary commit is never blocked by the calendar"
itd-101 lists stale entries among what the offline lint enforces against, next to broken entries and missing receipts. 10-docs records staleness as a warning past 180 days, promoted to a blocker only in the release-gate mode, so that an ordinary commit is never blocked by the calendar. The two disagree on whether a stale entry is refused by the lint a commit runs.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 655.
Grounds
- declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): the two ends do not conflict when read in full. Read in full, itd-101's acceptance criterion and decisions carry the same two-tier policy as 10-docs.md ('commits are never calendar-blocked'); the press release sentence is a summary of the release-gate end state.
Frontmatter
| id | iss-2610262036322416 |
|---|---|
| type | issue |
| lifecycle | wontfix |
| severity | minor |
.abcd/work/issues/wontfix/iss-2610262036322416-itd-101-says-the-offline-lint-enforces.md
open on GitHub ↗ · commit history ↗
References1
- itd-101**Every citation abcd publishes is provably alive and honestly labelled — and the gate that enforces it never flakes.** A cited reference page is only as trustworthy as its links, and links rot silently: pages retitle, URLs redirect, whole platforms announce their own shutdown. abcd splits citation validation across a deterministic gate and an explicit refresh. An offline lint family checks structure and source policy on every commit — footnote markers and definitions in bijection, URLs and DOIs well-formed, aggregator domains refused — with zero network in the gate. `abcd docs cite refresh` does the live fetching on demand and writes a committed baseline: per URL, the final resolved address, when it was last checked, and whether verification was automatic or manual — never how. Sources that block automated fetchers join a manual queue the maintainer clears link by link: printed as a checklist first, later as a generated, disposable checklist page that hands back a receipt file the verb ingests. The lint then enforces the baseline offline — no broken entries, no stale entries, no cited URL without a receipt, no citation whose recorded final address has drifted. The engine is native and dependency-free first; a specialist link checker can slot in later behind the same seam. "My release gate stays deterministic and my citations stay alive," said Kira, an open-source maintainer. "When a source needs human eyes, abcd hands me the exact list to click through and records that I did — not how I did it."related
mentions1
- dcn-26102711123305362026-10-27 — The product thinker accepted on 2026-10-27 the triage of the 1301 records the 2026-10-26 consistency pass filed. The duplicates, the records a later record already settles, the ones that are no contradiction and the one already fixed are closed with each reader's reason. Every other record gets its fix as its remedy, the rulings' accepted answers included, so a drain can take it. The 45 major records left open are deferred past v0.15.1, because the brief's single-home rewrite rewrites or removes most of the passages they quote. The person ruled the major rulings one at a time; the minor rulings take their recommended answers.