A release is a claim about a specific revision, platform envelope, artifact, and behavior. Proof is the chain that lets another person inspect that claim.
UnitOne revision and its declared platform matrix
OutputChecks, artifact identity, demo evidence, and known limits
Reader testCan someone reproduce or inspect the result?

The proof bundle

1

Identify the revision

Record the repository, commit, tag, build environment, and declared platform matrix. “Latest” is not a stable identifier.
2

Build from the documented path

Use the same package definition or build script presented to users. Record generated artifacts and their hashes when distribution matters.
3

Run layered checks

Keep compilation, static analysis, unit tests, integration tests, end-to-end checks, and security tooling separate. One green command should not conceal which layers were skipped.
4

Reproduce the visible claim

Capture a seeded frame, source-row trail, health report, or operator flow from the built revision.
5

Publish boundaries with the release

State required services, unsupported platforms, simulated components, data paths, security assumptions, and rollback instructions.

Weak and strong evidence

Where each project stands

The status ledger lists the strongest current proof and the main open gap for every project. It is dated and changes in the same pull request as the page it summarises.

Release gate

Before attaching shipped to a surface, answer yes to each applicable question:
  • Is the revision immutable or tagged?
  • Does a clean environment build through the public path?
  • Are required tests named and visible?
  • Can the flagship claim be reproduced from a fixture or documented account path?
  • Are external services and data paths explicit?
  • Are simulated components labeled beside the feature?
  • Does the license match the distribution claim?
  • Can an operator remove, stop, roll back, or recover the system?
  • Does the release state known limits without burying them?
A fast-moving project can ship often without calling every commit a release. Preserve the difference between development activity and a supported artifact.

The public proof surface

A strong repository should let a reader move through four layers:
  1. Ten seconds: outcome, real visual, and maturity label.
  2. One minute: one-click, one-command, or seeded demo.
  3. Five minutes: architecture, boundaries, checks, and release identity.
  4. Contributor depth: source layout, development setup, roadmap, and issue path.
The Field Manual covers the third layer.