Skip to content

workflow-sandbox-canary-runbook.md

Latest commit

 

History

History
53 lines (39 loc) · 2.76 KB

workflow-sandbox-canary-runbook.md

File metadata and controls

53 lines (39 loc) · 2.76 KB
Raw

Workflow Sandbox Canary Runbook

This runbook covers the repo-local scripts/workflow-sandbox-canary.mjs harness for the Idea-to-Build sandbox campaign.

Modes

  • --dry-run — print target sandbox path, delivery policy, fixture list, and final package layout. No Multica mutations.
  • --apply — create sandbox project resources, binding, parent issue, and start a canary run. Rejects explicit production project IDs.
  • --campaign — advance exactly one Hermes stage from existing canary state. Requires prior --apply. Add --run-full-campaign to permit more than one stage.
  • --human-review — approve (or reject) the completed canary run, sync parent metadata, close parent issue, and write 10-human-final-review.md. Requires prior --campaign with workflow_status=completed.
  • --resume <workflow-run-id> — resume an existing canary run from ledger state.
  • --fixture <name> — execute one failure fixture in isolation (F1_success_path … F8_stage_starvation).
  • --report — regenerate the final package from existing evidence without live side effects.

Typical flow

node scripts/workflow-sandbox-canary.mjs --dry-run
node scripts/workflow-sandbox-canary.mjs --apply
node scripts/workflow-sandbox-canary.mjs --campaign --max-stage-cycles 1
# After explicit approval, repeat the one-stage tick until currentStageId=final_package.
node scripts/workflow-sandbox-canary.mjs --human-review
node scripts/workflow-sandbox-canary.mjs --report

Do not run --human-review after a single tick unless it reached final_package.

Full campaign rehearsal only:

node scripts/workflow-sandbox-canary.mjs --campaign --run-full-campaign --max-stage-cycles 80

Safety checks

  1. Confirm the sandbox path is under C:/Users/Keisu/Projects/Sandbox/.
  2. Verify deliveryPolicy.productionAllowed=false and releaseAllowed=false.
  3. Do not pass production project IDs to --apply.
  4. Record live IDs only in investigation docs; never commit webhook tokens.
  5. If Multica CLI reports a daemon task marker, remove .multica/daemon_task_context.json or rely on automatic cleanup in --apply / --campaign / --human-review (v0.5.2+).

Operations handoff

  1. Locate the parent Workflow Issue and open the Workflow Run Ledger.
  2. Read currentStageId, migration.status, and the latest routeDecisions entry.
  3. Refresh telemetry snapshots when refresh_telemetry is the last controller action.
  4. Run adapter migration dry-run before any apply.
  5. Use migration rollback when migration.status=preparing.
  6. Keep unresolved preferences in 07-assumptions-and-open-questions.md.

Live execute

For orchestrated live rehearsal (--execute) and failure recovery, see workflow-sandbox-live-execute-runbook.md.