SynAIpse Harness Execution Plan

When to use

Use when a slice spec is accepted and the user needs the implementation order before code changes.

Required inputs

• User request or routed handoff naming this stage.
• Current repository, branch, artifact, tracker, PR, validation, and session evidence when available.
• The previous-stage artifact when this stage depends on one.

Deliverables

• A stage result with schema_version, stage, status, evidence_refs, blocked_by, and next_stage.
• Exact validation status using pass, fail, or blocked.
• A handoff that names what is proven and what remains unproven.

Procedure