Readiness statement
DMX Analytics, Inc. · Statement dated 1 November 2026 · Signed by the Administrator, Eileen Ma · Published under Operations Manual PB-19 · Mirrored at dmxanalytics.info/readiness · Not legal advice
DMX publishes this statement to disclose the operational, legal and governance conditions for two kinds of sale.
- Gate A, licensed data sales: closed.
- Gate B, settlement-referenced contracts: closed.
Gate A governs a licensed-tier data sale, where a buyer receives a published series and settles nothing. Gate B governs any contract, license or side letter that uses a DMX value as a settlement, valuation or reference input. This includes a reference-rights license for an indexation clause in a commercial contract. DMX offers no Gate B instrument until every Gate B line reads true and counsel review is recorded as obtained.
DMX's Administrator made this assessment. Unless a line names a third party, no outside auditor has reviewed the controls or evidence. A line marked true carries no regulatory approval, legal opinion or third-party certification. The oversight committee is not seated, and charter §15 governs every review and report named below.
Each line is assessed as of the signing date. Earlier statements remain in the archive listed under Record.
The regulatory perimeter, as assumed. No registration or authorization category in the United States covers a publisher of a reference value, and DMX holds none. DMX conducts itself as if Commodity Exchange Act section 6(c)(1) and Rule 180.1 apply to every contract that references a DMX value, including a commercial escalator (Decision 55, 5 October 2026). The controls on this page are the record of that conduct. Every representation DMX makes about the series concerns process: methodology version, calendar, archive, and prompt disclosure of any defect. DMX makes no representation about a value's fitness for any contract.
Gate A: licensed-tier data sale
| Line | Condition | Status | Since / evidence |
|---|---|---|---|
| A1 | License text current and version-stamped; Terms and Privacy Notice final | Not yet | Terms of Use and Privacy Notice are version 1.0 DRAFT with blank effective dates, pending counsel review. The registration service refuses production while either reads DRAFT |
| A2 | Redistribution rights bound for every jurisdiction in a delivered scope. Federal government works enter on their public-domain status. State series need a written redistribution grant (P1 or P2). Silent-terms jurisdictions enter the national aggregate only | In force | Redistribution audit, counsel extract of 9 September 2026; Decision 24. No licensed-tier scope has been delivered |
| A3 | Agreement carries no settlement, valuation or reference-input language; not-for-settlement clause present for indicative values | Not yet tested | No licensed-tier agreement exists. The clause is drafted in the Terms and carried as not_for_settlement: true in every indicative payload |
| A4 | This statement is published and current, with Gate B lines visible as not yet where they are | True | 1 November 2026, this statement. Supersedes the statement of 10 September 2026 |
| A5 | Pre-release review disclosed as single-person while it is | True | White paper 13.7.5; Operations Manual B.1 |
| A6 | Upstream use authorized. For each source in the licensed scope, DMX documents the source's data-use limits and its legal basis to collect, process, publish and license it. A source with an unresolved material limit stays out of the licensed scope | Not yet | Founder determination of 30 October 2026 covers the free national print only. Terms 9(g) requires documented authorization for paid delivery. The CDC WONDER (Centers for Disease Control and Prevention, Wide-ranging Online Data for Epidemiologic Research) commercial-use question is open, so a paid scope that includes the federal series fails this line |
Gate B: settlement-referenced contract
| Line | Condition | Status | Since / evidence |
|---|---|---|---|
| 1 | Roles split: Approver is separate from the Operator; Key custodian is separate from the Archive operator | Not yet | One person holds every role. The first role to hand off is Key custodian |
| 2 | Oversight committee: at least two independent members seated; minutes exist | Not yet | Charter drafted 19 August 2026; no member seated |
| 3 | Second capture agent live for every jurisdiction in scope, administered by a named third party under their own credentials, operator published; canonicalization rules published | Not yet | Capture runs on three separately hosted sites under one administrator: Mac and droplet with paired reads from 3 September 2026, and a Linode third site. Canonicalization rules are published in canon.py. A third-party administrator is still owed |
| 4 | Two named time-stamp authorities and the public anchor operating; tokens verifying for the last 30 days | True | First window 6 September to 6 October 2026 passed (Decision of 31 October 2026). DigiCert and Sectigo tokens on every attestation digest, roots pinned; OpenTimestamps anchor on every digest. Exceptions: Mac time-stamp tokens arrived about 5 hours late on 19 September; the Mac OpenTimestamps anchor lagged about 32 hours from 18 to 19 September. No token failed reverification. The droplet has no committed status file for 6 September |
| 5 | Basis factor βⱼ frozen for every jurisdiction in scope that could reach precedence step 3; the rest listed as excluded | Not yet | Frozen in PS-2026.1 for jurisdictions with paired history; the remainder are provisional and listed in Appendix G; full freeze at the first rebalancing |
| 6 | First settleable reference month published per jurisdiction in scope, and the first referenceable date of T12 for every jurisdiction and the national series | Not yet | Go-live print under PB-17 was print 2026-10-15, released 16 October 2026 and indexed as first_framework_print. It published no settled values: the archive holds no settlement extract, and its correction 2026-10-15-r1 ran with settlement deferred |
| 7 | Off-site backup restored at least once in the last 90 days with hash verification | True | Restore drill P9, 6 September 2026: snapshot restored on a separate host, integrity verified, supply run receipt #3 reproduced to the float. Next drill due by 5 December 2026 |
| 8a | Credentials register current and held outside DMX's own systems | Not yet | The register exists (ops/DmxPb19CredentialsRegister20260823.md) inside DMX's own repository. No adviser or counsel holds a copy |
| 8b | Funded escrow: required escrow E, amount funded, horizon H | Not yet; E not yet sized | Rule fixed 9 September 2026: the term test reads the referencing contract; funding due before the earlier of the first adjustment date and thirty days after the first fee. The order of funding and offer is under counsel review against the opening rule. E: not sized, two custodian quotes requested. Funded: 0. H: none, no reference-rights license exists |
| 9 | Operator-unavailable procedure executed once as a drill | Not yet; blocked | The PB-20 drill runbook was prepared 10 September 2026. The drill needs a designated backup operator, and none is named |
| 10 | Counsel review: written view that tiered indicative access is separate from pre-release access; license text carrying the not-for-settlement and settlement-object clauses; reference-rights license text naming settled values only, the object per jurisdiction, the V(m) print as earliest adjustment date, and DMX as calculation agent | Not obtained | The argument is stated as DMX's own view in white paper 13.7.7 and Operations Manual C.2. The reference-rights license is not yet drafted |
| 11 | Heartbeat and pager live; last month's service-level report produced from it | Not yet | Liveness monitor runs on all three sites and pages by email through Postmark. Green monitor runs ping a Healthchecks.io heartbeat, which catches a silent monitor from outside DMX. The monthly service-level report produced from it is still owed |
What a reader should take from this page
Gate A remains closed. Three items are open: final Terms and Privacy Notice, a tested paid-tier agreement, and source-use clearance for the licensed scope. Completed infrastructure controls do not authorize a sale on their own. Each item needs separate evidence before production access opens.
Gate B remains closed, and this page will say so until it opens. Lines 4 and 7 are true. Lines 1, 2, 3, 8a and 9 wait on people: an independent approver, two committee members, a third-party capture administrator, an adviser holding the credentials register, and a backup operator. Lines 5 and 6 wait on the print calendar and the first rebalancing. Lines 8b and 10 need money and counsel. Line 11 needs the monthly report. The 15 October 2026 release was 1,653 minutes late because the signing step needed the operator by hand. Lines 9 and 11 are the controls for that failure.
Record
Source of record: ops/readiness/statement.md in the dmx-engine repository, under version control. The site page at /readiness is a mirror of this file and is regenerated from it at each new statement. A per-licensee copy is written to ops/readiness/<date>-<licensee>.md and referenced in the contract file when any Gate B instrument is signed.
Each statement records the conditions verified on its date. If any condition later fails, expires or changes materially, DMX issues a new statement and, where it applies, an incident report under PB-19 and notice to affected licensees. Earlier statements stay archived and are never edited.
Previous statements:
- 10 September 2026:
ops/readiness/archive/StatementV0120260910.md