• Proposal Name: (fill me in with a unique identifier, my_awesome_feature)
• Start Date: (fill me in with today's date, YYYY-MM-DD)
• RFC PR: oceanbase/powercontext#0000

Summary¶

One paragraph explanation of the proposal.

Motivation¶

Why are we doing this? What use cases does it support? What outcome do we expect?

Guide-level explanation¶

Explain the proposal as if it were already included in PowerContext and you were teaching it to users or contributors.

This generally means:

• Introduce new named concepts.
• Explain the feature mainly through examples.
• Explain how users should think about the feature.
• Describe migration guidance, warnings, or error messages if applicable.
• Call out differences between existing users and new users if applicable.

Reference-level explanation¶

This is the technical portion of the RFC. Explain the design in sufficient detail that:

• Its interaction with existing features is clear.
• The implementation path is reasonably clear.
• Important edge cases are covered by examples.
• Compatibility, persistence, and API impacts are explicit.

Return to examples from the guide-level section and explain how the detailed design supports them.

Drawbacks¶

Why should we not do this?

Rationale and alternatives¶

• Why is this design the best option among the alternatives?
• What other designs were considered?
• Why were those alternatives not chosen?
• What is the impact of not doing this?

Prior art¶

Discuss related work from PowerContext, adjacent tools, or other communities.

If there is no prior art, say so. A new design can still be valuable.

Unresolved questions¶

• What parts of the design should be resolved before this RFC is merged?
• What related issues are intentionally out of scope?
• What follow-up decisions may need their own RFCs?

Future possibilities¶

Describe natural extensions of this proposal and how they may affect the project roadmap.

This section is for related ideas that are useful context but not required for accepting the current RFC.