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
- Restate the active repo, branch, requested stage, and available evidence.
- Check the previous-stage artifact or explain why it is not required.
- Perform only the work owned by execution-plan.
- Record evidence refs and classify each lane as pass, fail, blocked, or not_checked.
- Emit the next-stage handoff to work or a blocker with the smallest recovery step.
Validation
Fail fast: stop at the first failed required gate, classify the blocker, and do not proceed to downstream stages until the failure is resolved or explicitly waived. Run the smallest relevant local check for changed files; for package-level changes, run plugin validation and SDK proof commands from the repository wrapper.
Handoff
Return the stage artifact or blocker, then hand off to work only after this stage's exit criteria are satisfied.
Failure modes
- Missing previous-stage artifact: block and request or create the required artifact through the owning stage.
- Conflicting evidence lanes: route to reconcile.
- Repeated failure or durable learning: route to reinforce.
- Requested action exceeds authority: block with the required authorization.
Gotchas
Do not use this stage to skip the lifecycle, merge evidence lanes, mutate external systems without explicit authorization, or complete another stage's exit criteria.
Similar legacy names may exist in caches or older Harness Engineering packages; do not expose them as SynAIpse active skills.
A local artifact can explain work, but it does not prove remote PR, CI, tracker, or deployment state.
If multiple stages seem plausible, route to sy-reframe instead of doing blended stage work.
References
1---2name: sy-execution-plan3description: Plan how to implement one approved slice, including file targets, validation gates, rollback, and proof lanes. Use when a slice spec is accepted and the user needs the implementation order before code changes.4---5# SynAIpse Harness Execution Plan67## When to use89Use when a slice spec is accepted and the user needs the implementation order before code changes.1011## Required inputs1213- User request or routed handoff naming this stage.14- Current repository, branch, artifact, tracker, PR, validation, and session evidence when available.15- The previous-stage artifact when this stage depends on one.1617## Deliverables1819- A stage result with schema_version, stage, status, evidence_refs, blocked_by, and next_stage.20- Exact validation status using pass, fail, or blocked.21- A handoff that names what is proven and what remains unproven.2223## Procedure24251. Restate the active repo, branch, requested stage, and available evidence.262. Check the previous-stage artifact or explain why it is not required.273. Perform only the work owned by execution-plan.284. Record evidence refs and classify each lane as pass, fail, blocked, or not_checked.295. Emit the next-stage handoff to work or a blocker with the smallest recovery step.3031## Validation3233Fail fast: stop at the first failed required gate, classify the blocker, and do not proceed to downstream stages until the failure is resolved or explicitly waived. Run the smallest relevant local check for changed files; for package-level changes, run plugin validation and SDK proof commands from the repository wrapper.3435## Handoff3637Return the stage artifact or blocker, then hand off to work only after this stage's exit criteria are satisfied.3839## Failure modes4041- Missing previous-stage artifact: block and request or create the required artifact through the owning stage.42- Conflicting evidence lanes: route to reconcile.43- Repeated failure or durable learning: route to reinforce.44- Requested action exceeds authority: block with the required authorization.4546## Gotchas4748- Do not use this stage to skip the lifecycle, merge evidence lanes, mutate external systems without explicit authorization, or complete another stage's exit criteria.4950- Similar legacy names may exist in caches or older Harness Engineering packages; do not expose them as SynAIpse active skills.51- A local artifact can explain work, but it does not prove remote PR, CI, tracker, or deployment state.52- If multiple stages seem plausible, route to sy-reframe instead of doing blended stage work.5354## References5556- Stage contract: [contract](./references/contract.yaml)57- Eval cases: [evals](./references/evals.yaml)58- Task profile: [task profile](./references/task-profile.json)59- Source context: [source context](./references/source-context.yaml)
jscraik