RFC 0000 — <a class="headerlink" href="#rfc-0000" title="Permanent link">¶</a></h1>
<table>
<thead>
<tr>
<th></th>
<th></th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Status</strong></td>
<td>Draft / Accepted / Rejected / Superseded</td>
</tr>
<tr>
<td><strong>Author(s)</strong></td>
<td><name></td>
</tr>
<tr>
<td><strong>Created</strong></td>
<td>YYYY-MM-DD</td>
</tr>
<tr>
<td><strong>Last updated</strong></td>
<td>YYYY-MM-DD</td>
</tr>
<tr>
<td><strong>Supersedes</strong></td>
<td><RFC number, if any></td>
</tr>
<tr>
<td><strong>Superseded by</strong></td>
<td><RFC number, if any></td>
</tr>
</tbody>
</table>
<h2 id="summary">Summary<a class="headerlink" href="#summary" title="Permanent link">¶</a></h2>
<p>One paragraph. What is being proposed, in plain language.</p>
<h2 id="motivation">Motivation<a class="headerlink" href="#motivation" title="Permanent link">¶</a></h2>
<p>Why does this RFC exist? What problem are we solving? Who is hurt today
by the absence of this change?</p>
<p>Reference the specific section of the specification (e.g. B3.4) and / or
the relevant code paths.</p>
<h2 id="proposal">Proposal<a class="headerlink" href="#proposal" title="Permanent link">¶</a></h2>
<p>The actual proposal, in enough detail that an implementer could build
it without further input. Include:</p>
<ul>
<li>Data model / schema changes (with migrations if applicable)</li>
<li>API surface changes (with deprecation strategy if breaking)</li>
<li>Diagrams (Mermaid preferred)</li>
<li>Pseudocode for non-obvious algorithms</li>
</ul>
<h2 id="alternatives-considered">Alternatives considered<a class="headerlink" href="#alternatives-considered" title="Permanent link">¶</a></h2>
<p>What else was on the table? Why was each alternative rejected?</p>
<p>A blank "Alternatives considered" section is a sign the proposal hasn't
been pressure-tested. Include at least two genuine alternatives, even
if both are weaker than the chosen path.</p>
<h2 id="backwards-compatibility">Backwards compatibility<a class="headerlink" href="#backwards-compatibility" title="Permanent link">¶</a></h2>
<ul>
<li>Does this change the wire format, schema, or API in a way that
existing deployments must care about?</li>
<li>What's the upgrade path?</li>
<li>Are there feature flags or runtime checks involved?</li>
</ul>
<h2 id="security-implications">Security implications<a class="headerlink" href="#security-implications" title="Permanent link">¶</a></h2>
<p>Map this proposal against the <a href="../../threat-model/">threat model</a>. Does
it strengthen, weaken, or leave unchanged each in-scope threat? If it
introduces a new threat, document it.</p>
<h2 id="conformance-implications">Conformance implications<a class="headerlink" href="#conformance-implications" title="Permanent link">¶</a></h2>
<p>Does this proposal change what Level 1 / 2 / 3 conformance requires?
If yes, list the test additions or modifications.</p>
<h2 id="rollout-plan">Rollout plan<a class="headerlink" href="#rollout-plan" title="Permanent link">¶</a></h2>
<ol>
<li>Land RFC as draft, solicit feedback (14-day minimum).</li>
<li>Implement behind a feature flag if disruptive.</li>
<li>Update conformance suite.</li>
<li>Update specification document.</li>
<li>Cut a release.</li>
</ol>
<h2 id="open-questions">Open questions<a class="headerlink" href="#open-questions" title="Permanent link">¶</a></h2>
<p>Bullet list of things the author is uncertain about. Will be resolved
before the RFC is accepted.</p>
<h2 id="references">References<a class="headerlink" href="#references" title="Permanent link">¶</a></h2>
<ul>
<li>Specification section(s) touched</li>
<li>Prior RFCs</li>
<li>External standards</li>
</ul>
</article>
</div>
<script>var target=document.getElementById(location.hash.slice(1));target&&target.name&&(target.checked=target.name.startsWith("__tabbed_"))</script>
</div>
<button type="button" class="md-top md-icon" data-md-component="top" hidden>
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M13 20h-2V8l-5.5 5.5-1.42-1.42L12 4.16l7.92 7.92-1.42 1.42L13 8v12Z"/></svg>
Back to top
</button>
</main>
<footer class="md-footer">
<div class="md-footer-meta md-typeset">
<div class="md-footer-meta__inner md-grid">
<div class="md-copyright">
<div class="md-copyright__highlight">
Copyright © 2026 KpiFinity Inc. — Specification CC BY 4.0, software Apache 2.0.
</div>
Made with
<a href="https://squidfunk.github.io/mkdocs-material/" target="_blank" rel="noopener">
Material for MkDocs
</a>
</div>
</div>
</div>
</footer>
</div>
<div class="md-dialog" data-md-component="dialog">
<div class="md-dialog__inner md-typeset"></div>
</div>
<script id="__config" type="application/json">{"base": "../..", "features": ["navigation.tabs", "navigation.sections", "navigation.expand", "navigation.top", "navigation.indexes", "content.code.copy", "content.code.annotate", "search.highlight", "search.share", "search.suggest", "toc.follow"], "search": "../../assets/javascripts/workers/search.b8dbb3d2.min.js", "translations": {"clipboard.copied": "Copied to clipboard", "clipboard.copy": "Copy to clipboard", "search.result.more.one": "1 more on this page", "search.result.more.other": "# more on this page", "search.result.none": "No matching documents", "search.result.one": "1 matching document", "search.result.other": "# matching documents", "search.result.placeholder": "Type to start searching", "search.result.term.missing": "Missing", "select.version": "Select version"}}</script>
<script src="../../assets/javascripts/bundle.ad660dcc.min.js"></script>
</body>
</html>