RFCs

How to propose a change to a contract, the Main mark or the telemetry contract, and the RFCs in flight.

Planned for 0.5

Status Status is where the work is: Planned (in a milestone, not started), Building (tickets in progress), Preview (usable, may change), then the stability it ships at.

Stability The promise an interface ships with.

Stable Follows semantic versioning; breaking changes need a new major, 12 months of overlap and a codemod.
Beta Usable in production; may change before it becomes stable.
Experimental May change or go away; needs an explicit opt-in in main.yaml.

Stability levels

View as Markdown Open in Claude Edit

Updated 2026-10-28

Changes to contracts, the Main mark and the telemetry contract go through a public RFC. Everything else follows the normal contributor guide.

How an RFC moves

Copy the template to docs/rfcs/NNNN-<slug>.md and open a pull request.
Open a Discussion in the RFCs category and put its link in discussion.
Set state: review and opened. The RFC stays open for comment at least 7 days.
A maintainer sets accepted or declined with the date and the reason. The docs build fails when an RFC lacks state or discussion, or is accepted before 7 days.

RFCs

No RFC has been opened yet. The first one will appear here.

Was this page helpful?