Chapter 5.1 opens part 5, the task library, after part 4, the profile library, and precedes chapter 5.2, Construction of a maintenance task.
A task, a maintenance change presented to an agent, is initiated by a ticket, a user request for work. The library map covers the naming convention, task runtime, registration process, and indexed status of each task. source: operations/site-ia/A6-page-briefs.md, section T0.
5.1.1 Task scroll sequence of the maintenance-task suite
A ticket enters the agent view. The agent produces a change. The harness runs the visible checks and then the hidden tier. The result enters the task record.
Figure D-T0-1. The construction of one maintenance task from the customer ticket to its proven hidden checks
%% figure D-T0-1 flowchart TB subgraph construction["Task construction"] n1_1["4. Task Library/Project H/H-M027/TICKET.md"] --> n1_2["Project H/README.md"] n1_2 --> n1_3["step"] n1_3 --> n1_4["step"] n2_1["HASP Task Design/gates/task_realism_gate.md"] --> n2_2["task_index.csv"] n2_2 --> n2_3["prompt_vagueness"] n2_3 --> n2_4["invariant_density"] n3_1["search_directness"] --> n3_2["blast_radius"] n3_2 --> n3_3["hidden_acceptance_pressure"] n3_3 --> n3_4["repair_pass_risk"] n4_1["human_realism"] --> n4_2["task_scoring_rubric.md"] n4_2 --> n4_3["HASP Task Design/manifests/task_registration_manifest_template.json"] n4_3 --> n4_4["target_variant"] n5_1["step"] --> n5_2["designer"] n5_2 --> n5_3["reviewer"] n5_3 --> n5_4["realizations"] n6_1["gate_outcome"] --> n6_2["freeze"] n6_2 --> n6_3["H-M027/SURFACES.md"] n6_3 --> n6_4["H-M027/HIDDEN_CHECKS.md"] end subgraph checks["Hidden checks"] n7_1["4. Task Library/PROBE_AUTHORING.md"] --> n7_2["_hidden_lib/README.md"] n7_2 --> n7_3["H-M027/hidden_checks/checks_core.py"] n7_3 --> n7_4["hidden_checks/checks.py"] n8_1["LapFamilyDriver"] --> n8_2["ControlDriver"] n8_2 --> n8_3["_hidden_lib/fiveb_probe.py"] n8_3 --> n8_4["fiveb_schema.py"] n9_1["fiveb_leniency.py"] --> n9_2["fiveb_judge.py"] n9_2 --> n9_3["fiveb_browser.py"] n9_3 --> n9_4["fiveb_handoff.py"] n10_1["H-M027/retry_feedback.json"] --> n10_2["H-M027/task_manifest.json"] n10_2 --> n10_3["present"] n10_3 --> n10_4["type"] n11_1["script"] --> n11_2["Project H/_verification/witness-patches/"] n11_2 --> n11_3["_verification/absence-sweep.txt"] n11_3 --> n11_4["step"] n12_1["run_checks()"] --> n12_2["classify()"] n12_2 --> n12_3["_verification/passability.md"] n12_3 --> n12_4["passability.txt"] n13_1["step"] --> n13_2["step"] n13_2 --> n13_3["1. Harness/config/hidden_judge.json"] n13_3 --> n13_4["HOW_TO_VERIFY.md"] n1_4 --> n2_1 n2_4 --> n3_1 n3_4 --> n4_1 n4_4 --> n5_1 n5_4 --> n6_1 n6_4 --> n7_1 n7_4 --> n8_1 n8_4 --> n9_1 n9_4 --> n10_1 n10_4 --> n11_1 n11_4 --> n12_1 n12_4 --> n13_1 end n1_3 -- "HASP Task Design/prompts/task-designer.md" --> n1_3_reference["reference"] n1_4 -- "prompts/task-reviewer.md" --> n1_4_reference["reference"] n5_1 -- "variant_freeze_hash" --> n5_1_reference["reference"] n11_4 -- "1. Harness/scripts/verify_task_absence.py" --> n11_4_reference["reference"] n13_1 -- "control-passability.txt" --> n13_1_reference["reference"] n13_2 -- "_hidden_lib/fiveb_judge.py" --> n13_2_reference["reference"]
source: operations/site-ia/A3-diagram-specification.md
source: operations/site-ia/A6-page-briefs.md, section T0.
The task scroll sequence from ticket to hidden tier.
5.1.2 Directory layout of the maintenance-task suite
The task library is arranged by project, with task folders holding the material needed for the ticket, execution, checks, and record. Project folders distinguish the task families and their status.
Figure D-T0-2. The task packages, the shared library, the design kit, and the archive
%% figure D-T0-2 flowchart TB subgraph g1[" "] n1_1["Project H/H-M020"] --> n1_2["H-M036"] n1_2 --> n1_3["SEQUENCE-1-work-item-checklist.md"] n1_3 --> n1_4["SEQUENCE-2-mention-notifications.md"] end subgraph g2[" "] n2_1["_hidden_lib/"] --> n2_2["HASP Task Design/"] n2_2 --> n2_3["Project H/_verification/"] n2_3 --> n2_4["Project H/_archive/"] end subgraph g3[" "] n3_1["Project F/"] --> n3_2["Project E/"] n3_2 --> n3_3["Project H/README.md"] end n1_4 --> n2_1 n2_4 --> n3_1
source: operations/site-ia/A3-diagram-specification.md
source: operations/site-ia/A6-page-briefs.md, section T0.
The folder map of the task library.
5.1.3 Task suite map of the maintenance-task suite
The shared task suite map shows the relationship among the task families and their maintenance paths.
The shared task suite map.
5.1.4 Task index of the maintenance-task suite
The index contains 55 data rows and fifteen columns, with seven difficulty factors among the columns. source: task_index.csv columns project_id and status
The index contains sixteen registered and one draft Project H units. source: task_index.csv columns project_id and status
The index contains eight archived Project H tasks. source: task_index.csv columns project_id and status
The index contains ten draft and eight superseded Project F tasks. source: task_index.csv columns project_id and status
The index contains twelve draft Project E tasks. source: task_index.csv columns project_id and status
5.1.5 Naming convention of the maintenance-task suite
A task name identifies its project and task type. The identifier remains stable when the task structure changes. The harness uses the identifier for lookup, while the name supports human reading.
5.1.6 Runtime anatomy of the maintenance-task suite
A task package contains the ticket, the agent-facing checks, the hidden checks, the evidence, the manifest, a record of package settings, and the executable grader. The agent receives the ticket and visible checks. The harness runs the visible and hidden checks, records the result, and retains the evidence.
5.1.7 Task package approval discipline
Registration, the approval step that admits a task package, requires a manifest, a record of package settings, including the difficulty band, status, and hidden-scoring record. A task enters a measured run after its folder carries a valid registration record that points to an executable grader. The admission gate checks the starting tree before an agent begins.
5.1.8 Project H status of the maintenance-task suite
Project H contains the live additive maintenance tasks and its archived removal-based tasks. The index records the registered, draft, and archived states.
5.1.9 Project F status of the maintenance-task suite
Project F contains draft and superseded maintenance tasks. The index records the status for each task.
5.1.10 Project E status of the maintenance-task suite
Project E contains draft maintenance tasks. The index records the status for each task.