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
- Copy
0000-template.mdtoNNNN-<short-slug>.mdusing the next free number. - Fill in the design, compatibility, conformance, and implementation sections.
- Open a pull request or, in owner-led mode, commit it with the implementation.
- The project owner accepts, requests changes, or rejects the proposal.
- 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. - Accepted RFCs move to
accepted; after the implementation ships, they move toimplemented. Rejected and superseded RFCs remain as design history. - An RFC whose own deliverable is the decision — it defines no fields and ships no code — is
decidedrather thanaccepted, and that is terminal. See Status values for the full vocabulary and for howdecideddiffers fromaccepted.
Index
| # | Title | Status | Affects |
|---|---|---|---|
| 0001 | Locale negotiation | implemented | format, protocol, core, conformance |
| 0002 | Module signing | implemented | protocol, core, conformance, tooling |
| 0003 | Custom asset-class declarations from modules | implemented | format, protocol, core, conformance, tooling |
| 0004 | Conformance test runner v2 (language-agnostic) | implemented | protocol, core, conformance, tooling |
| 0005 | Stochastic calculations | implemented | protocol, core, conformance |
| 0006 | Hospitality reference module | implemented | core, conformance, tooling |
| 0007 | Sensitivity tables as a calc primitive | implemented | protocol, core, conformance |
| 0008 | Lease-up modeling | implemented | protocol, core, conformance |
| 0009 | _meta v2 sub-object reorganization | implemented | format, protocol, core, conformance |
| 0010 | Signed blocks | implemented | format, protocol, core, conformance, tooling |
| 0011 | Capability tokens for write authorization | implemented | protocol, core, conformance |
| 0013 | Embedding-based corpus retrieval | draft | protocol, core, conformance |
| 0014 | Extensible multi-format interchange | implemented | format, protocol, core, conformance, tooling |
| 0015 | Portfolio and relationship profiles | implemented | format, protocol, core, conformance, tooling |
| 0016 | Signed deterministic verification receipts | implemented | format, protocol, core, conformance, tooling |
| 0017 | .uw.md Lite / .uwx.md Extended source split | implemented | format, protocol, core, conformance, tooling |
| 0018 | Composable document profiles and deal packages | implemented | format, protocol, core, conformance, tooling |
| 0019 | Mixed-use composition as a document shape | implemented | format, protocol, core, conformance, tooling |
| 0020 | Align the format spec and examples with .uwx.md | implemented | format, protocol, conformance, tooling |
| 0021 | Composable UWX documents — externalization, composites, rollup receipts | implemented | format, protocol, core, conformance, tooling |
| 0022 | Market data as an attributable UW document | implemented | format, protocol, core, conformance, tooling |
| 0023 | A numeric model and a single quantization boundary | implemented | protocol, core, conformance, tooling |
| 0024 | Pin the iterative solvers so two engines agree on a root | implemented | protocol, core, conformance |
| 0025 | Scale percent displays by moving the point, not by dividing | implemented | format, core, conformance |
| 0026 | A typed capital stack — tranches, preferred equity, and stack-aware sizing | implemented | format, protocol, core, conformance, tooling |
| 0027 | Declare every asset class's size intensive, once | implemented | format, protocol, core, conformance, tooling |
| 0028 | Make a missing required section a reportable defect | implemented | format, core, conformance |
| 0029 | Make stage requirements class-aware | implemented | format, core, conformance |
| 0030 | Make partial conformance mechanically checkable | implemented | protocol, core, conformance, tooling |
| 0031 | Reconcile the source vocabularies and close the unpoliced-write path | implemented | format, protocol, core, conformance, tooling |
| 0032 | State how _meta.provisional interacts with signing | implemented | protocol |
| 0033 | Scope capital_stack to one point in time | implemented | format |
| 0034 | Calendar-anchored cash flows — dated series, day counts, deterministic xirr/xnpv | implemented | format, protocol, core, conformance |
| 0035 | Distribution waterfall — state-and-verify promote, pref, and catch-up over a dated series | implemented | format, protocol, core, conformance |
| 0036 | IRR-hurdled waterfall tiers — a closed-form boundary, not a nested solve | implemented | format, protocol, core, conformance |
| 0037 | Cross-check resolution over variant maps, and a validation coverage channel | implemented | format, protocol, core, conformance |
| 0038 | Tax basis on stated return metrics | implemented | format, protocol, core, conformance |
| 0039 | Data-center module — the first product module on a module-declared asset class | implemented | core, conformance, tooling |
| 0040 | Variant roles — resolve cross-checks by a declared role, not a key name | implemented | format, protocol, core, conformance |
| 0041 | Explicit period addressing for the standard series | implemented | format, protocol, core, conformance |
| 0042 | Stated period inputs in refinement | implemented | protocol, core |
| 0043 | Contextual Excel period bindings | implemented | protocol, core, tooling |
| 0044 | Project verified lease-up amounts onto explicit cash dates | implemented | protocol, core, conformance, tooling |
| 0045 | Assemble explicitly covered property cash flows | implemented | protocol, core, conformance, tooling |
| 0046 | Document currency identity | implemented | format, protocol, core, conformance |
| 0047 | Property cash-flow input inventory | implemented | core, tooling |
| 0048 | Standalone UW document kit and package examples | implemented | conformance, tooling, documentation |
| 0049 | PostgreSQL JSONB lake adapter boundary | implemented | tooling, documentation |
| 0050 | Preferred equity with a split coupon | implemented | format, protocol, core, conformance |
| 0051 | Distribution waterfall dual-hurdle "any" mode | implemented | format, protocol, core, conformance |
| 0052 | Named exit sale deductions | implemented | protocol, core, conformance |
| 0053 | Tax abatements and reassessment basis | implemented | format, protocol, core, conformance |
| 0054 | Where per-lease economics live (decision) | decided | format, documentation |
| 0055 | Typed commercial lease clauses | implemented | format, protocol, core, conformance |
| 0056 | Typed rate hedges, escrows and the reserves that fund them | implemented | format, protocol, core, conformance |
| 0057 | The renovation draw, and capex that buys an expense reduction | implemented | format, protocol, core, conformance |
| 0058 | Expense recoveries and the CAM true-up | implemented | format, protocol, core, conformance |
| 0059 | Waterfall clawback as a terminal true-up | implemented | format, protocol, core, conformance |
| 0060 | The four tranche-class candidates (decision) | decided | documentation |
| 0061 | Keep protocol version labels synchronized | implemented | protocol, tooling, documentation |
| 0062 | Permit same-day cash-flow rows while refusing ambiguous selectors | implemented | format, protocol, core, conformance |
| 0063 | Admit disposition at the final calendar period's exclusive boundary | implemented | protocol, core, conformance, tooling |
| 0064 | Verify property reserve-account roll-forwards without netting expenditure | implemented | format, protocol, core, conformance, tooling |
| 0065 | Bind a stated reserve draw to an already-stated gross expenditure | implemented | format, protocol, core, conformance, tooling |
| 0066 | Resolve calc identifiers over variant-map sections the way cross-checks do | implemented | protocol, core, conformance, tooling |
| 0067 | Tenure and ground-lease contract | draft | format, protocol, core, conformance |
| 0068 | Manufactured-housing module — a community leased by the site, with park-owned homes as a second income line | superseded | core, conformance, tooling |
| 0069 | Declare the student rent-roll bed counts and pre-leasing dates the student pack already reads | implemented | format, protocol, core, conformance |
| 0070 | Bind outright replacement-cap funding to an exact modeled cash payment | implemented | format, protocol, core, conformance, tooling |
| 0071 | A calendar-date validity predicate for safe expressions | implemented | protocol, core, conformance, documentation |
| 0072 | Give frontmatter scenario a defined meaning | implemented | format, core, conformance, tooling |
| 0073 | Previous identifiers for module-declared asset classes | draft | protocol, core, conformance |
| 0074 | What a dependent module's declaration override means | implemented | protocol, core, conformance |
| 0075 | Read a rate hedge from the senior loan when debt_structure is a role map | implemented | format, protocol, core, conformance |
| 0076 | Refuse a stated rate hedge whose loan or cash lines cannot be selected | implemented | format, protocol, core, conformance |
| 0077 | Define exit proceeds to equity when the capital stack carries junior capital | implemented | format, core, conformance, tooling |
| 0078 | The protocol is verification: separate the standard from the starter products | implemented | protocol, format, conformance, core, tooling |
| 0079 | Verify stated metrics at their stated precision; one cash-on-cash definition | implemented | protocol, core, conformance, tooling |
| 0080 | Every official asset class is a builtin | implemented | format, protocol, core, conformance, tooling |
| 0081 | One format, one protocol: remove backward compatibility (pre-release cleanup) | implemented | format, protocol, core, conformance, tooling |
| 0082 | A borrower-underwriting document profile for a loan to an operating company | draft | format, protocol, core, conformance, tooling |
| 0083 | Split @uwmd/verify, the reference implementation of the standard, out of @uwmd/core | implemented | core, conformance, tooling |
| 0084 | Bind a document snapshot without discarding signed block attribution | implemented | protocol, core, conformance, tooling |
| 0085 | Keep full records as verification subjects and remove destructive compaction | accepted | format, protocol, core, conformance, tooling |
| 0086 | One purchase-price authority for data-center metrics, with the summary cross-checked | accepted | format, protocol, core, conformance, tooling |
| 0087 | Define the basis for hospitality revenue reconciliation | draft | format, protocol, core, conformance, tooling |
| 0088 | Resolve financial power and transcendental reproducibility | accepted | protocol, core, conformance |
| 0089 | Preserve extension variants in a complete versioned Envelope | accepted | format, protocol, core, conformance, tooling |
| 0090 | Admit required provenance actors with an explicit diagnostic | accepted | format, protocol, core, conformance, tooling |
| 0091 | Allocate the two required metadata boolean diagnostics | accepted | format, protocol, core, conformance, tooling |
| 0092 | Verify stated pro forma identities under declared conventions | accepted | format, protocol, core, conformance |
| 0093 | Close three metadata-shape diagnostic gaps | accepted | format, protocol, core, conformance, tooling |
| 0094 | Allocate three present-invalid metadata leaf diagnostics | accepted | format, protocol, core, conformance, tooling |
| 0095 | Allocate bounded optional metadata and provenance-reference diagnostics | accepted | format, protocol, core, conformance, tooling |
| 0096 | Allocate bounded stated-payload admission diagnostics | accepted | format, protocol, core, conformance, tooling |
| 0097 | Refuse invalid selected institution configuration before validation | accepted | format, protocol, core, conformance, tooling |
| 0098 | Declare the point in time of the capital stack and senior loans, and reconcile CC-03 per point | accepted | format, protocol, core, conformance, tooling |
| 0099 | Verify each dictionary metric wherever the document states it | accepted | format, protocol, core, conformance, tooling |
| 0100 | Refuse negative sizes, counts, areas and rents | accepted | format, protocol, core, conformance, tooling |
| 0101 | Refuse every present source value outside the actor grammar | accepted | format, core, conformance |
| 0102 | A structured block opens only on a three-backtick json line | accepted | format, conformance, tooling |
| 0103 | Four metric dictionary corrections — USALI F&B gross margin, data-center mark-to-market and drawn power, booked rooms revenue | accepted | format, core, conformance, tooling |
| 0104 | Validation issue field paths are dotted paths from the payload root; issue order is not normative | accepted | protocol, core, conformance |
| 0105 | Name the field each financial-validity threshold reads, and check each stated home | accepted | format, core, conformance |
| 0106 | Refuse a structured block whose JSON is not an I-JSON object | accepted | format, protocol, core, conformance |
| 0107 | Give the LTC band a Format-defined home and an FV code | accepted | format, protocol, core, conformance |
| 0108 | Align the §4.17 validation section's vocabulary with the validation result | accepted | format, conformance |
| 0109 | Report financial-validity findings as deal flags, not record errors | accepted | format, protocol, core, conformance, tooling |
| 0110 | Name the §4.17 financial_validity entry's band "band", as RFC 0109 does | accepted | format, conformance |
| 0111 | Verify each record under the rule set of the version it declares | accepted | format, protocol, conformance, core |
| 0112 | Remove the retired agent host layer vocabulary from the standard | accepted | format, protocol, core, conformance, tooling |
| 0113 | Define hospitality occupied room nights as paid room nights sold | accepted | format, conformance |
| 0114 | Record the area measurement standard behind per-area metrics | accepted | format, protocol, core, conformance |
| 0115 | Portable conformance subcommands for every Verifier obligation | accepted | protocol, conformance, core |
| 0116 | Stage readiness by class section, a scope minimum in Format fields, and present meaning stated | accepted | format, protocol, core, conformance, tooling |
| 0117 | Extend the size contract to mixed-use component sizes and guard the per-size component metrics | accepted | format, protocol, core, conformance |
| 0118 | Refuse closed frontmatter values outside their vocabularies | accepted | format, protocol, core, conformance |
| 0119 | Compare NOI by absolute difference when it is zero or negative (CC-05, CC-06) | accepted | format, protocol, core, conformance |
| 0120 | Preserve selected-source cash-flow structural findings | accepted | format, protocol, core, conformance |
| 0121 | Bound CS-01 to tranche identities and required members | accepted | format, protocol, core, conformance |
| 0122 | Make DQ-05 date parsing deterministic | accepted | format, protocol, core, conformance |
| 0123 | Recompute dictionary-defined receipt results without a starter pack | accepted | format, protocol, core, conformance |
| 0124 | Require an explicit rule-set declaration in every source representation | accepted | format, protocol, core, conformance |
| 0125 | Verify data-center purchase price per stated rentable square foot | accepted | format, protocol, core, conformance |
| 0126 | Verify the stated land carry-NOI identity | accepted | format, protocol, core, conformance |
| 0127 | Portable receipt engine identity in conformance | accepted | protocol test configuration, conformance, Python |
| 0128 | RFC0092 admission, ledger roles and reports | accepted | protocol, schemas, reference verification, conformance |
| 0129 | Catalog document families and three attributable fact profiles | accepted | format, protocol, reference library, conformance | | 0130 | Give indeterminate receipt verification a distinct nonzero exit | accepted | protocol, conformance, tooling | | 0131 | Preserve authored sparse-statement aggregates | accepted | | 0132 | Separate physical and economic occupancy | accepted | | 0133 | Align malformed input-hash diagnostics | accepted |
0012 is an unused number, left as a gap so existing references keep their meaning. RFC 0017 is retroactive: it documents a change that shipped before its RFC was written, and records that process failure rather than hiding it. See its Process failure section.
Status values
This is the authoritative list. An RFC's frontmatter status: must be one of these values, and npm run verify-indexes fails on any other.
- 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, and this RFC itself still promises implementation that has not shipped.
- decided — terminal. The RFC's own deliverable is the architectural or design decision, and it explicitly promises no implementation of its own.
- 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.
accepted versus decided
The test is what this RFC promises, not whether any work remains in the area.
A decided RFC may identify implementation that a separate future RFC would have to carry. That deferral does not demote it to accepted, because the deferred work was never this RFC's deliverable — there is nothing here left to ship, so it never becomes implemented.
RFC 0054 is the worked example: it decides where per-lease economics live, states outright that it "defines no fields and implements nothing", types the lease clauses through RFC 0055, and defers the periodic series until a consumer exists. It is decided, not accepted, even though it names future work.
Use accepted when the RFC in hand describes a change that is still owed.
When status changes, edit the RFC's frontmatter and update this index.