orrery/ship-check@0.1.0

Seal ship-check evidence: metadata release+UTC or content-bundle readiness stages

What to pass

mode=metadata: release metadata → source-watch → world-time → artifact-seal; mode=content-bundle: manifest-bind → manifest-preflight → structure-audit → link-check-bounded → artifact-seal

package* string · required for mode=metadata
source_digest string
mode string · metadata (default) | content-bundle
files array · required for mode=content-bundle [{path, content, format?}]
policy string · content-bundle preflight policy
max_link_count integer · content-bundle link cap

What you get

evidence object
envelope signed-envelope

Dispositions: ready, not-ready, stale, blocked

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

Composite receipt

constellation: orrery/ship-check@0.1.0policy_digest: sha256:27c5e185477d417879c9f2e38cf5d022032e50d0d00e315f27b188bb21de0ee9
chain:
  1. release     Envelope ✓  PyPI/npm latest (metadata)
  2. source-watch     Envelope ✓  Python notes diff
  3. world-time     Envelope ✓  UTC evidence
  4. manifest-bind     Envelope ✓  content-bundle inventory
  5. link-check-bounded     Envelope ✓  bounded HTTPS
release: sha256:ship-check…  signed orrery-ship-check-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