Chapter 5.8 follows chapter 5.7, The chained task sequences, and precedes chapter 5.9, Task applicability by arm, within part 5, the task library.
The verification records establish that the hidden checks respond to the requested behaviour. The absence sweep records failure when the behaviour is absent. The passability sweep records success when the behaviour is present. The first contact record and later verification records preserve the results of these checks.
5.8.1 Absence sweep of the maintenance-task suite
An absence sweep, a run that tests untouched builds for clean failure, establishes that a hidden check detects missing behaviour. It runs the registered task checks against the untouched frozen builds. The build directory is the working directory, and the build source comes first on the import path.
The sweep distinguishes a clean failure from a binding failure. A clean failure shows that the requested behaviour is absent. A binding failure shows that the check could not reach the intended behaviour. The absence sweep accepts only the clean failure.
The sweep covered sixteen tasks and found each task clean. source: _verification/README.md line 5
Per-task absence verdicts are recorded in the absence sweep file. source: absence-sweep.txt
5.8.2 Passability sweep of the maintenance-task suite
A passability sweep, a run that tests an honest implementation for successful checks, establishes that a hidden check can recognise the requested behaviour. A witness is an honest host-side implementation used to prove passability. It is written by hand after the checks are frozen and kept outside every measured build. It satisfies the ticket criteria without being an agent implementation.
The passability sweep runs the hidden checks against the witness implementation. A failed witness run identifies a check that requires correction because it is too strict or tests behaviour outside the ticket.
The passability sweep found every witness implementation passable. source: passability.txt
The passability.md file describes the sweep. The control-passability.txt file records the control run. Per-task passability verdicts are recorded in passability.txt, whose final verdict is pass. source: passability.txt
5.8.3 First contact record of the maintenance-task suite
First contact, the initial recorded run of the hidden checks against the witness implementations, preserves the outcome of each check with its supporting record. It provides the record used to examine an unexpected result and confirm the witness implementation.
The first-contact.md file records the witness results for the task set. Its entries show the initial outcomes and connect each result to the relevant witness patch.
5.8.4 Re-score and invalidation records
The re-score record preserves a later check after a correction. The invalidation record preserves the decision to withdraw a result when a flaw affects the check.
The re-score records preserve the first and later re-score reviews. The invalidation record preserves the invalidation review. The witness-patches folder contains the host-side changes used by the records.
5.8.5 Verification figures of the maintenance-task suite
Hidden check validation through witness passability and absence detection.
Figure sweep-results. A comparison of the passability sweep record with the absence sweep record for the task set
%% figure sweep-results flowchart LR subgraph g1[" "] n1["A comparison of the passability sweep record with the absence sweep record for the task set"] end
source: operations/site-ia/A3-diagram-specification.md
Sweep results from the passability and absence records.
Figure september-records. A record flow connecting first contact with the re-score and invalidation records
%% figure september-records flowchart LR n1["A record flow connecting first contact with the re-score and invalidation records"]
source: operations/site-ia/A3-diagram-specification.md
Verification records for first contact, re-score, and invalidation.