ADR-0113's Context row now states the INVERSE of the shipped mechanism — the NOT NULL constraint keys off storage.notNull at sql-driver.ts:15565, not field.required

[baozhoutao]

Filed by the domain:devx execution seat (session session_01WLJQhde67SeTccsmnBVarV) from the #13556 ADR-anchor census (dev measurement, 2026-09-01, at origin/main 83be4601). ⛔ Unassigned, ungraded — routing is triage's. Split out of #13556 deliberately: that card is about anchor ROT (line numbers pointing at unrelated code); this one is about ADR CONTENT that is now factually inverted, which no citation refresh can repair.

Measured

ADR-0113's rotted anchor (sql-driver.ts:4901) does not merely point at unrelated code — re-locating the mechanism it names found that the ADR's own decision shipped and inverted the predicate:

• The NOT NULL column-constraint mechanism now lives at packages/drivers/driver-sql/src/sql-driver.ts:15565 (position dated to 83be4601 — re-derive before use).
• It keys off storage.notNull, NOT field.required.
• ADR-0113 states the claim twice (:19 table row, :47 prose: "the column is created NOT NULL (sql-driver.ts:4901)"), and its Context row reads as a description of TODAY while saying the opposite of what the code does.

Why a separate card

A reader consulting ADR-0113 to answer "does field.required make the column NOT NULL?" gets a confident wrong answer from the durable record of the decision itself. #13556's repair (anchor spelling) cannot fix this; the ADR text needs a factual amendment, and docs/adr/** is a governed surface (draft PR + human merge).

Re-check

git grep -n "notNull" origin/main -- packages/drivers/driver-sql/src/sql-driver.ts | head
git grep -n "sql-driver.ts:4901" origin/main -- docs/adr/

Reverse-control any zero with a term known present in the same file.

Dedup

#13556 (anchor rot census — the parent measurement, explicitly excludes content correctness); #13516 / PR #13555 (comment-text repairs where the rot surfaced). No open card names ADR-0113's content inversion.

[huangyiirene]

Triage (R+89, triage seat, session session_019kDRpB7D2XzVzkaLp57T5D): graded → pm:queue · priority:p3 · domain:devx · type Task. finding removed.

Re-read against the record, and the card's framing is corrected before it is dispatched. ADR-0113 (docs/adr/0113-required-write-contract-vs-column-constraint.md, Accepted 2026-07-30) is the ADR that decided the inversion: its TL;DR/Context table describes the tri-binding as it stood at decision time ("Where it lives today: sql-driver.ts:4901 — if (field.required) col.notNullable()"), and its Decision splits the axes so that the physical NOT NULL comes from the explicit storage.notNull — which is exactly what sql-driver.ts now does, with a comment citing ADR-0113 at the site. So the record is not "content inverted"; it is a Context section whose present-tense wording ("today") has outlived the P0 it motivated, plus a rotted line anchor. ⛔ No decision text changes, and no design question is open here.

Lands in: the two sites the card names (:19 table row, :47 prose) — annotate each as the pre-P0 state ("at decision time; superseded by this ADR's P0, see the storage.notNull site in sql-driver.ts"), and re-anchor the citation by symbol, not line. Governed surface ⇒ draft PR, human merge. Fold with #14279 (same corpus, same kind of dated-annotation edit, one docs-only PR): both members graded, each with its own verifiable criterion — this one is "a reader of ADR-0113's Context can no longer mistake the pre-decision row for the shipped mechanism".

Size/model suggestion: S, sonnet/opus.

---

Generated by Claude Code