T-FTV3-runner-registry-v1
Status: closed/superseded · Impact: medium · Complexity: medium
D-VSLI-distributed-work-runner-architecture v1’s second half: the
folder-of-YAML runner registry with the implementation runner
registered, and the kind: stamp sweep so existing tasks carry
the field explicitly.
| Location | Role today |
|---|---|
apps/sdlc/lib/model/entities/task/implementation-ready.md | The implicit implementation-kind readiness contract; nothing declares it as a runner’s. |
apps/sdlc/skills/task-work/SKILL.md | Hard-codes the implementation workflow; no registry lookup. |
docs/planning/tasks/ | Existing tasks carry no kind:. |
Proposed
Section titled “Proposed”A runner registry under apps/sdlc/runners/ — one YAML per kind
declaring readiness contract, work-dispatch skill, expected
outputs, and lifecycle deviations (shape per D-VSLI’s starter). v1
registers only implementation, pointing at the existing
contract and skills; a loader validates registry entries. Sweep
kind: implementation onto existing open tasks for query
consistency. task-work / task-ensure-ready do NOT become
dispatchers yet — v1 is registry + declaration only.
Approach
Section titled “Approach”- Define the registry entry schema and loader (validated YAML).
- Author
apps/sdlc/runners/implementation.yamldeclaring today’s contract and skills. - Sweep
kind:onto existing non-closed tasks (deterministic; one commit). - Tests: loader rejects a malformed entry; the implementation entry resolves its declared paths.
Files to touch
Section titled “Files to touch”| Location | Kind | Change |
|---|---|---|
apps/sdlc/runners/implementation.yaml | new | The v1 runner declaration. |
apps/sdlc/lib/model/entities/task/ | modify | Registry loader + entry schema (final home per entity-code placement). |
docs/planning/tasks/ | modify | kind: stamp sweep on open tasks. |
Acceptance criteria
Section titled “Acceptance criteria”- AC-1: The registry loader parses the implementation entry and resolves its declared contract/skill paths.
- AC-2: A malformed registry entry fails validation with a named error.
- AC-3: Every non-closed task carries an explicit
kind:after the sweep.
Out of scope
Section titled “Out of scope”planning/researchrunners and dispatcher rewiring of task-work / task-ensure-ready — later D-VSLI phases.
Dependencies
Section titled “Dependencies”- T-JOXA-task-kind-field-and-leaf-dispatch — the field the registry keys on.
Discovery context
Section titled “Discovery context”- D-VSLI accepted at v1 scope (PR #1123).
Depends on
Section titled “Depends on”T-JOXA-task-kind-field-and-leaf-dispatch