spae-check

Check (SPAE)

When to use

• STATE.json reports phase: check.
• Cursor names active task.

Goal

• Compare active task implementation against PLAN.md Intent, Acceptance, and Verification.
• Route gaps to /fix or advance clear task.

Input

Read:

• .spae/current/STATE.json (consult references/STATE.md for field reference, directives, and phase snapshots)
• Active task section from .spae/current/PLAN.md (Intent, Acceptance, Verification)
• Source files and test logs scoped to active task

Workflow

1. GATE—Read .spae/current/STATE.json; confirm phase: check and active_task_id. Self-heal state drift: if tasks[active_task_id] reads "todo", correct it to "in_progress" and write STATE.json before proceeding. Halt on state drift: if tasks[active_task_id] reads "done", halt. Read active PLAN.md task section; confirm title, Intent, Acceptance, Verification. Halt on missing or malformed input; report and make no changes.
2. ORIENT—Verify active task; hand off to /fix, /build, or /verify. Leave source, tests, config, docs, PLAN.md, SPEC.md, task scope, and workstream completion untouched.
3. PLAN—List active-task Acceptance outcomes and Verification steps. Map evidence for declared Intent; scope source/test reads to active task. Never read SPEC.md.
4. ACT—Execute:
   • Run active-task verification steps and project checks. Without automation, inspect source, logs, or scripted probes for observable behavior.
   • Confirm every Acceptance outcome and Intent against evidence.
   • Label findings with exactly two tags:
     • Gap: unmet Acceptance, failed Verification, Intent mismatch, speculative abstraction, unrequested complexity, defensive bloat beyond task Scope, or a self-introduced cleanup violation per references/cleanup-guide.md. Include unmet item, file:line, expected vs actual, reproducible evidence. Blocks a clear result.
     • Observation: minor concern outside task scope, unrequested edge-case coverage, theoretical risk. Report only; never write to FIX.md or affect the verdict.
   • Draft gaps per references/FIX.md schema; consult references/prose-protocol.md.
5. VERIFY—Reconcile every Acceptance, Verification, and Intent against evidence. Clear verdict only with zero gaps. Confirm drafted FIX.md matches references/FIX.md structure.
6. PERSIST—Apply one verdict:
   • Gap found: create/overwrite .spae/current/FIX.md per references/FIX.md. Write STATE.json: phase: fix; preserve status, cursor, task registry, version, workstream. Active task stays in_progress.
   • Task clear, tasks remain: write STATE.json: mark active task done, advance cursor to next "todo" task, phase: build.
   • Final task clear: write STATE.json: mark active task done, retain cursor active task ID, phase: verify.
   • All branches: re-read STATE.json after writing; on a field mismatch, rewrite and re-read before REPORT.
7. REPORT—Emit result per directives. Template B after gap, D after clear nonfinal task, E after clear final task. Observations under Findings only.