Repository navigation

The ratchet consumer: an emit-clean frontier over a discovered roster, where an unmeasured subject is neither clean nor suspect - #9213

Merged

gunbai-bot[bot] merged 18 commits into

mainfrom

session/gentle-bee-495

Aug 26, 2026

Commits on Aug 25, 2026
- Rebuild the per-entry emission instrument as a .dag entry point
  
  Brian Searls
  and
  claude
  committed
  f9083ad
- Bind the execution subject, and require cargo's terminal message
  
  Brian Searls
  and
  claude
  committed
  500d298
- The emit population states whether it is the whole population
  
  Brian Searls
  and
  claude
  committed
  a42b245
- The ratchet consumer: an emit-clean frontier over a discovered roster, where an unmeasured subject is neither clean nor suspect
  
  gunbc-ci-auto-heal
  and
  claude
  committed
  8e95f46
- Hash the discovery policy into the roster digest; avoid two corpus-wide name collisions
  gunbc-ci-auto-heal
  committed
  fe4a98c
- Give the verdict-entry accessor its consumer: every verdict names its subject
  gunbc-ci-auto-heal
  committed
  3b62c9e
- Fix the one blocking diagnostic: a renamed fixture binding missed inside a list literal
  gunbc-ci-auto-heal
  committed
  fc06819
- Adopt the superseded contract: three-valued outcome, the enrolment wall as a construction, and both holes pinned by execution
  
  gunbc-ci-auto-heal
  and
  claude
  committed
  c56f7f1
- Hole 2's mechanism was wrong: a parse failure under a recognized header refuses LOUDLY
  
  gunbc-ci-auto-heal
  and
  claude
  committed
  84271e0
- Four stale sentences, not one: the corrected mechanism had not reached the strings that render it
  
  gunbc-ci-auto-heal
  and
  claude
  committed
  0c2d1b9
- Delete the FIPS 180-4 fork in sha256sum: consume the citation extdeps.crypto.hash owns
  
  gunbc-ci-auto-heal
  and
  claude
  committed
  200bfbd
- roster_identity had two declarers: a per-entry compile sees one, the floor sees both, so the collision was invisible to the check an author runs
  gunbc-ci-auto-heal
  committed
  80c479e
- Merge main
  gunbc-ci-auto-heal
  committed
  bdbd401
- The enrolment claim still asserted the pre-rename wording, so it went red on the branch where only the carrier had been swept
  gunbc-ci-auto-heal
  committed
  ae4c4d5
Commits on Aug 26, 2026
- Merge main
  gunbc-ci-auto-heal
  committed
  76d5f09
- Two commentary rows in String carriers: DESIGN 4c names that shape as misplaced data, and this branch added both
  gunbc-ci-auto-heal
  committed
  fe7d35b
- Name the reader as the owner when a population is unreadable, and declare the third hole
  
  gunbc-ci-auto-heal
  and
  claude
  committed
  98839cd
- Hold the seam's asymmetry, and stop the sample from reading as a proportion
  
  gunbc-ci-auto-heal
  and
  claude
  committed
  a1856a5

Navigation Menu

Repository navigation

The ratchet consumer: an emit-clean frontier over a discovered roster, where an unmeasured subject is neither clean nor suspect - #9213

The ratchet consumer: an emit-clean frontier over a discovered roster, where an unmeasured subject is neither clean nor suspect#9213
gunbai-bot[bot] merged 18 commits into
mainfrom
session/gentle-bee-495

Commits on Aug 25, 2026

Rebuild the per-entry emission instrument as a .dag entry point

Bind the execution subject, and require cargo's terminal message

The emit population states whether it is the whole population

The ratchet consumer: an emit-clean frontier over a discovered roster, where an unmeasured subject is neither clean nor suspect

Hash the discovery policy into the roster digest; avoid two corpus-wide name collisions

Give the verdict-entry accessor its consumer: every verdict names its subject

Fix the one blocking diagnostic: a renamed fixture binding missed inside a list literal

Adopt the superseded contract: three-valued outcome, the enrolment wall as a construction, and both holes pinned by execution

Hole 2's mechanism was wrong: a parse failure under a recognized header refuses LOUDLY

Four stale sentences, not one: the corrected mechanism had not reached the strings that render it

Delete the FIPS 180-4 fork in sha256sum: consume the citation extdeps.crypto.hash owns

roster_identity had two declarers: a per-entry compile sees one, the floor sees both, so the collision was invisible to the check an author runs

Merge main

The enrolment claim still asserted the pre-rename wording, so it went red on the branch where only the carrier had been swept

Commits on Aug 26, 2026

Merge main

Two commentary rows in String carriers: DESIGN 4c names that shape as misplaced data, and this branch added both

Name the reader as the owner when a population is unreadable, and declare the third hole

Hold the seam's asymmetry, and stop the sample from reading as a proportion