docs(2347): rfcs is main-only, so the standard says so

[LukasWodka]

Closes the prose half of backend#2347. One line in org-standards.md.

The develop-first rule named docs as its sole exception. rfcs has the same shape and the same reason — it publishes no artifact, has no deploy stages, and is not on the release train — so a promotion gate there has nothing to gate.

The machine-readable side already said this

No inventory change is needed, because repo-inventory.yml has described rfcs as a single-branch repo all along:

• release_train: false, so audit_branch: develop-first-on-train already resolves to the default branch (main), not develop.
• The develop role carries exempt: *no_develop_branch_single_branch_repo — "single-branch repo: main is the only integration branch, so there is no develop to protect. Structural, not a gap."

So the prose was the drift, and this line now follows the inventory rather than the reverse. Stated as a class with its members named and pointed at the derived source: a bare list drifts, and a bare class invites argument about who is in it.

Why nobody caught it

The conformance guard flags a stale exemption only when the role's branch appears AND carries protection. rfcs/develop existed and was completely unprotected, so the contradiction between an inventory saying "there is no develop" and a live develop branch was invisible by construction — exactly the staleness rule that anchor's own note spells out after .github#196.

That is also the argument for deleting the branch rather than protecting it: protecting rfcs/develop would make the guard start flagging a stale exemption, while deleting it makes reality match what both files already assert.

Sequence

• rfcs#45 reconciles the two branches (7 develop-only commits, including a 999-line RFC absent from main) and rewrites that repo's own Branching section.
• rfcs/develop is deleted after chore: promote auto-classify Deploy-from-Status sync to main #45 merges.
• This PR is independent of both and can land in any order.

Note on the sync: standards-sync is report-only on schedule, so this does not fan out on merge. The Monday audit will report the consuming repos as drifted until someone dispatches it with create-prs.

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation-only wording change in org-wide standards; no code, protection, or inventory behavior is modified.

Overview
Updates the branch-model exception in org-standards.md so main-only is a class (no artifact, no deploy stages, not on the release train) with members docs and rfcs, instead of naming docs as the sole exception.

The line now defers to repo-inventory.yml (release_train: false plus the single-branch exemption) as the authority.

^{Reviewed by Cursor Bugbot for commit 714161b. Bugbot is set up for automated code reviews on this repo. Configure here.}

[saqlainsyed007]

One line, and correct. Adds rfcs beside docs as the "no artifact, no deploy stages → main-only" exception, and crucially defers to repo-inventory.yml as the authority ("this line follows it, not the reverse") rather than creating a second source of truth. Consistent with how #293/#306 treat rfcs (release_train:false + single-branch exemption). LGTM.

[LukasWodka]

/fr-pass