From 15b96a625b4dc246eef6565455e13d6ab408ab7e Mon Sep 17 00:00:00 2001 From: doxa-maps Date: Tue, 22 Sep 2026 05:26:01 +0000 Subject: [PATCH] Refresh the dated identity measurement: 18 of 18, was 17 of 17 Applying last tick's lesson systematically: swept every numeric claim about the catalog across all docs. Only one had aged into something misleading. "Measured 2026-09-21: 17 of 17 bundles identity-proven" was TRUE when written, and the gate reads the live manifest so nothing was broken. But a reader today sees 17 beside a catalog of 18 and cannot tell whether a bundle went missing or the sentence simply aged. Re-ran check:catalog-identity: 18 of 18, PASS. Restated with the delta named. The other three hits are fine and deliberately left alone: the "21 bundles" in the CLI doc is prose explaining why a count was REMOVED, the 18 in reference-capability-exemplars.md is auto-generated, and "5 plugin capabilities" is a constant rather than a count. Added the general rule beside the number: a dated measurement is not a stale claim, but it still misleads once the underlying figure moves, so re-run the gate and restate rather than leaving a reader to guess. --- documentation/reference.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/documentation/reference.md b/documentation/reference.md index 3d08d0867..0be51e6e3 100644 --- a/documentation/reference.md +++ b/documentation/reference.md @@ -288,8 +288,15 @@ The rest, grouped by what they guard — same rule (outside the build, run befor and is a 2,872-byte HTML **sign-in page** — the app-shell login wall. A status check reads that as healthy. The public door is `/plugin-assets/doxa-maps/`. Every profile already carries an `integrity` hash the build computed, so comparing it against the live bytes is a cryptographic identity proof -that costs nothing extra to maintain. Measured 2026-09-21: **17 of 17 bundles identity-proven**, and -the live manifest byte-identical to `platform/mfe-index`. +that costs nothing extra to maintain. Re-measured 2026-09-22: **18 of 18 bundles identity-proven**, and +the live manifest byte-identical to `platform/mfe-index`. (It read "17 of 17" on 2026-09-21; the catalog +has since gained `golden-path-check`.) + +> **A dated measurement is not a stale claim — but it still misleads once the underlying number moves.** +> "17 of 17" was true when written and the gate reads the live manifest, so nothing was broken. The +> problem is what a READER concludes: seeing 17 beside a catalog of 18, they cannot tell whether a bundle +> went missing or the sentence simply aged. ★ If you quote a count here, re-run the gate and restate it — +> `bun run check:catalog-identity` prints the current figure in one line. ### The screenshot gates — three different lies a picture can tell