post-release

A post-release assessment is a structured evaluation that codifies a release cycle's outcomes, measuring coherence and analyzing lag. You need it after creating a git tag to ensure evidence, closure decisions, and next steps are documented.

You standardize post-release reviews by applying an automated evaluation across alpha, beta, and gamma axes to measure coherence and analyze lag. This generates a comprehensive assessment artifact for governance decisions and cycle closure.

To generate a post-release assessment artifact, run the evaluation after creating a new git tag. This produces a POST-RELEASE-ASSESSMENT.md file containing required sections for coherence measurement, lag analysis, and closure dispositions.

Post-release assessment requires a git tag and release event to trigger. It operates without external dependencies, applying cross-surface patch discipline to generate documentation within the docs/gamma/cdd directory structure.

The best way to document post-release evidence is generating a standardized assessment artifact that ties shipped artifacts to governance decisions. This provides cycle-level decision support for dispositioning contributions in the next iteration.

You should avoid automated post-release evaluation if your project lacks a formal git tag release process or does not require strict coherence measurement and lag analysis across alpha, beta, and gamma axes for governance.