From 94a8967d9691febd3f27091401301ef0efa51ad0 Mon Sep 17 00:00:00 2001 From: Boyd Cohen Date: Sat, 8 Aug 2026 23:47:16 -0600 Subject: [PATCH] The wdk-op-policy provenance note describes the state the 2026-08-08 fix removed Measured 2026-08-09. Two false statements, both at the URL a consumer checking provenance lands on, and both created by the work that was supposed to make provenance checkable. 1. "0.2.0, 0.3.0, 0.3.1, 0.3.2 and 0.4.0 resolve only in a private repository and cannot be fetched from outside the organisation." All five resolve in the PUBLIC observer-protocol/wdk-op-policy on the unmerged provenance/pre-monorepo branch, and each is reachable from a tag named for its version. Confirmed from a mirror clone taken with no authentication beyond public read. That is exactly what the 2026-08-08 provenance pass accomplished, and this sentence is its own description of the state it removed. 2. "(archived, read-only)". The repository reports archived=false. The pattern is the one already corrected twice this week at op-legacy-deployment: a true sentence becomes false because the state it describes was FIXED, and nobody re-reads the sentence because the fix felt like the end of the work. The block now says every published version resolves publicly, names which branch each sits on and why the divergent ones are tagged, and records both retired claims beside the correction. Swept the other six READMEs for the same shape: every remaining "(archived, read-only)" claim matches the measured archive state of the repository it names. --- packages/wdk-op-policy/README.md | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-) diff --git a/packages/wdk-op-policy/README.md b/packages/wdk-op-policy/README.md index c6eeb41..7106ce1 100644 --- a/packages/wdk-op-policy/README.md +++ b/packages/wdk-op-policy/README.md @@ -14,11 +14,19 @@ > > **Versions.** Published `0.4.1`. > -> **Provenance.** Versions `0.1.0` and `0.4.1` resolve in -> [`observer-protocol/wdk-op-policy`](https://github.com/observer-protocol/wdk-op-policy) -> (archived, read-only). **`0.2.0`, `0.3.0`, `0.3.1`, `0.3.2` and `0.4.0` resolve only in a private -> repository and cannot be fetched from outside the organisation.** The next release onward resolves -> here. +> **Provenance. Every published version resolves publicly.** All seven, `0.1.0` through `0.4.1`, +> resolve in [`observer-protocol/wdk-op-policy`](https://github.com/observer-protocol/wdk-op-policy), +> and each is reachable from a tag named for its version. `0.1.0` and `0.4.1` sit on `main`; `0.2.0`, +> `0.3.0`, `0.3.1`, `0.3.2` and `0.4.0` sit on the unmerged `provenance/pre-monorepo` branch, a +> divergent lineage rather than an ancestor of `main`, which is why they are tagged. The next release +> onward resolves here. +> +> *Correction 2026-08-09: this block previously said those five versions "resolve only in a private +> repository and cannot be fetched from outside the organisation", and described the repository as +> "(archived, read-only)". Both were false when read. The five were made publicly resolvable on +> 2026-08-08 and that work is what this sentence was describing, so the fix left the description of +> the old state in place at the URL a consumer checking provenance lands on. The repository is not +> archived: `archived=false`, measured 2026-08-09.* > The Observer Protocol API's rail registry no longer carries a pin. **Ruled 2026-08-05:** the > field was named `version` and read as "these versions are known to work together", while > nothing enforced or checked it — the running server never reads it. It is now