From 2c69f470ef3d16e1a56c4789888fa14b6eca7f06 Mon Sep 17 00:00:00 2001 From: Scott Converse Date: Tue, 5 May 2026 00:51:55 -0600 Subject: [PATCH] [CO-2b] docs: rename historical provenance disclosure --- ...venance-draft.md => historical-provenance.md} | 0 docs/ops/release-signing.md | 16 +++++++--------- 2 files changed, 7 insertions(+), 9 deletions(-) rename docs/ops/{historical-provenance-draft.md => historical-provenance.md} (100%) diff --git a/docs/ops/historical-provenance-draft.md b/docs/ops/historical-provenance.md similarity index 100% rename from docs/ops/historical-provenance-draft.md rename to docs/ops/historical-provenance.md diff --git a/docs/ops/release-signing.md b/docs/ops/release-signing.md index a02f9ca..e51b380 100644 --- a/docs/ops/release-signing.md +++ b/docs/ops/release-signing.md @@ -222,14 +222,12 @@ actual file. ## Historical Disclosure Publication -The historical provenance disclosure remains a draft while it is named -`docs/ops/historical-provenance-draft.md`. Final policy publication is a -two-step operation in one verified PR: +The historical provenance disclosure now lives at +`docs/ops/historical-provenance.md`, but it remains a draft until the final +policy-promotion step lands. -1. Remove draft-specific language and fill the authorized baseline date and - baseline tag. -2. Rename the file to `docs/ops/historical-provenance.md` so the canonical - public disclosure is discoverable without the `-draft` suffix. +Before publishing it as operative policy, remove draft-specific language and +fill the authorized baseline date and baseline tag in a verified PR. -Do not publish the disclosure as operative policy until both steps land -together and the auditor explicitly authorizes publication. +Do not publish the disclosure as operative policy until that policy-promotion +step lands and the auditor explicitly authorizes publication.