title:
authors:
- <GitHub handle or team>
created: <YYYY-MM-DD>
last_updated: <YYYY-MM-DD>
status: draft
discussion: <GitHub issue URL>
rfc_pr:
implementation:
- <GitHub issue or pull request URL>
supersedes:
superseded_by:</h2>
<h1>RFC: <Title></h1>
<h2>Summary</h2>
<p>One paragraph describing the proposed decision.</p>
<h2>Motivation</h2>
<p>What user or engineering problem requires a decision, and why now?</p>
<h2>Goals</h2>
<ul>
<li>A concrete outcome this proposal must achieve.</li>
</ul>
<h2>Non-goals</h2>
<ul>
<li>A nearby concern this proposal deliberately does not solve.</li>
</ul>
<h2>Terminology</h2>
<p>Define terms whose meaning affects the proposal.</p>
<h2>Current state</h2>
<p>Describe the observable architecture or behavior today. Link repository
evidence where possible.</p>
<h2>Proposal</h2>
<p>Describe the public contract, component ownership, data and control flow,
lifecycle, compatibility, and platform behavior.</p>
<p>Place supporting assets in the sibling <code><issue>/</code> directory and reference them
with relative links:</p>
<pre><code class="language-md">
</code></pre>
<h2>Alternatives considered</h2>
<p>Explain the strongest alternatives and why they were not selected.</p>
<h2>Compatibility and migration</h2>
<p>Describe additive delivery, deprecations, breaking changes, rollback, and
release sequencing.</p>
<h2>Security, privacy, and telemetry</h2>
<p>State permission boundaries, sensitive-data handling, and what telemetry may or
may not contain.</p>
<h2>Implementation plan</h2>
<p>Split the work into independently reviewable increments with explicit parity
and rollback gates.</p>
<h2>Test and acceptance plan</h2>
<p>List the evidence required to consider the RFC implemented.</p>
<h2>Unresolved questions</h2>
<ul>
<li>A decision that must be made during review.</li>
</ul>
<h2>Decision record</h2>
<p>Complete this section when review concludes. Summarize material feedback,
accepted changes, rejected alternatives, remaining risks, and final disposition.</p>