From a88e2b855c280aa12004f9150c386145dede4e73 Mon Sep 17 00:00:00 2001 From: iancooper Date: Sat, 8 Aug 2026 16:24:17 +0100 Subject: [PATCH] =?UTF-8?q?Revert=20the=20depth=20probe=20=E2=80=94=20the?= =?UTF-8?q?=20measurement=20is=20recorded?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Four segments publishes correctly on this site. Measured against the live site 2026-08-08, minutes after PR #83 merged: path guaranteed-at-least-once/azureblobarchiveprovider/ azureblobconfiguration/urldepthprobe sitemap present; 112 entries, was 111 status 200 location 0 headers -- no redirect, this is a genuine page body 529,080 bytes (a 404 shell is ~189.5 KB) title URL Depth Probe | Paramore Brighter Documentation S3's ceiling of three was an untested assumption, not a platform limit. GitBook's own documentation already published 30 pages at four segments below its site root; this establishes the same for our site. Reverts the content of 39823ea (PR #83). The tree is byte-identical to c4aedb5, the commit before the probe. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_012tcdwxVb8NmKaX2S6fvyFg --- SUMMARY.md | 1 - contents/UrlDepthProbe.md | 34 ---------------------------------- 2 files changed, 35 deletions(-) delete mode 100644 contents/UrlDepthProbe.md diff --git a/SUMMARY.md b/SUMMARY.md index c7bc6b4..cece5b1 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -75,7 +75,6 @@ * [Azure Service Bus Configuration](/contents/AzureServiceBusConfiguration.md) * [Azure Blob Archive Provider](/contents/AzureBlobArchiveProvider.md) * [Azure Archive Provider Configuration](/contents/AzureBlobConfiguration.md) - * [URL Depth Probe](/contents/UrlDepthProbe.md) * [Brighter Control API](/contents/BrighterControlAPI.md) ## Outbox and Inbox diff --git a/contents/UrlDepthProbe.md b/contents/UrlDepthProbe.md deleted file mode 100644 index f1faa76..0000000 --- a/contents/UrlDepthProbe.md +++ /dev/null @@ -1,34 +0,0 @@ -# URL Depth Probe - -> **Reference** · Applies to **Brighter V10** - -This page is a temporary measurement for Spec 010 and will be removed within minutes of -being published. It exists to establish, against the live site rather than by inference, -whether a page nested three levels deep in `SUMMARY.md` publishes at a four-segment URL. - -## URL Depth Probe Method - -Spec 010's shape rule **S3** caps a published path at three segments, on the stated grounds -that three is the deepest the live site is *known* to work at and four had never been -tested. That is an evidence boundary rather than a platform limit, and it was costing -navigation quality in two places, so it is being measured instead of assumed. - -This page is nested under *Azure Archive Provider Configuration*, which itself publishes at -three segments. The predicted path is therefore: - -```text -guaranteed-at-least-once/azureblobarchiveprovider/azureblobconfiguration/urldepthprobe -``` - -A page that has never existed at any path is used deliberately, so that no automatic -redirect can mask the result — the same reasoning that made Spec 010's D0 experiment a -measurement rather than a hope. No existing page moves, so no real URL churns and no -redirect is cached against content a reader might want. - -The result is read from `sitemap-pages.xml` and from the response fingerprint, never from -the status code: every cached response on this site reports `200`, and the reliable tell is -that no genuine page response carries a `location:` header. - -## Further Reading - -- [Basic Concepts](/contents/BasicConcepts.md)