Turn a mature technical debate into a bounded contributor choice and a maintainer response.
An RFC has several viable implementations. Discussion has produced evidence, but repeating arguments no longer moves the project toward a decision.
Define the complete obligation before opening the decision.
This dossier keeps the business trigger and the expected public record in one ordered view.
Why this needs a bounded decision
An RFC has several viable implementations. Discussion has produced evidence, but repeating arguments no longer moves the project toward a decision.
Ask the people who carry the consequence
Contributors who meet a declared activity rule, such as a merged change or active issue during the last year.
State the failure the contract must prevent
Discussion remains open indefinitely, or a binding result hides the compatibility test that maintainers can later use as a veto.
Match the ballot to the evidence needed
Use approval when maintainers need the option with the broadest acceptable support. Use ranked Borda when a complete fallback order matters.
State what the company will publish
Publish the chosen implementation, the compatibility checks, and any documented blocker that overrides an implementation-binding result.
Show what changed after the answer
Northwind CLI selected TOML, published the compatibility test results, and recorded the format as shipped in version 3.
Close an open-source RFC
Turn a debated implementation choice into a bounded contributor decision and a maintainer response.
Review the contractInspect the result state in context
See how this part of the contract remains attached to the other decision states.
Open the relevant demonstration stateClose an open-source RFC
The template opens a reviewable Create form. It does not submit or publish automatically.