Skip to content

T-HQ5L-relax-the-task-contract-files-to-touch-to-areas-today-to

State: closed/done · Impact: high · Complexity: large

The task implementation-ready contract’s “Files to touch” table (exact paths, a new/modify/delete Kind, a mandatory delete-reference-enumeration rule) and its “Today” | Location | Role today | table both resolved against the filesystem, disqualifying a task whose cited path had moved even when the task’s substance was still sound — busywork that fought the plan’s own goal of a mostly-autonomous overnight loop.

TaskSchema/TaskReadyContract were at schema version 6. “Files to touch” was a required-shape table with path-existence resolution; “Today” required a | Location | Role today | table. Both were routinely the first thing to go stale as code moved.

Schema version 7: “Files to touch” becomes “Areas” (| Area | Note |, advisory, no resolution disqualifier — a cited area never has to resolve to an existing path); “Today” becomes optional free-form prose with no required shape and no path-existence check. The claim resolver for collision avoidance works at area/directory granularity. Goal, acceptance criteria, and out-of-scope stay strict. A v6-to-v7 migration transform reshapes every existing task.

  1. Added v6-to-v7.ts to lib/model/entities/task/migrations/, converting a “Files to touch” table into “Areas” and relaxing “Today“‘s required shape.
  2. Updated TASK_BODY in schema.ts (schema version 7) and the birth/ready contracts to reflect the renamed, relaxed sections.
  3. Ran entities-migrate across the task corpus, touching 814 files.
  4. Finished the rename across tests, docs, and the local task-work skill/hook that referenced the old section name.
AreaNote
solutions/ontological/lib/model/entities/task/Schema v7, TASK_BODY, v6-to-v7 migration
docs/planning/tasks/Corpus-wide migration (814 files)
solutions/ontological/skills/task-work/Areas rename in the local hook/skill prose
  • AC-1: TaskSchema.SCHEMA_VERSION is '7' and TASK_BODY names the areas section “Areas”, not “Files to touch”.
  • AC-2: No task file under docs/planning/tasks/ contains a “Files to touch” heading.
  • AC-3: sdlc entities audit --strict reports zero schema-version-drift findings on the task corpus.
  • none
  • none

← Back to Tasks