Constellations · drawn policy

orrery/kida-ready@0.1.0

Kida check → gate → render → sealed ready | needs-work | inconclusive disposition

What to pass

kida-check → gate → kida-render → artifact-seal

templates* array · [{path, content}] .html/.kida
data* object · JSON context for render
validate_calls boolean · default true
strict boolean · default false
surface string · html only in v1

What you get

disposition string
stages object
envelope signed-envelope

Dispositions: ready, needs-work, inconclusive

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

Composite receipt

constellation: orrery/kida-ready@0.1.0policy_digest: sha256:d3f2a86a0a5df0dc0a23b09e6ba0713d09829b4ba3fea1eb84e3468d261affd3
chain:
  1. kida-check     Envelope ✓  static findings
  2. gate     open|blocked  check pass required
  3. kida-render     Envelope ✓  HTML + digests
release: sha256:kida-ready…  signed orrery-kida-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