Skip to content

docs(release): install-from-tag statement and committed release runbook with layer ownership (#236 D4/D5) - #243

Merged
chrisdpurcell merged 1 commit into
testingfrom
docs-529
Sep 1, 2026
Merged

chrisdpurcell merged 1 commit into
testingfrom
docs-529

Conversation

@chrisdpurcell

Copy link
Copy Markdown
Collaborator

Summary

Owner decision D4 (2026-09-01): the immutable Git tag is the supported install path; GitHub release assets are convenience copies. README says so and points at the new committed release runbook, docs/reference/release-runbook.md, which replaces the per-train scratch runbooks: R0–R12 with command, observable, and rollback per step; a layer-ownership table placing each of the 16 proofs in exactly one layer (leg, integrated gate, release-prep delta, hosted Check on main, publication, periodic); and the wall-clock measurement method with a v5.29.0 row to fill.

Governing work

Supporting: #236

Acceptance coverage

Verification

technical-writer validate (0 errors), prettier + markdownlint over the three files, sync-payload-projection --check, project-standards validate on the wheel runtime (42 files) — all exit 0; every relative link resolved.

…lease runbook

README's install section now states that the immutable Git tag is the
supported install path and GitHub release assets are convenience
copies, not a supported source, per the D4 owner decision. The new
docs/reference/release-runbook.md replaces the per-train session-log
runbook with a durable procedure: each step's command, exit evidence,
and rollback, plus a Layer ownership table assigning every release
proof to exactly one gate layer (leg, integrated gate, release prep,
hosted Check, publication, or periodic).

Refs #236
@chrisdpurcell
chrisdpurcell marked this pull request as ready for review September 1, 2026 20:42
@chrisdpurcell
chrisdpurcell merged commit 789c66f into testing Sep 1, 2026
4 checks passed
@chrisdpurcell
chrisdpurcell deleted the docs-529 branch September 1, 2026 20:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant