What Citable observes
- Release-manifest declarations, expected bytes or checksums, controlled-surface URLs, and receipt validation results.
- Per-surface success or failure observations produced by an explicitly run deployment-receipt collector.
- The distinction between package publication, workflow execution, and live deployment state.
Evidence artifacts
- Synchronized package release projection
- Release manifest and controlled-surface declarations
- Schema-valid per-surface deployment receipts when collected
- Checksums and failure observations retained by the release process
What the observation cannot establish
- A package version or changelog entry does not prove workflow success or deployment.
- A successful workflow does not prove that every controlled surface serves the expected bytes.
- Missing, stale, incomplete, or uncommitted receipts leave deployment state unknown rather than passing.
Next operational step
Act on the bounded result
Run the governed receipt collector for the release, commit the fresh validation artifacts, and treat any absent or failed required surface as a release blocker.