| name | ssot-release |
| description | Manage release entities with full CLI coverage, including claim/evidence membership and certify/promote/publish/revoke progression. |
SSOT Release
Use this skill for release-only operations.
Command discipline
- Do not spend turns rediscovering syntax with
--help during normal SSOT work. Use the command surface and examples in this skill directly.
- Pick one verified CLI rail for the repo (
ssot, ssot-registry, ssot-cli, or uv run ssot) and reuse it consistently by substituting that rail into the examples below.
- Only inspect parser or help text when the user explicitly asks about the CLI surface or when observed runtime behavior contradicts the command patterns documented here.
Command surface
release create|get|list|update|deleterelease add-claim|remove-claim|add-evidence|remove-evidencerelease certify|promote|publish|revoke
Workflow
- Inspect release/boundary linkage and current status.
- Maintain claim/evidence membership completeness.
- Progress gates in strict order: certify -> promote -> publish.
Operating rules
- Fail closed: never promote or publish when prerequisite gates fail.
- Keep release claim/evidence sets aligned with frozen boundary scope.
- For full decision-to-release orchestration, escalate to
$ssot-e2e-change-orchestrator.
Example
ssot release get . --id rel:demo.v1
ssot release add-claim . --id rel:demo.v1 --claim-ids clm:demo.login.t1
ssot release certify . --release-id rel:demo.v1 --write-report
ssot release promote . --release-id rel:demo.v1
ssot release publish . --release-id rel:demo.v1
