docs(rfc): qualified identifier for the rootless spike + fix the LPI back-link#403
Open
LukasWodka wants to merge 1 commit into
Open
docs(rfc): qualified identifier for the rootless spike + fix the LPI back-link#403LukasWodka wants to merge 1 commit into
LukasWodka wants to merge 1 commit into
Conversation
…back-link RFC numbers are assigned per repo, so a bare "RFC 0001" names four different documents across the org. Add the qualified ID (`RFC-CLIENT-0001`) to the header, in the bold-label style this document already uses, and give it an explicit `Draft` status. Also repoint the `**RFC:**` back-link. It pointed at `./0001-least-privilege-install.md`, which (a) does not exist on develop and (b) collided with this very file's number. That document is being renumbered to `0002-least-privilege-install.md` in #369, so the link now targets 0002. The link is dead either way until #369 merges — it is dead on develop today. If this lands first it stays dead for the gap; if #369 lands first it resolves immediately. No ordering requirement. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jul 25, 2026
Contributor
Author
|
👋 Heads-up — Code review queue is at 38 / 30 Above the WIP limit. The team convention is to review existing PRs before opening new work. Open PRs currently in Code review (oldest first):
Pull from review before opening new work. (This is a nudge from the kanban WIP check, not a block.) |
Contributor
Author
|
bugbot run |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 60ee638. Configure here.
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
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.
Summary
Two small fixes to
docs/rfcs/0001-rootless-spike.md, both consequences of RFC numbers being assigned per repo — a bare0001currently names four different documents across the org.RFC-CLIENT-0001, in the bold-label style this document already uses, and carries an explicitDraftstatus.RFC:back-link. It pointed at./0001-least-privilege-install.md— a link that is broken ondeveloptoday and that collided with this very file's own number.The within-repo collision
clienthad a genuine collision, not just a cross-repo one: the least-privilege-install RFC in #369 was also numbered0001, the same number as the rootless spike already ondevelop.That one is being renumbered to
0002-least-privilege-install.md(RFC-CLIENT-0002) in #369, so the back-link here now targets0002.0002was the next free number in this repo.No merge-order requirement. The link is dead either way until #369 merges — it is dead on
developright now. If this lands first it stays dead for the gap; if #369 lands first it resolves immediately.The stray duplicate file
docs/rfcs/0001-rootless-spike 2.md— a macOS copy artifact — was never committed to git. It existed only as an untracked file in a local working tree (git ls-filesandgit log --allboth return nothing for it).Verdict: it is a byte-for-byte duplicate of
0001-rootless-spike.md, not an inferior or diverged copy — both are 6842 bytes with md56544a40cd86f84940725bc8bcad29c3c, matching the copy onorigin/developexactly. Its only difference was a-rw-------permission bit. It has been deleted from the working tree; no repository change was required, which is why this PR shows no deletion.Public-repo note
clientis public. The added text names onlytracebloc/backendand issue numbers, both of which this document already referenced ondevelop. No customer names, hostnames or internal-only detail.Companion PRs
backenddocs/rfcs/README.md, private repo by design)cliclientRFC-CLIENT-0002: the renumber, status Accepted, un-draftedIn-flight: tracebloc/backend#1146 adds
backend/docs/rfcs/0002-platform-cost-autoscale-architecture.md. It will need the same header treatment (RFC-BACKEND-0002) when it merges — it is already listed in the index.Test plan
Docs-only; no chart, script or workflow touched. Verified the document renders and that the only link change is the intended
0001→0002repoint.🤖 Generated with Claude Code
Note
Low Risk
Documentation-only header and link updates with no runtime, chart, or workflow changes.
Overview
Updates
docs/rfcs/0001-rootless-spike.mdso cross-repo RFC numbering is unambiguous: the header now declaresRFC-CLIENT-0001, tells readers not to cite a bare "RFC 0001", and points at the org index intracebloc/backend.Status is explicitly Draft (prepended to the existing status line). The
RFC:back-link no longer targets./0001-least-privilege-install.md(broken and same-number collision); it now linksRFC-CLIENT-0002at./0002-least-privilege-install.md, aligned with the companion renumber in #369.Reviewed by Cursor Bugbot for commit 60ee638. Bugbot is set up for automated code reviews on this repo. Configure here.