Skip to content

docs(rfc): RFC-009 — unify CLI access paths; align the RFC corpus - #206

Merged
aaltshuler merged 1 commit into
mainfrom
rfc/unify-access-paths
Jun 12, 2026
Merged

docs(rfc): RFC-009 — unify CLI access paths; align the RFC corpus#206
aaltshuler merged 1 commit into
mainfrom
rfc/unify-access-paths

Conversation

@aaltshuler

Copy link
Copy Markdown
Collaborator

Design only. Adopts the unify-embedded/remote-paths draft as RFC-009 with three alignment amendments, and brings the rest of the RFC corpus into one coherent dependency graph.

RFC-009 amendments (vs the raw draft)

  1. The "companion config-authority RFC" already exists and mostly landed — it's RFC-008 (stages 1–4 shipped). Referenced as a dependency; its remaining sliver (yaml-boot removal, stage 5) is noted as eased by Phases 4–5, not blocked.
  2. Open Q3 answered by the two-surface architecture: embedded graphs list enumerates the cluster catalog (read_serving_snapshot), never omnigraph.yaml; the verb becomes Both-capability.
  3. Phase 2 salvages prior art: PR Omnigraph Config v2 #139's review found the omnigraph-api-types extraction clean — seed from those commits (narrow cherry-pick, never wholesale), per the parked-branch discipline.

Plus concrete referee motivation from this cycle: the operator-alias positional bug and the write_text_if_absent flush bug are both no-referee-class failures a parity matrix would have caught.

Corpus alignment

  • RFC-002 header now maps each piece to its successor (007 landed / 008 landed / 009 proposed) with an explicit "don't implement from here without checking successors" warning — the umbrella stays, the foot-guns go.
  • RFC-007 gains the RFC-009 relationship (actor + keyed-credential chains as RemoteClient constructor inputs).
  • RFC-008 stage 5 cross-references Phases 4–5.
  • Dev index row added.

Sequencing note in the RFC: post-v0.7.0 (the release cut comes first — #202 is green and waiting).

🤖 Generated with Claude Code

Adopts the unify-embedded/remote draft as RFC-009 with three alignment
amendments: (1) the promised 'companion config-authority RFC' is RFC-008,
already landed through stage 4 — referenced, not re-proposed; (2) open
question 3 is answered by the two-surface architecture (embedded graphs
list enumerates the cluster catalog via read_serving_snapshot, never
omnigraph.yaml); (3) Phase 2 salvages PR #139's reviewed-clean
omnigraph-api-types extraction instead of rebuilding. Adds the
cycle's two no-referee bugs (alias positional, write-if-absent flush) as
concrete parity-matrix motivation, and RFC-007's addressing/credential
chains as RemoteClient constructor inputs.

Corpus alignment: RFC-002's header now maps each of its pieces to the
successor that landed or superseded it (007/008/009) with a do-not-
implement-from-here-unchecked warning; RFC-007 gains the RFC-009
relationship; RFC-008 stage 5 notes the Phases-4/5 easing; dev index row.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@aaltshuler
aaltshuler requested a review from ragnorc as a code owner June 12, 2026 14:33

@greptile-apps greptile-apps 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.

aaltshuler has reached the 50-review limit for trial accounts. To continue receiving code reviews, upgrade your plan.

@aaltshuler
aaltshuler merged commit e0d80c0 into main Jun 12, 2026
8 checks passed
@aaltshuler
aaltshuler deleted the rfc/unify-access-paths branch June 12, 2026 14:38
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.

1 participant