Release
A first-class object pinning commits across all linked repos and snapshotting the requirements set. State machine: draft → verifying → verified → shipped → archived. Re-verification is a pure replay against the same pinned commits and requirement snapshot.
Why It Matters
"What got shipped" is typically ambiguous in robotics: many repos, many branches, many merges per day. Without a defined release object, audit replay is impossible because the inputs to the verification are moving.
How Roboticks Implements It
A Release pins commit SHAs in each linked repo, snapshots the requirements (so editing requirements later doesn't retroactively change the release's verification), and accumulates verifying test runs. Evidence packs scope to a release. Multi-repo: customer designates one "release-tagged repo"; others pin to default-branch HEAD at tag time.