Constellations · drawn policy

orrery/content-readiness@0.1.0

Assess a caller content bundle: manifest, structure, bounded links → sealed disposition

What to pass

manifest-bind → manifest-preflight → structure-audit → link-check-bounded → artifact-seal

files* array · [{path, content, format?}]
policy string · orrery/docs-only@v1 or orrery/max-100-files@v1
max_link_count integer · 1..50; default 20

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/content-readiness@0.1.0policy_digest: sha256:70131d049f0f2d056626337d93f8be64b403cc8ba4e2cb4126be9e5b8d32de37
chain:
  1. manifest-bind     Envelope ✓  digest inventory
  2. manifest-preflight     Envelope ✓  named policy
  3. structure-audit     Envelope ✓  markdown findings
  4. link-check-bounded     Envelope ✓  bounded HTTPS
release: sha256:content-readiness…  signed orrery-content-readiness-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