Proposal: </h1>
<blockquote>
<p>Enhancement proposals (KEP/RFC-style) are how architectural and product change
flows — before first implementation they stage features against the
implementation arc (the <code>milestone:</code> field); after it, they are the change
process for the running system. Move this file from <code>draft/</code> to <code>accepted/</code>
and advance <code>status:</code> (draft | accepted | implemented | withdrawn) as it
moves. Early in the project this is deliberately lightweight; the discipline
matters more than the ceremony. If a decision is foundational rather than an
enhancement, it may instead warrant an ADR.</p>
</blockquote>
<h2>Motivation</h2>
<p>What problem does this solve? Why now? What is the user- or operator-visible need?</p>
<h2>Design</h2>
<p>The proposed change. Be concrete about interfaces and the affected components.</p>
<h2>Alternatives considered</h2>
<p>What else was weighed, and why this over those?</p>
<h2>Graduation criteria</h2>
<p>How do we know it is done and correct? What tests and what definition of done?
What telemetry confirms it in production?</p>
<h2>Backward compatibility</h2>
<p>Effect on existing data, existing deployments (version skew during rollout), and
the public API.</p>
<h2>Open questions</h2>
<p>Mark unresolved points explicitly.</p>
</article>
</main>
</div>
<div class="wrap">
<footer>
<div class="foot-row">
<nav class="foot-links" aria-label="footer">
<a href="https://github.com/getwyrd/vord">github</a>
<a href="/architecture/">architecture</a>
<a href="/adr/">decisions</a>
</nav>
<div class="foot-meta">Apache-2.0</div>
</div>
</footer>
</div>
<!-- SCRIPTS: render_site.py injects the Mermaid include only on pages that
contain a diagram; empty otherwise. -->
</body>
</html>