Constellations · drawn policy

orrery/board-memo@0.1.0

Resumable board-memo demo: memo-bind → audience-choice pause → pdf-seal composite (ADR 0007 Example 2)

What to pass

memo-bind → audience-choice → pdf-seal

title* string · memo title
summary* string · memo body text
author string · optional author label
caller_id string · authenticated resume identity

What you get

disposition string
outstanding_action_requests object
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/board-memo@0.1.0policy_digest: sha256:093e3aec5092d2848008df1defac4972bb0546c7bb616c6f348961115a1c85ef
chain:
  1. memo-bind     Envelope ✓  title+summary bound
  2. audience-choice     awaiting_input  typed choice
  3. pdf-seal     Envelope ✓  managed PDF artifact
release: sha256:board-memo…  signed orrery-board-memo-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