docs: tick P1, and record the design change it forced - #6
Merged
Conversation
Canonical is published and serving; the gate is proven against the real remote in CI as well as locally. The change worth recording is that STANDARD_URL defaults to canonical inside standard.mk rather than being set per adopter, which is not what this plan said. Per-adopter opt-in fails open: a repo that vendors the file and forgets the line has no drift protection and reports that as a notice reading like a pass. Nobody greps for an absent line. Vendoring the file is now what arms it. Also recording the consequence every adopter inherits — `make lint` now requires network — because that is the RFC's deliberate tradeoff for refusing a cache, and P2 and P4 will both meet it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XLuSsmv88aheh7mNQgBDQK
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
P1 is done: canonical published at https://just-buildit.github.io/standard.mk (just-buildit.github.io#9) and vendored back into just-makeit (just-makeit#637).
The gate is now proven against the real remote, in CI as well as locally — a matching copy passes, a one-character edit fails with the diff. Before this it had only ever been shown that it would work.
One design change from this plan
STANDARD_URLdefaults to canonical insidestandard.mk, rather than each adopter setting it.The plan said arming was "the one-line change" per repo. That fails open: a repo that vendors the file and forgets the line has no drift protection at all, and announces it as a notice that reads like a pass — and nobody greps for a line that isn't there. Vendoring the file is now what arms it; deliberate opt-out is
STANDARD_URL =, which is a line and so can be found across the org.Consequence recorded, because every adopter inherits it
make lintnow requires network. That is the RFC's deliberate tradeoff for refusing a cache — a Pages outage reddenslintorg-wide rather than silently comparing against something older. P2 and P4 will both meet this.One thing I did not change
P3's note reads "until
standard.mkexists, the doc describing the old names is still accurate". That premise is now stale — it does exist. The scheduling still holds for a different reason (doppler keeps the old names until P2 renames them), but the stated reason no longer does. Left alone since P2/P3 are yours; flagging rather than rewriting.