jeffryandClaude Opus 5
f8b41dfb19
How a repository records what it depends on, and finds out when it changes. Pull what you use; two facets beside it; ETag freshness; reconciliation running the other way; venues for what you cannot fetch; gaps, with moving a file as the homing act. Built on bedrock's sibling facets, whose three open choices are answered in .loom/externals/git.hypertheory-labs.dev/loom/annotating/annotating.usages.md — the convention adopting annotating using itself. That is the cheapest available test of whether it works. It also states in public the answer whose absence kept two agreements frozen from 2026-08-21: the pair is released by replacement, never by rewriting. A source you did not write is not yours to rewrite, and the protocol never said what to do instead. Nobody chose badly; nobody was asked. The first copy of annotating here was written by hand. You cannot fetch and annotate before the thing that says how exists — self-hosting is a test, not a derivation. Note: loom/annotating does not exist yet, so the external's origin path currently resolves to nothing. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
801 B
801 B
externals
How a repository records what it depends on, and finds out when it changes.
- Externals — the convention
Built on bedrock's sibling
facets, whose three open choices we answer in
our usages of annotating.
And annotating is here as an external of ours — fetched, locked, annotated
— which is the convention describing itself using itself. If that had not
worked, the convention would be wrong, and it is the cheapest test available.
The first copy was written by hand. You cannot fetch-and-annotate before the thing that says how exists. Self-hosting is a test, not a derivation.