RFC-0000 · Design Q&A
Versioned draft snapshot
RFCs, reference catalogs, and evidence reflect Spec 3b2e3e7a114fb826b1445d39a48756b8fff629cd. Counts and pending/status notes belong to that snapshot. Read the dated project update for later progress.
Source repositories are private during staging. Links marked “repository access required” need access to the linked repository.
Q: What diagnostic namespace is canonical for RFC-0019 and earlier?
Status: Open
Source: RFC-0000 §6.1–6.3; RFC-0019 M01901; RFC-0006 M06520
Issue: §6 allocates M19xxx to RFC-0019 and says codes use a two-digit RFC ID plus a three-digit local code, while RFC-0019 emits M01901. That code has 01 in the allocated RFC-ID position; M06520 in RFC-0006 correctly has 06 and is not an example of the mismatch. RFC-0013 through RFC-0016 also declare Lean diagnostic ranges inside RFC-0001’s M01000–M01999 allocation. The short-code migration table covers only RFC-0001 through RFC-0005 and does not explain these forms. The same section says all codes use M, then allocates F, L, and R exceptions. The occurrence inventory records exact tokens and source lines but does not infer ownership or meaning.
Recommendation: Preserve allocated historical IDs and meanings as canonical, including registered M0xxxx legacy exceptions. Classify the inventoried tokens as definitions, aliases, examples, and cross-RFC references; define an exact code-to-owner registry and reject new collisions. The inherited narrative/decisions/diagnostic-codes.md record, consumer audit, and revised namespace proposal provide the evidence and acceptance criteria for owner review.
Q: Which RFC-0014 lint code means a breaking change under a minor or patch bump?
Status: Open
Source: RFC-0000 §6.2; RFC-0014 semver lint; RFC-0019 §§2, 4 Issue: The allocation table describes L01401 as a nonbreaking change published as MAJOR, while RFC-0019 uses L01401 as the blocking breaking-change-under-minor/patch code and L01402 as a warning. The table can direct publish implementations to gate on the wrong condition. Recommendation: Reconcile RFC-0014’s diagnostic definitions with the RFC-0000 allocation table and RFC-0019 publish gate, then add an exact code/meaning drift check.
Q: How is the seven-part required RFC structure enforced for the existing corpus?
Status: Open
Source: RFC-0000 §5; tools/check_rfc_structure.py; 57 authored RFCs
Issue: §5 requires scope, invariants, data contract, evaluation rules, failure modes, security, and compatibility in each RFC. The current structural checker validates the emitted RDF graph, not those Markdown sections, and many authored RFCs use different layouts. The corpus gate can pass without proving this requirement.
Recommendation: Either revise §5 to define a semantic checklist whose evidence may live in structured Lean/reference sections, or add a source-aware gate and migrate all RFCs to the required authoring layout before normative release.
Evidence: The seven-part layout audit distinguishes literal H2 coverage from substantive content and records why the current RDF structure check does not enforce §5.
Q: Can a derived MCP principal have a fixed rank in the trust order?
Status: Open
Source: RFC-0000 §§9.1–9.3; capability authorization in RFC-0006
Issue: An MCP Client derives trust from its authenticated backing identity, but the RFC also ranks Derived between Medium and Constrained. A client backed by an Install Operator or unauthenticated user cannot be assigned that fixed rank without contradicting its derivation rule. The rank also risks implying a higher role can bypass explicit capability checks.
Recommendation: Make trust evaluation depend on the authenticated principal and granted capabilities, with no fixed Derived rank or implicit high-trust privilege.
Q: Which system operations require a workflow declaration?
Status: Open
Source: RFC-0000 canonical Actor definition; §§9.1, 9.3; RFC-0010 kernel transitions
Issue: System is described as the built-in reserved actor that needs no actor declaration, but §9.3 requires System principals to be declared in workflow definitions. Kernel-driven transitions and other internal operations may not belong to a workflow, leaving their principal status unclear.
Recommendation: Distinguish the built-in System principal from a workflow-scoped delegation, and require an explicit capability and audit record for every system operation without assuming a workflow exists.