OpenSpec Workflow

Use OpenSpec for planning significant changes, especially new capabilities, breaking changes, architecture changes, or ambiguous work that needs a written contract.

Standard Flow

1. Create a proposal.
2. Review and refine the spec.
3. Apply the approved change.
4. Validate.
5. Archive the change.

Documentation

Any change that modifies APIs, CRDs, state machines, or user-visible behavior should update the relevant documentation pages.