Chapter 5.9 follows chapter 5.8, The witness and the verification records, and precedes chapter 5.10, The retired removal suite and the draft tasks for other projects, within part 5, the task library.
A maintenance task needs a substrate, the frozen surface on which it operates. The substrate must be present on an arm before the task can run. The applicability record maps each task to the arms that can host it. The corpus guard checks that the task is absent from the untouched build before agent work begins. The two-way test checks absence on untouched trees and passability on a witness implementation. source: operations/site-ia/A6-page-briefs.md, section ”# T8. Task applicability by arm.”
5.9.1 Task substrate and applicability record
The applicability record determines whether a task is runnable, conditionally runnable, or excluded for an arm. An absent substrate excludes the task from that arm. A conditional entry records a qualification that the arm must satisfy before the task is admitted. The record therefore keeps task assignment separate from the result produced after work.
The retired suite record is the source for the applicability decisions represented here. The other project record covers the paperless-ngx surfaces, so its tasks do not have missing-substrate exclusions.
source: operations/site-ia/A6-page-briefs.md, section ”# T8. Task applicability by arm.”
5.9.2 Corpus guard of the maintenance-task suite
The corpus guard runs the hidden checks against the untouched build before agent work. It distinguishes a failed check, which demonstrates absence, from a crash caused by a broken binding. A crash cannot establish absence. The guard records the reason and the verdict for each checked tree.
The absence verifier performs the absence and passability checks. The feature-base materializer supplies the feature bases used for the checked trees. The paths named in an earlier page section are unresolved because the files have never existed. The guard that landed is the absence and witness check, with feature bases materialized by the materializer.
source: operations/site-ia/A6-page-briefs.md, section ”# T8. Task applicability by arm.”
5.9.3 Two-way checker test of the maintenance-task suite
The absence side requires every hidden check to fail on the untouched tree without a crash. The passability side runs the same checks on an honest witness implementation made after the checks were frozen. A checker passes this test only when it distinguishes the untouched state from a working implementation.
The test also keeps the hidden checks within the ticket. A hidden check may retest a stated criterion with a fresh input. It may not add a requirement absent from the ticket. This makes the checker a test of the requested behavior instead of a test for a particular implementation shape.
source: 5. Experiment/6. The Task Suite.md; 5. Experiment/ANALYSIS.md
5.9.4 Applicability record figure of the maintenance-task suite
The retired suite applicability matrix records task status across the documented reference, stripped twin, and independent control arms.
5.9.5 Corpus guard figure of the maintenance-task suite
Figure fig-guard. A flow diagram of the corpus guard, showing hidden checks on untouched trees, failure classification, and the witness passability check.
%% figure fig-guard flowchart TB subgraph g1[" "] n1["A flow diagram of the corpus guard<br/>hidden checks on untouched trees<br/>failure classification<br/>the witness passability check"] end
source: operations/site-ia/A3-diagram-specification.md
The corpus guard flow for absence and witness passability.