Archive notice: This page documents historical Spec Kitty behavior and is not the current 3.2 workflow. Start with Spec Kitty 3.2 for current docs.

2.x Orchestration and API Boundary

2.x keeps orchestration external while preserving host-owned workflow integrity.

Boundary model

Host: spec-kitty manages lane state, dependency checks, and merge/accept semantics.
Provider: external orchestration runtime executes agents and calls host API.
Contract: spec-kitty orchestrator-api JSON envelope and deterministic error codes.

Operational implications

Security-sensitive environments can disable external automation and keep manual flow.
Multiple provider strategies can be implemented without changing host internals.
Runtime governance remains centralized in the host contract.

Baseline commands

spec-kitty orchestrator-api contract-version
spec-kitty orchestrator-api mission-state --mission 034-my-feature
spec-kitty orchestrator-api list-ready --mission 034-my-feature

Reference provider

Use spec-kitty-orchestrator for turnkey automation:

spec-kitty-orchestrator orchestrate --mission 034-my-feature --dry-run
spec-kitty-orchestrator orchestrate --mission 034-my-feature

Custom provider guidance

Implement your orchestration loop against orchestrator-api; do not import host internals or write lane state directly.

References

Edit this page