Skip to content

backlog: close the demand-gate triage (#172 declined, #156 deferral confirmed) - #315

Merged
wshallwshall merged 1 commit into
mainfrom
w3-ledger-b
Aug 11, 2026
Merged

backlog: close the demand-gate triage (#172 declined, #156 deferral confirmed)#315
wshallwshall merged 1 commit into
mainfrom
w3-ledger-b

Conversation

@wshallwshall

Copy link
Copy Markdown
Collaborator

Closes the demand-gate triage: #172 declined, #156 deferral confirmed. Ledger only.

This is a follow-on to the previous ledger PR. That one merged at the SHA it was opened against; this
commit was authored on the same branch afterwards and did not travel with it, so it is routed
separately rather than left holding work on a local ref alone.

Verification

  • Merges cleanly onto main; the instrument was checked first against a known-conflicting branch.
  • Ledger re-derived with parse_items from this branch: live 244, open 184, archive 236 -- namespace
    480 conserved. No duplicates, no item declaring more than one status. Both rows present.
  • Status checker pointed at this branch's extracted file rather than a working tree.
  • Leak scan clean, negative control firing.

… confirmed

The last two rows. With these, EVERY demand-gate item in the ledger has been
ruled: nothing in that class is now waiting on a decision nobody has made.

#172 DECLINED, and the distinction is the point: the CODEC shipped and what is
declined is AUTO-EXTRACTION ON THE CONNECTOR. All six functions are exported from
the top-level package, so a Handler compresses or extracts in one line and binary
rides the store through the ADR 0028 carriage. The connector's gzip-only limit is
defended at three layers, and they are deliberate -- a gzip is one stream, a zip
is an ARCHIVE. Auto-extracting would put the ingest path in charge of deciding
which member is the message, on a partner file this project treats as untrusted,
with traversal entries and decompression bombs to adjudicate.

Two details establish the split was DESIGNED and not merely unfinished, and both
were checked rather than assumed: the decompress functions take a max_output_bytes
BOMB CEILING, and zip_compress takes a mapping of NAME to bytes -- so an outbound
zip needs an entry name only the feed author can choose. A connector could not
supply either. Left open, this item invites someone to remove three guards to
"finish" it, and what they would switch on is automatic extraction of partner
archives at the front door.

#156 deferral confirmed. Its trigger names an observation nobody can make yet --
operators reporting flapping the existing throttle does not damp -- which cannot
fire from analysis, only from watching real alerts. Building a deadband now means
choosing two threshold constants with no traffic to choose them from.

A CORRECTION TO THE RECORD, made because the instrument was mine. I previously
reported #156 as cited by ASVS cell 3.7.3. It is not: 3.7.3 is external-link
interstitials and same-origin assertions. My cross-reference matched a bare "#156"
inside that cell's text rather than a citation. Re-run against a "BACKLOG #N"
token, ZERO cells cite #156 or #172. A pattern that matches digits is not a
citation index -- the same blindness this ledger keeps finding in other people's
greps, found in mine.

Ledger: live 244, open 184, closed-in-live 60, archive 236, namespace 480
conserved. Status check run with --backlog against this tree, not the ambient one.
@wshallwshall
wshallwshall merged commit b52fd84 into main Aug 11, 2026
34 checks passed
@wshallwshall
wshallwshall deleted the w3-ledger-b branch August 11, 2026 00:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant