Release Book: definition and contract

A Release Book presents changed Journeys, verified contexts, Decisions, accepted risks, downstream updates, and approved outputs as one release truth. It is a view over canonical linked objects and hashes, not a parallel status database or an automatically generated claim that a release is risk-free.

What a Release Book answers

• Which meaningful product outcomes changed?
• Which Journey Versions and contexts were verified?
• What did the Runs actually observe?
• Which Decisions were made, by whom, and under what authority?
• Which risks, exceptions, and uncertainties remain?
• Which documentation, support, training, demos, and marketing outputs changed?
• What was published, where, and with which receipt?
• Which owners have completed or still owe release-readiness actions?

One fact set, multiple views

Engineering, support, documentation, accessibility, design, and marketing may need different projections. They should not edit separate versions of the release facts. Each view resolves to the same Journey, Observation, Decision, Rendition, Publication, commit, build, environment, and item identity.

Signing and offline verification

A signed Release Book package can prove package integrity and origin. It does not prove that coverage was complete or that every accepted risk was wise. Coverage, uncertainty, exceptions, and owner Decisions remain visible inside the package.

Offline verification checks item hashes, manifest integrity, signature, and matching public key without requiring a Reshot account. See the manifest specification and offline verifier.

Example: a changed invitation Journey

The Release Book may show the new Journey Version, verified owner and admin contexts, a repaired target, the approving Decision, an updated support procedure, a refreshed documentation screenshot, and the receipts for their Publications. If one locale was not verified, that gap remains explicit rather than disappearing from an executive summary.

Explore the Release Book product surface or return to the Product Journey glossary.