Skip to content

docs(rfc): qualified identifier for the rootless spike + fix the LPI back-link#403

Open
LukasWodka wants to merge 1 commit into
developfrom
docs/rfc-qualified-ids
Open

docs(rfc): qualified identifier for the rootless spike + fix the LPI back-link#403
LukasWodka wants to merge 1 commit into
developfrom
docs/rfc-qualified-ids

Conversation

@LukasWodka

@LukasWodka LukasWodka commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

Summary

Two small fixes to docs/rfcs/0001-rootless-spike.md, both consequences of RFC numbers being assigned per repo — a bare 0001 currently names four different documents across the org.

  1. Qualified identifier. The header now states RFC-CLIENT-0001, in the bold-label style this document already uses, and carries an explicit Draft status.
  2. Fixed the RFC: back-link. It pointed at ./0001-least-privilege-install.md — a link that is broken on develop today and that collided with this very file's own number.

The within-repo collision

client had a genuine collision, not just a cross-repo one: the least-privilege-install RFC in #369 was also numbered 0001, the same number as the rootless spike already on develop.

That one is being renumbered to 0002-least-privilege-install.md (RFC-CLIENT-0002) in #369, so the back-link here now targets 0002. 0002 was the next free number in this repo.

No merge-order requirement. The link is dead either way until #369 merges — it is dead on develop right 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-files and git log --all both 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 md5 6544a40cd86f84940725bc8bcad29c3c, matching the copy on origin/develop exactly. 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

client is public. The added text names only tracebloc/backend and issue numbers, both of which this document already referenced on develop. No customer names, hostnames or internal-only detail.

Companion PRs

Repo PR Contents
backend tracebloc/backend#1259 the scheme + the org-wide index (docs/rfcs/README.md, private repo by design)
cli tracebloc/cli#412 qualified IDs in the three cli RFC headers
client #369 RFC-CLIENT-0002: the renumber, status Accepted, un-drafted

In-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 00010002 repoint.

🤖 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.md so cross-repo RFC numbering is unambiguous: the header now declares RFC-CLIENT-0001, tells readers not to cite a bare "RFC 0001", and points at the org index in tracebloc/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 links RFC-CLIENT-0002 at ./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.

…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>
@LukasWodka

Copy link
Copy Markdown
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.)

@LukasWodka

Copy link
Copy Markdown
Contributor Author

bugbot run

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ 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.

@LukasWodka LukasWodka self-assigned this Jul 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants