Planning

docs/production-plan.md

@@ -16,7 +16,7 @@ Status: active engineering plan; **not launch or payment authorization**. Update
 | Payment before sale finalization | A paid sale must not complete or be included as a completed ownership sale on Wikideck until the agreed XMR payment has satisfied its confirmation/unlock policy. Payment notification/mempool presence is insufficient. |
 | Existing boundaries | No real processor access, credentials, invoices, transfers, genesis change, destructive migration or launch approval is authorized by this plan. Software licensing still requires an operator choice and publication. |
 
-**Current behavior is not changed by these decisions alone.** The public sandbox is still USD-priced with mock XMR amounts; the SHKeeper harness uses USD invoice requests. Those are migration targets, not the intended production pricing model. Existing orders must retain their agreed terms, not be silently reinterpreted as XMR.
+**Production settlement remains disabled.** The public sandbox now prices new v3 listings/orders in native XMR atomic units, with mock-only confirmations, fees, refunds and payouts; legacy v2 USD records retain their original terms. The disconnected SHKeeper harness still models USD invoice requests and is not wired to v3. No real XMR invoice, payable address, conversion, transfer or settlement was enabled. Existing records are not silently reinterpreted as XMR.
 
 ## 2. Resolve the cross-chain requirement before selecting architecture
 
@@ -136,7 +136,7 @@ Acceptance: signed release evidence packet; recorded unresolved accepted risks w
 
 First implementation increment: write the M0 threat model/ADR research questions and P1 XMR domain specification, then build exact amount/property tests. Do not spend the next increment adding another disconnected “live” scaffold. Each milestone must integrate with its actual callers, persistence, recovery, UI and failure tests before being described as delivered.
 
-First increment status: [M0 source-grounded investigation/threat model](settlement-feasibility.md) and [M1 amount/migration specification](xmr-domain.md) recorded. Shared exact amount and commission primitives are reused by existing mock/processor-lab callers; no native-XMR public marketplace migration, approved exchange protocol or live payment integration is claimed. Both milestones remain open against their full acceptance criteria.
+Next increment status: M0 source investigation and [concrete settlement/evidence choices](settlement-feasibility.md) remain open. M1 now has a signed v3 XMR-native mock marketplace path; the public USD-to-XMR rate was removed. Version-2 historical USD orders are preserved and can continue under their original terms; open USD listings are legacy read-only until seller retirement/relisting. This is not live settlement, a completed migration dry-run, or production milestone acceptance; payment and payouts remain mock-only, and live auctions remain a separate release gate.
 
 ## 5. Acceptance evidence and release discipline