sorrel: reconcile bedrock 82 and 83, and answer both prompts

publication.md and starting.md both came back 200 and are applied. Step 4 — fetch it, from somewhere that is not your machine and not your account — is now the procedure our declined command was an argument for. Answers the Select for a fixed path but against .loom/externals/README.md, with a measured reason: check walks that directory for adopted documents, so a generated file there reports as unlocked in every repository using the feature, forever. The deeper reason is the invariant — everything under externals/ is somebody else's document, which is what makes do-not-edit a rule you can state in four words. Proposes .loom/orientation.md, beside event-log.md, since .loom/README.md is already given to what is in published/ and why. Answers the Question yes. The visibility check was built as a moment and loom is right that it is a fact that decays: access is verified once and the copy is durable. It costs nothing at add time, since the anonymous request already happens and the answer is thrown away, and one request per run at check time rather than per document, since only our own visibility must be current. Adds the refinement that the stored value decays both ways, so a source recorded private is re-checked only when the alarm would fire. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018UTxuSizozEA8yDitPuris
2026-09-08 09:05:38 -04:00
parent fb8b8d01d3
commit 1cc528c8aa
3 changed files with 26 additions and 8 deletions
@@ -4,9 +4,9 @@
 git.hypertheory-labs.dev/jeffry/homelab-cluster/gitea.md	https://git.hypertheory-labs.dev/jeffry/homelab-cluster/raw/branch/main/.loom/published/gitea.md	"530c5bef62bbd325956ed170bb2decf37975e4b9"
 git.hypertheory-labs.dev/loom/annotating/annotating.md	https://git.hypertheory-labs.dev/loom/annotating/raw/branch/main/.loom/published/annotating.md	"9b1f7e6ca92f2339b2d433686c27845362944bdb"
 git.hypertheory-labs.dev/loom/bedrock/loom-directory.md	https://git.hypertheory-labs.dev/loom/bedrock/raw/branch/main/.loom/published/loom-directory.md	"ee0f49cb900c0812678061971194325d9cba366a"
-git.hypertheory-labs.dev/loom/bedrock/publication.md	https://git.hypertheory-labs.dev/loom/bedrock/raw/branch/main/.loom/published/publication.md	"385e26ef4108029c12a4267600399da1eece52af"
+git.hypertheory-labs.dev/loom/bedrock/publication.md	https://git.hypertheory-labs.dev/loom/bedrock/raw/branch/main/.loom/published/publication.md	"c0d9231aa8eed3041c60b72da5735585457fbc90"
 git.hypertheory-labs.dev/loom/bedrock/recording-decisions.md	https://git.hypertheory-labs.dev/loom/bedrock/raw/branch/main/.loom/published/recording-decisions.md	"d190eeae7929b9a99ecf09211d94e7e5b32635bd"
 git.hypertheory-labs.dev/loom/bedrock/sibling-facets.md	https://git.hypertheory-labs.dev/loom/bedrock/raw/branch/main/.loom/published/sibling-facets.md	"a46446a34ccb8bfc533d3cce19f4c88548c4fa04"
-git.hypertheory-labs.dev/loom/bedrock/starting.md	https://git.hypertheory-labs.dev/loom/bedrock/raw/branch/main/.loom/published/starting.md	"7d997a30248a88c90b23f2f9453d7cfceb03848e"
+git.hypertheory-labs.dev/loom/bedrock/starting.md	https://git.hypertheory-labs.dev/loom/bedrock/raw/branch/main/.loom/published/starting.md	"b9eefba0f4668a496ccfc6a1377277f0721456d2"
 git.hypertheory-labs.dev/loom/cart/cart.md	https://git.hypertheory-labs.dev/loom/cart/raw/branch/main/.loom/published/cart.md	"15331f1a9cc81bf61a44830cfbb7c274f4c2b119"
 git.hypertheory-labs.dev/loom/externals/externals.md	https://git.hypertheory-labs.dev/loom/externals/raw/branch/main/.loom/published/externals.md	"a7586eb52caf275d9bcedbbd8042c43e5aaad0b9"
@@ -37,6 +37,21 @@ copy without inheriting the visibility it was published under.*
 **The test is a fetch you did not perform.**
 ## Doing it
 1. **Decide it is a contract and not a detail.** *This is the whole decision and
   the rest is mechanics.*
 2. **Move the file into `.loom/published/`.** *One commit, so the diff carries it.*
 3. **Say who the readers are** — *if it is not obvious from where it landed.*
 4. **Fetch it.** *From somewhere that is not your machine and not your account.*
 5. **Record the decision**, if you keep a log.
 **Step 4 is the one that gets skipped and the only one that can fail.** *Steps 1
 to 3 are things you do; step 4 is a fact about the world that you find out.*
 *Then say what it depends on. A published document that quietly requires a private
 one has moved the problem rather than solved it.*
 ## What is published is a document
 **Prose, in whatever form its readers need.** *If a repository organises its
@@ -60,13 +60,16 @@ what they came for.*
 ## Look at one instead of reading this
-**There is a worked example — six documents, one gap, no decomposition — and it
+**[`jeffry/homelab-cluster`](https://git.hypertheory-labs.dev/jeffry/homelab-cluster)** —
-is private.**
+*six documents, one gap, no decomposition.* **It describes what a home cluster
 offers to somebody deciding whether to put something on it**, and a reader who
 has never heard of any of this still gets what they came for.
-*It describes a cluster in enough detail to be a target list, so it is not
+**It was private, and being unable to link to it is what made the split obvious.**
-published, and **this page will not link you to something you cannot fetch.***
+*The operational tree is a version inventory and a target list; the pages telling
-**If you have access, ask for it by name; if you do not, the two questions at the
+somebody what to decide are neither.* **So the manifests moved to a private
-top are the whole of it.**
+sibling and the documents stayed** — *and the documents got better for being
 written to a stranger, which was not the reason for doing it.*
 > **A public page naming a private thing as its canonical answer is worse than no
 > example**, and this page did exactly that until somebody measured it.