backlog: rule 13 demand-gate rows, file #1212 and #1213 - #314
Merged
Conversation
The owner worked through the remaining demand-gate surface item by item. Five declined, six deferrals confirmed with their triggers restated, one re-tiered, one split. Open items 188 -> 185 (the deferrals stay open by design). DECLINED (5). Each verified to have a working alternative in shipped code, or a trigger that cannot arise. Declining is reversible; re-filing costs one item. #94 #62 #64 -- the whole storage-efficiency cluster retires together. #62's win is a ~60% at-rest CONSTANT FACTOR with no correctness stake, against reopening ADR 0028's NUL-safe carriage decision where being wrong corrupts message bodies. A larger disk answers a constant factor. #64's only surviving role was indexing that cluster; it now indexes nothing. #179 -- and the reason is a correction to MY OWN objection, recorded because the method matters more than the outcome. I argued unbounded growth eventually outruns "buy a bigger disk". It does not, on any instance that matters: allow_unbounded_phi (#186a, ASVS 14.2.4) makes a PHI instance REFUSE TO START in prod unless both PHI-body windows are bounded. Reading the guard settled it; reasoning about growth did not. #180 -- with a consequence stated rather than left implicit: greenfield drain-before-cutover, discarding retained history AND audit, is now the shipped answer for backend promotion. That is a position, not an oversight. DEFERRALS CONFIRMED (6), each with what the banner previously failed to say: #141 the relay workaround places a hop OUTSIDE count-and-log and outside the forward-secrecy floor asserted at 12 sites -- a policy question, not demand. #105 its gate #313 is ABOVE the published #231 baseline BY DESIGN and is sound evidence; and the role layer IS wired, so "0 Action objects" is a pre-wiring measurement that must not be quoted as current state. #158 building it REQUIRES WIDENING FILE-1, the one-path-component cap that stops an attacker-controlled field writing outside the target directory. The banner read as a connector knob; it is a path-traversal control widening. #3 the 45M/day target does NOT imply it -- ~0.35 ev/s per connection, about 170x below the one-lane bound. The target is met by concentration. Also: the 2026-07-09 decline was OVERTURNED and must not be re-declined on the purity argument. #96 NOT demand-gated -- BUILD-GATED on an owner re-ratification (ADR 0074). It waits on the owner, not a customer, and its guard layer is buildable. #155 deferred by owner: build after more testing. RE-TIERED (1): #99 is RIG-BLOCKED, not demand-gated -- its own amendment already said "PROVISIONING, not code". Six items now wait on one lab rig. SPLIT (1): #78 keeps the persisted-definition model with its #26 adjacency stated; the NCPDP codec becomes #1213. FILED (2), both allocated with scripts/coord/alloc.ps1: #1212 bound PHI-body retention by default (60 days, not keep-forever). Owner requested after establishing the current default is 0 = KEEP FOREVER. It lands inside ASVS 14.2.4 and 14.2.7, both partial, and carries five traps -- the two that matter are that audit_days must STAY keep-forever by design, and that the change flips what an OMITTED setting means. #1213 NCPDP codec, the clean additive half of #78. Ledger, re-derived with parse_items: live 244, open 185, closed-in-live 59, archive 236, namespace 480 conserved. All three ledger gates pass.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rules 13 demand-gate rows: 5 declined, 6 deferrals confirmed with restated triggers, 1 re-tiered,
1 split. Ledger only -- no engine, IDE or webconsole code is touched.
BACKLOG #1212 #1213
Two declines that state their consequence rather than leaving it implicit
drain-before-cutover, discarding retained history and audit, is the answer for backend promotion.
That is a position, not an oversight, and it should surface wherever backend promotion is documented.
growth outruns "buy a bigger disk"; it does not, because
allow_unbounded_phimakes a PHI instancerefuse to start in production unless both PHI-body windows are bounded. Reading the guard settled it.
#1212 is the one to read
It bounds PHI-body retention by default. The current default is
0, which means keep forever. Itlands inside two ASVS requirements that are both partial, and carries five traps. Two matter most:
audit_daysmust stay keep-forever by design -- a tamper-evident chain against a multi-yearretention expectation -- so a sweep of "all the zero defaults" would convert a compliance property
into a bug.
Four rows previously routed for a ruling are now resolved
#141deferred and restated as a policy question, with the relay workaround's cost written into thebanner: that hop sits outside count-and-log and outside the forward-secrecy floor.
#178is a narrowlyscoped build -- a floor assertion on the one transport hop that lacked it, with the configurable
allow-list still deferred.
#158deferred, recording that building it would require widening theone-path-component cap that stops an attacker-controlled HL7 field writing outside the target
directory; the banner had read as a connector knob.
#105deferred, with its citation corrected ratherthan left implying a broken reference.
Verification
parse_itemsfrom this branch: live 244, open 185, closed-in-live 59,archive 236 -- namespace 480 conserved. No duplicates, no item declaring more than one status.
total describes the change under review.
main, with the instrument checked first against a known-conflicting branch.