Chapter 5.10 follows chapter 5.9, Task applicability by arm, and closes part 5, the task library; part 6, the reference part, begins with chapter 6.1, Glossary of campaign terms.
The retired suite used removal tasks whose patches could not be applied to the unguided control. The control had a different file layout from the documented reference, so the failed application left the comparison invalid. The ruling ended this suite and moved the campaign to additive tasks.
5.10.1 Archived removal tasks of the maintenance-task suite
The archive contains eight task folders for Project H, the project named H: H-M009, H-M013, H-M014, H-M015, H-M016, H-M017, H-M018, and H-M019. The archive contains the applicability, archive note, catalogue, readme, and realization records. The index records the same tasks as archived.
source: archive folder listing and task_index.csv (eight Project H rows with status archived)
The suite ran for run sets 011 to 029. The removal patch was applied to the documented reference and the stripped twin. It failed on the unguided control because that control used a different file layout. The failure meant that the control did not receive the removal task and that the comparison was invalid. source: operations/results-integrity/B0-scope-filter-finding.md section 7 third row, which the drafter confirms against run_index.csv
5.10.2 Falsifier tasks of the maintenance-task suite
A falsifier, a task intended to disprove a claim, is described in R2. The falsifier tasks were H-M009 and H-M014.
source: archive folder listing and task_index.csv (eight Project H rows with status archived)
H-M009 was the archived import-transposition task. It moved an import statement between files. H-M014 was the archived stale-sessions task. It removed code for stale sessions. Both were intended to show whether documentation made no difference. Their results could not repair the invalid control comparison.
source: archive folder listing and task_index.csv (eight Project H rows with status archived)
5.10.3 Checker status of the maintenance-task suite
Draft task records are held in the draft archive and void archive. Their checkers remain unproved, so the records are not registrable.
The paperless-ngx draft records are held in the withdrawn-ticket archive and superseded-ticket archive. Those records are withdrawn or superseded and are not registrable.
5.10.4 Project drafts of the maintenance-task suite
Project F has eighteen draft tasks in 4. Task Library/Project F/F-M001/ to F-M018/. Their checkers remain unproved.
source: P6 and P7
Project E has twelve draft tasks in 4. Task Library/Project E/E-M001/ to E-M012/. Their checkers remain unproved.
source: P6 and P7
5.10.5 Retired suite record of the maintenance-task suite
The ruling retired the removal-based suite. Its record is in Appendix A line 78. The ruling ended the patch-based comparison after the control application failed. The additive task design became the current design because its customer-language ticket can be applied to each arm without depending on a matching file layout.
source: Appendix A line 78