Update RFC

Update the existing RFC so engineers can understand the current design, what has been implemented, and what remains unverified. Preserve its identity and agreed intent while incorporating concrete implementation evidence. Work in one document, with terminology near the end, followed by a references section when needed; keep its Rust-style structure or established repository format.

This is a public repository. Use public evidence or independently developed material suitable for public review. Keep restricted research outside the checkout; removing links or attribution does not make internal findings publishable. See RFC conventions for location and conventions.

Invocation

Run on an explicit instruction to update the RFC, including a combined request such as “verify the implementation and update the RFC.” Completing implementation alone is not authorization to run this skill.

Locate the RFC and evidence

Read repository guidance, the target RFC, and the supplied implementation references. Follow existing links and repository conventions to locate the relevant RFC when none is named. Ask only if multiple plausible documents imply materially different scope. If no matching RFC exists, report that and leave files unchanged; suggest create-rfc when useful. Preserve unrelated edits and update the existing numbered file rather than creating a replacement RFC.

Establish the implementation boundary: change or commit range, relevant code and configuration, verification results, and environment. A local diff is evidence of local work, not of merge or deployment. Prefer focused reads of affected interfaces and behaviors to a repository-wide audit.

Inspect relevant design records, implementation plans and available verification findings. Confirm their mapping to the code rather than inferring completion from a checked task list.

Build a working comparison between affected RFC claims and evidence: unchanged, implemented as designed, implemented differently, partially implemented, deferred, or still unknown. Keep this comparison in working context or required private notes, not a new companion design document.