markdowneditor

RFC-NNNN: Feature or change title

Proposal needing review – sequence diagram included

使い方: Proposals needing async review before build. Set a review deadline; silence isn't consent – chase sign-off.

プレビュー

RFC-NNNN: Feature or change title

FieldValue
StatusDraft / In review / Accepted / Rejected
Author@you
CreatedYYYY-MM-DD
Review deadlineYYYY-MM-DD

Summary

Two to three sentences: what is proposed and why now.

Motivation

What problem does this solve? Who experiences the problem? What happens if we do nothing?

Goals

  • Measurable goal one
  • Measurable goal two

Non-goals

  • Explicitly out of scope, to preempt scope creep

Proposal

Detailed design. Include diagrams where they help:

sequenceDiagram
    participant C as Client
    participant S as Server
    C->>S: request
    S-->>C: response

API / interface changes

interface NewAPI {
  method(input: Input): Promise<Output>;
}

Data model changes

Describe schema changes, migrations, backward compatibility.

Alternatives

What else was considered and why this won.

Security & privacy impact

What new data flows? What attack surface? Any compliance impact?

Rollout plan

  1. Phase one – behind feature flag
  2. Phase two – gradual rollout
  3. Cleanup – remove flag, old path

Open questions

  • Question still unresolved

関連テンプレート