T-Y9RS-the-implementation-process-registered-as-data-in-processes
State: planning/proposed · Impact: medium · Complexity: medium
With the source, the steps, and the driver in place, the implementation kind is a registration record, not Rust.
Proposed
Section titled “Proposed”solutions/ontological/engine/processes.json registers implementation as preflight-worktree,
implement (agent), quality, sync, and pr-open, with awaits_external: pr-merge. foreman validate
accepts it. Lease payload parity with the TypeScript service is pinned by a fixture.
Acceptance criteria
Section titled “Acceptance criteria”- AC-1:
foreman validate --root solutions/ontological/enginepasses on the registration. - AC-2: The parity fixture fails if either side changes the lease payload shape.
Out of scope
Section titled “Out of scope”- Review and planning kinds.
Dependencies
Section titled “Dependencies”- T-I1SJ-sdlc-work-run-step-preflight-worktree-quality-sync-and-pr
- T-OKV9-claude-code-agent-driver-and-the-sdlc-agent-call-verb
Depends on
Section titled “Depends on”T-I1SJ-sdlc-work-run-step-preflight-worktree-quality-sync-and-pr, T-OKV9-claude-code-agent-driver-and-the-sdlc-agent-call-verb