UW Markdown RFCs

This directory contains the request-for-comments documents that precede any normative change to UW Markdown — the format spec, the protocol spec, the JSON Schemas, the conformance corpus, or the public API of @uwmd/core.

See GOVERNANCE.md for when an RFC is required and how it gets accepted.

Process

1. Copy 0000-template.md to NNNN-<short-slug>.md using the next free number.
2. Fill in the design, compatibility, conformance, and implementation sections.
3. Open a pull request or, in owner-led mode, commit it with the implementation.
4. The project owner accepts, requests changes, or rejects the proposal.
5. In owner-led mode there is no mandatory waiting period. After collaborative mode activates under GOVERNANCE.md, a normative RFC remains open for public comment for at least 14 days before acceptance.
6. Accepted RFCs move to accepted; after the implementation ships, they move to implemented. Rejected and superseded RFCs remain as design history.

Index

#	Title	Status	Affects
0001	Locale negotiation	draft	format, protocol, core, conformance
0002	Module signing	draft	protocol, core, conformance
0003	Custom asset-class declarations from modules	draft	format, protocol, core, conformance
0004	Conformance test runner v2 (language-agnostic)	draft	conformance, tooling
0005	Stochastic calculations	draft	protocol, core, conformance
0006	Hospitality reference module	draft	core, conformance
0007	Sensitivity tables as a calc primitive	draft	protocol, core, conformance
0008	Lease-up modeling	draft	protocol, core, conformance
0009	_meta v2 sub-object reorganization	draft	format, protocol, core, conformance
0010	Signed blocks	draft	format, protocol, core, conformance
0011	Capability tokens for write authorization	draft	protocol, core, conformance
0013	Embedding-based corpus retrieval	draft	protocol, core, conformance
0014	Extensible multi-format interchange	accepted	format, protocol, core, conformance, tooling

Status values

• draft — author is still iterating; reviewers may comment but the proposal is not stable.
• active — open for comment; the 14-day minimum applies in collaborative mode.
• accepted — merged with intent to implement.
• implemented — the change has shipped in a release; CHANGELOG entry exists.
• rejected — closed without merging the change. RFC stays in the directory.
• superseded — replaced by a later RFC; cross-link both.
• withdrawn — author pulled the proposal.

When status changes, edit the RFC's frontmatter and update this index.