Skip to content

docs(rfc): status lines out of sync — implemented RFCs still DRAFT, four early RFCs missing status #182

Description

@eric8810

A sweep of rfc/*.md found the status lines out of sync with the code in both directions.

Implemented, still marked DRAFT / pending:

  • RFC-0016 (align with AI SDK) — still DRAFT (pending review), but Align the request pipeline with the AI SDK #164 just implemented its core (Core-owned retry layering, error domain alignment, timeout semantics) and Parse and validate tool inputs at the Core boundary #165 follows. The status should reflect what landed and what remains.
  • RFC-0021 (composite model routing) / RFC-0022 (MoA single fanout) — both still DRAFT (pending review), but Router/MoA are implemented and were just hardened in fix(go)!: eliminate lifecycle deadlocks #157 (lifecycle deadlocks, all-or-nothing construction). Update status or note the implementing PRs.
  • RFC-0005 (rename to aimux)Decided plan, pending execution; the repo, crates, and binaries are all named aimux. Verify nothing remains and close it out.

No status line at all:

  • 0002-provider-improvements.md, 0003-test-cassette.md, 0004-provider-inventory.md, 0005-protocol-conversion.md — early RFCs predating the > **Status**: convention. 0003 (cassettes) and 0004 (provider inventory) are actively used (cassettes mounted in provider tests; inventory superseded by the registry per chore(scripts): delete one-shot scripts, the fix_tool crate, and unused workspace deps #169's audit). Each needs a status line stating where it stands (e.g. IMPLEMENTED / SUPERSEDED-by).

Suggest handling as a single docs PR alongside the next RFC touch; nothing here blocks code.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions