Operations Demo Coverage
This walkthrough shows how orchestration and outbound operations are executed or simulated in-product, with clear status, failure reasons, and guided next actions.
proc-orch-sellable-app-pipeline
Mode: Live + Simulated
What happened: An idea flows through intake, analysis, implementation, and launch checkpoints.
Why it matters: Teams can show repeatable delivery without terminal-only operations.
Operator next action: Operator retries from failed stage with dry-run first.
proc-orch-dispatch
Mode: Live + Simulated
What happened: Ready tasks are dispatched across local/background/cloud lanes with strategy controls.
Why it matters: Execution bottlenecks are caught before queues stall overnight.
Operator next action: Run ready-only simulation, then execute selected lane strategy.
proc-script-setup-outbound
Mode: Local-VPS default
What happened: Outbound workflows are imported and activated from an operator-safe setup panel.
Why it matters: Revenue-critical setup is no longer blocked on token-first auth.
Operator next action: Keep local-vps mode by default, enable API key mode only if required.
proc-script-check-outbound
Mode: Live + Simulated
What happened: Webhook preflight runs validate endpoint reachability and report failures.
Why it matters: Prevents late discovery of broken outbound pipelines.
Operator next action: Run manual preflight, then schedule recurring checks.
proc-orch-token-optimized
Mode: Live + Simulated
What happened: Skill-first cascade routes deterministic gates through cheap skills before escalating to agents.
Why it matters: 60-80% token reduction vs full-agent pipeline — enterprise clients see cost efficiency.
Operator next action: Run classify gate, inspect tier assignments, then execute full cascade.
proc-orch-enterprise-onboard
Mode: Live + Simulated
What happened: New client provisioning flows through intake → classify → configure → deploy → verify.
Why it matters: White-label ready pipeline — portable for enterprise injection and partner demos.
Operator next action: Enter client details, run intake simulation, then execute full onboarding flow.
proc-orch-idea-spawn
Mode: Live + Simulated
What happened: A plain-language idea becomes a structured queue with dependency chaining.
Why it matters: Compresses strategy-to-build handoff cycle time.
Operator next action: Use spawn preview before enqueueing.
proc-orch-queue-builder
Mode: Live + Simulated
What happened: Operators inspect and prioritize queue items before dispatch.
Why it matters: Improves delivery predictability and lane utilization.
Operator next action: Validate dependency graph and priority order.
proc-orch-overnight-runner
Mode: Live + Simulated
What happened: Timeline replay shows started, done, timed-out, and failed overnight tasks.
Why it matters: Operations can recover quickly each morning.
Operator next action: Run timeout-safe dry-run before full overnight window.
proc-orch-submit-pr
Mode: Dry-run first
What happened: Pre-submit checks, reviewer tiering, and PR body generation are surfaced in one panel.
Why it matters: Release governance is clear and auditable.
Operator next action: Review dry-run output and then execute submit flow.
Operators can execute these flows from the admin hub routes with local-vps defaults.