jeffryandClaude Opus 5
e62bbe17c1
Two decisions from cart osprey in loom-cli, and this repository had nowhere to record them until now. 404 is named as two answers wearing one status, filed as a gap using this document's own test and correctly ours to close. And the correction that matters: a facet describes the local pair. A gap is true of the copy you hold rather than the document upstream, so a publisher fixing their end does not close it — we nearly deleted a consumer's .gaps.md on exactly that mistake. It follows from the thing this convention rests on, that the copy is theirs and everything beside it is ours, which we had not followed through to reconciliation. A gap closes at reconciliation, not at repair. With the consequence we would not have reached: what survives is not the gap but what the gap justified. A workaround is often not retired by a fix — it stops being a workaround and becomes specified behaviour, unchanged in code and entirely changed in status, which is invisible where the code is and therefore an entry in the consumer's own log. And a closed gap is not a decline: opposite sign, and filing one as the other puts a thing you wanted into a list of things you rejected. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.