Constellations · drawn policy

orrery/api-spec-upgrade@0.1.0

Frozen OpenAPI upgrade graph with breaking-approval pause and composite receipt (#179)

What to pass

inventory → choose-profile → safe-upgrade → breaking-approval → validate-target → compatibility-diff → artifact-seal

entries* array · path/content OpenAPI tree
profile* object · pinned ADR 0008 MigrationProfile
caller_id string · authenticated resume identity

What you get

disposition string
outstanding_action_requests object
migration_receipt object
validation_digest string
compatibility_diff_digest string
artifact_digest string
envelope signed-envelope

Dispositions: completed, awaiting_input, inconclusive, failed, cancelled, expired

gate (must verify) repair loop (bounded) fan-in

Composite receipt

constellation: orrery/api-spec-upgrade@0.1.0policy_digest: sha256:50a5460b5f44cd66196f9b7cf67cda69740c4cbf3567ff3cdf1544012f406db3
chain:
  1. inventory     Envelope ✓  source inventory
  2. choose-profile     Envelope ✓  profile pin
  3. safe-upgrade     Envelope ✓  plan+apply
  4. breaking-approval     awaiting_input  typed approval
  5. validate-target     Envelope ✓  schema validate
  6. compatibility-diff     Envelope ✓  policy diff
  7. artifact-seal     Envelope ✓  migration receipt
release: sha256:api-spec-upgrade…  signed orrery-api-spec-upgrade-1

Why this isn't CI YAML

Same graph from any harness. Stars can live in different namespaces. Edges require verified Envelopes — not green checkmarks in one repo.

Run under acme/* Reliability console