Constellations · drawn policy

orrery/invite-ready@0.1.0

Secretary enrich-before-seal: clock + flight + place + venue hours composite

What to pass

world-time → flight-status → geocode → place-hours → seal

place string · allowlisted geocode token
venue string · allowlisted venue-hours token
flight string · allowlisted flight id
date string · pinned fixture date

What you get

enrichment object
envelope signed-envelope

Dispositions: enriched, incomplete

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

Composite receipt

constellation: orrery/invite-ready@0.1.0policy_digest: sha256:62c2cd5c0f39d900e75a66f2bf14f64b39ada462ef10a5935813a68d573d4241
chain:
  1. world-time     Envelope ✓  now
  2. flight-status     Envelope ✓  flight fixture
  3. geocode     Envelope ✓  place fixture
  4. place-hours     Envelope ✓  venue hours
release: sha256:invite…  signed orrery-invite-ready-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