Chapter 5.4 follows chapter 5.3, The retired seeded-defect design, and precedes chapter 5.5, Purpose of the hidden tier, within part 5, the task library.
A registered task package holds the records needed to give an agent a task and verify the result. Its contents include the ticket, the host-side record, hidden checks mapped to acceptance criteria, the verification command, confirmed surfaces, evidence probes, the retry-notice mapping, and the registration manifest. This package is in the additive task library. The other task folders are covered by reference. source: operations/site-ia/A6-page-briefs.md, section T3.
5.4.1 Package contents of the maintenance-task suite
The folder listing contains sixteen files and folders.
source: operations/site-ia/A6-page-briefs.md, section T3.
The package contains a ticket record, a readme record, a hidden-checks record, a verification guide, a surfaces record, an evidence data file, an evidence folder, a retry-feedback record, a task manifest, and hidden-check implementation files. The shared check core is present in the package and was absent from the architecture memo list on the date of the folder listing.
5.4.2 Ticket record of the maintenance-task suite
The ticket record states the work requested from the agent and the acceptance criteria. The readme record is the host-side record for the task package. It gives the package context and the operating information that accompanies the ticket.
5.4.3 Verification record of the maintenance-task suite
The verification guide gives the command for checking the agent work. The hidden-checks record maps host-side checks to the acceptance criteria. The checks are implemented in the hidden-check files. The hidden checks provide host verification after the agent has completed the work.
5.4.4 Surface record of the maintenance-task suite
The surfaces record documents the surfaces confirmed present for the task. It identifies the code files available for the requested change and gives the host a record of the intended edit area.
5.4.5 Evidence record of the maintenance-task suite
The evidence record records the package evidence. The evidence folder holds evidence probes and the task-run screenshots. The task-suite screenshots show the ticket, the verification command, and the resulting task state.
Figure D-T3-3. The evidence folder view for the package, showing the three task-suite screenshots that document the ticket, the verification command, and the resulting task state.
%% figure D-T3-3 flowchart TB subgraph g1[" "] n1["The evidence folder view for the package<br/>the three task-suite screenshots that document the ticket<br/>the verification command<br/>the resulting task state"] end
source: operations/site-ia/A3-diagram-specification.md
source: operations/site-ia/A6-page-briefs.md, section T3.
The package evidence screenshots.
5.4.6 Retry notice mapping of the maintenance-task suite
The retry-feedback record records the retry-notice mapping. It connects a retry notice with the error information and the action needed for another run.
5.4.7 Registration manifest of the maintenance-task suite
The registration manifest registers the task with the harness. It supplies the task metadata used to schedule and report the package.
5.4.8 Package diagram of the maintenance-task suite
Figure D-T3-1. The files of one task package on each side of the container boundary
%% figure D-T3-1 flowchart TB subgraph g1[" "] n1_1["TICKET.md"] --> n1_2["HOW_TO_VERIFY.md"] n1_2 --> n1_3["README.md"] n1_3 --> n1_4["HIDDEN_CHECKS.md"] end subgraph g2[" "] n2_1["SURFACES.md"] --> n2_2["evidence.json"] n2_2 --> n2_3["evidence/"] n2_3 --> n2_4["retry_feedback.json"] end subgraph g3[" "] n3_1["task_manifest.json"] --> n3_2["hidden_checks/checks.py"] n3_2 --> n3_3["hidden_checks/checks_core.py"] n3_3 --> n3_4["find"] end subgraph g4[" "] n4["Project H/H-M027/"] end n1_4 --> n2_1 n2_4 --> n3_1 n3_4 --> n4
source: operations/site-ia/A3-diagram-specification.md
source: operations/site-ia/A6-page-briefs.md, section T3.
The additive-suite task package.
5.4.9 Agent-visible files of the maintenance-task suite
Figure D-T3-2. The package files visible to the agent, separated from the host-side records and checks that remain outside the agent view.
%% figure D-T3-2 flowchart TB subgraph g1[" "] n1["The package files visible to the agent<br/>separated from the host-side records and checks that remain outside the agent view"] end
source: operations/site-ia/A3-diagram-specification.md
source: operations/site-ia/A6-page-briefs.md, section T3.
The files visible to the agent.
The agent receives the ticket, the host-side record, the confirmed surfaces, and the verification command. The host-side checks, evidence records, retry-notice mapping, and registration manifest remain host-side records. This division connects the requested work with its verification record while preserving the host checks. A previous and next navigation line, a compact link to adjacent pages, closes the page. A seeded defect, an intentionally planted flaw used to test a task workflow, appears in the package description. The seeded-defect design, a task design that uses an intentionally planted flaw to test a task workflow, appears in the navigation context.