A composition edge: two rostered absence classes firing in sequence

dag/gunbc/recurring_failure_mode/predicate_vacuously_true_on_an_empty_domain.dag

@@ -101,6 +101,14 @@ data predicate_vacuously_true_on_an_empty_domain: RecurringFailureMode = Recurri
     "**THESE SIX ARE A RECORD AND NOT A REPAIR, and `a_written_row_is_not_a_firing_mechanism` requires that be said rather than left for a reader to work out.** After they land, nothing is harder to type: a universal over a possibly-empty domain is still the shortest thing to write, and the next author attending to their GOAL rather than to the class of their step will write one, exactly as the author of these did minutes after repairing the first three. The one construction repair, in (v), removes a single generator on a single route and is scoped to it. This row's existing trigger -- the positive denominator on every completion or coverage predicate -- is the repair for the rest, and it is NOT DISCHARGED by these specimens. They raise the demand for it; they do not meet it. The class stands UNREMEDIED. ",
 
     "**WHAT ACTUALLY CAUGHT FOUR OF THE FIVE WAS A HUMAN NOTICING A NUMBER LOOKED WRONG, AND THAT IS THE ABSENCE OF A MECHANISM RATHER THAN THE PRESENCE OF ONE.** A one-line capture file where a log was expected, a row count of 114 out of 114, a `comm` join reporting `none` on both sides: three implausible NUMBERS, noticed by an author who happened to be attending to the step rather than to the goal. No gate fired, no lens ran, no review found any of them. THREE SAVES IN ONE DAY BY THE SAME FACULTY MUST NOT BE READ AS A PRACTICE -- this row already records that the faculty predictably does not fire when the author is attending to the goal, which is the ordinary case and was the case in the instance that got closest to shipping. If these specimens are ever cited as evidence that authorial attention covers this class, THAT CITATION IS WRONG AND THIS SENTENCE IS THE REFUTATION. ",
+
+    "A COMPOSITION EDGE: THE FIRST LEG OF THIS ROW'S UPSTREAM-FAILURE GENERATOR HAS ITS OWN ROSTERED OWNER (2026-09-08). The paragraph above already owns the general sequence -- an upstream failure manufactures an empty domain and the downstream universal certifies it -- and an earlier draft of this receipt wrongly claimed that sequence as new, having grepped ONE sentence of this row instead of reading it. What is recorded here is narrower and is a RELATION rather than a class: on a measured incident the two legs are owned by DIFFERENT rostered rows firing in sequence. `git show <unknown revision>` EXITED 128 and yielded empty stdout; the exit status was discarded and the empty bytes were split into an empty sentence set; the universal `every sentence the authority gained appears in the projection` then held vacuously and certified a commit that was never read. [[empty_capture_read_as_clean_result]] owns the FIRST failure -- a refusing read consumed as content. This row owns the SECOND -- the universal over the resulting empty domain returning true. NEITHER CLASS ALONE EXPLAINS THE INCIDENT. The bad SHA is provenance for the specimen and nothing more: it explains why this particular read refused, and it changes no mechanism, recognition rule or repair, since wrong paths, wrong windows and refusing reads are all already covered. ",
+
+    "WHY LEG ONE IS CITED TO THE SPECIALIZATION AND NOT TO ITS PARENT, and an earlier draft of this paragraph got the reason wrong. It claimed the boundary was WHETHER THE READ SIGNALLED FAILURE, with the parent as the no-error case. THAT IS FALSE AND THE PARENT SAYS SO IN ITS OWN TEXT: [[absent_reads_identically_to_never_looked]] carries arms that are LOUD -- stderr, non-zero exit -- and its sharper statement is that THE SILENCE WAS MANUFACTURED BY THE READER'S FILTER. The false discriminator came from reading three specimen LABELS instead of the row, which is this ledger's own artifact-verification defect committed against its own roster. THE ACTUAL RELATION IS SPECIFICITY, stated by the specialization itself: [[empty_capture_read_as_clean_result]] is a specialization of that parent, narrowed to the mechanism where THE REFUSAL IS WELL-FORMED AND HONEST AND SIMPLY TRAVELS ON A CHANNEL NOBODY KEPT. This specimen matches that narrower mechanism -- exit 128 on a channel the reader discarded -- so it is cited to the specialization because the specialization is more specific, not because any test separates the two classes. ",
+
+    "THE TWO OBLIGATIONS FOR A COMPOSED CHAIN, AND ONE OF THEM IS CITED RATHER THAN RE-DERIVED. (1) PRESERVE OR REFUSE THE FAILED READ: inspect the exit status so an upstream fault cannot become content. (2) REQUIRE A POSITIVE DENOMINATOR ON THE ACTUAL CHECKED DOMAIN -- not a synthetic control, which proves only that the MATCHER discriminates and says nothing about whether the domain had members. THAT SECOND OBLIGATION IS ALREADY ROSTERED ON THIS ROW and this receipt does not restate it as its own: THIS ROW'S OWN NEXT-RUNG TRIGGER names the positive denominator as the capability -- every completion or coverage predicate requiring one, so a zero-size population refuses as not-yet-started rather than passing as settled. AND IT IS DELIBERATELY NOT CITED TO [[absent_reads_identically_to_never_looked]], which an earlier draft did: that row's denominator-and-control language establishes THAT THE READER REACHED ITS SUBJECT, which is a different fact at a different point in the pipeline from THE NON-EMPTINESS OF THE DOWNSTREAM PREDICATE'S ACTUAL CHECKED DOMAIN. Collapsing the two is how one obligation gets taken for the other and neither gets built. ",
+
+    "AND THE SPLIT IS ONLY HONEST WITH THIS SAID, because without it a reader takes one: EITHER GUARD ALONE WOULD HAVE PREVENTED THIS EXACT FALSE PASS. The positive denominator would have rejected the zero-sentence domain with the read failure still swallowed, and preserving the read would have refused before any domain existed. Both are required to repair the COMPOSED CHAIN rather than this instance of it -- the first preserves and LOCATES the original fault, the second closes vacuity from every other origin. It is not two guards for two holes; it is one hole closable twice, and a chain that needs both of its ends held. ",
   ],
 
   evidence: [],