spec-kitty-orchestrator-api-operator

You integrate workflow orchestration into CI/CD automation by using a stable orchestrator-api JSON contract to query mission states and trigger work package transitions from your pipeline. This ensures reliable execution without breaking the host state machine.

The best way to query mission state from an external dashboard is calling the mission-state and list-ready orchestrator-api endpoints. These return a consistent JSON envelope containing success, error_code, and data for safe polling.

Yes, policy enforcement requires validated policy metadata for run-affecting work package transitions. This validates against secret-like values to ensure correct guard behavior and maintain a reliable audit trail for lane changes.

You verify orchestrator-api compatibility by using the contract-version check at startup. This confirms your external system matches the expected JSON contract before you attempt to query mission state or trigger work package transitions.

Yes, you can safely retry start-implementation transitions because the orchestrator-api supports idempotent claim behavior. This ensures that repeated calls from supervisor processes coordinate implementation without duplicating work or corrupting state.

Your external orchestrator fails to drive workflow execution if it bypasses the contract-version check or omits validated policy metadata for run-affecting transitions. Skipping these steps breaks guard behavior and disrupts audit logging.