Readiness statement
DMX Analytics, Inc. · Statement dated 10 September 2026 · Signed by the Administrator, Eileen Ma · Published under Operations Manual PB-19 · Mirrored at dmxanalytics.info/readiness · Not legal advice
This page states, line by line, whether DMX has met the conditions its own operations manual requires before two kinds of sale. It is published mostly reading not yet, on purpose. A dated, public checklist that is mostly negative is falsifiable and converts to positive one line at a time; silence is neither. Each line carries the date it became true, or the evidence that it has not.
Two gates. 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 under which a DMX value is a settlement, valuation or reference input, including a reference-rights license for an indexation clause in a commercial contract. No Gate B instrument is offered until every Gate B line reads true and counsel review is recorded as obtained.
Every review, approval and report named below is, at this date, a self-report by a single operator. The oversight committee is not seated. Charter §15 governs, and this statement says so rather than implying otherwise.
Gate A — licensed-tier data sale
| Line | Condition | Status | Since / evidence |
|---|---|---|---|
| A1 | License text current and version-stamped; Terms and Privacy not in draft | Not yet | Terms of Use and Privacy Notice are version 1.0 DRAFT, pending counsel review; the registration service refuses production while either reads DRAFT |
| A2 | Rights bound: every jurisdiction in a delivered scope carries a written redistribution grant (P1 or P2); silent-terms jurisdictions enter the national aggregate only, never a state series | In force | Redistribution audit, counsel extract of 9 September 2026; Decision 24; no licensed-tier scope has yet been delivered |
| A3 | No settlement, valuation or reference-input language in the agreement; 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 readiness statement is published and current, with its Gate B lines visible as not yet where they are | True | 10 September 2026, this page |
| A5 | Pre-release review disclosed as single-person while it is | True | White paper 13.7.5; Operations Manual B.1 |
Gate B — settlement-referenced contract
| Line | Condition | Status | Since / evidence |
|---|---|---|---|
| 1 | Roles split: Approver is not the Operator; Key custodian is not 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; charter §15 interim status applies to every report on this page |
| 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 | Two-site capture is live (Mac and droplet, paired reads from 3 September 2026) and the canonicalization rules are published in canon.py, but the second agent is self-administered, not third-party |
| 4 | Two named time-stamp authorities and the public anchor operating; tokens verifying for the last 30 days | Not yet; 30-day window running | DigiCert and Sectigo tokens on every attestation digest from 6 September 2026 on both sites, roots pinned; OpenTimestamps anchor on every digest. The 30-day condition is met on 6 October 2026 if verification holds |
| 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 are 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 | Publishes with the go-live print under PB-17, which has not run; every print to date is pre-framework |
| 7 | Off-site backup restored at least once in the last quarter with hash verification | True | Restore drill P9, 6 September 2026: 6 September snapshot restored on a separate host, integrity verified, supply run receipt #3 reproduced to the float; next drill due by 7 December 2026 |
| 8a | Credentials register current and held outside DMX's own systems | Not yet | The register exists (ops/PB19_CREDENTIALS_REGISTER.md) and is held inside DMX's own repository; no adviser or counsel yet 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; sized by rule, the fee first and DMX capital for any shortfall. E: not yet 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 | PB-20 drill not yet run; owed before the first reference-rights license |
| 10 | Counsel review: written view that tiered indicative access is not 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, labeled as such rather than as advice. 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 both sites and pages by email; the off-droplet heartbeat service and the monthly report produced from it are not yet in place |
What a reader should take from this page
Gate A is close and is blocked on one thing, counsel review of the Terms and the Privacy Notice, which is in progress through law-school clinic outreach. Nothing else on Gate A costs money.
Gate B is not close, and this page will say so until it is. Four of its eleven lines are structural and cheap: two committee members, an adviser holding the credentials register, a third party administering the second capture agent, and one drill. Three are on clocks: the 30-day time-stamp window, the go-live print, the rebalancing freeze. Two need money: counsel and escrow. Lines convert one at a time and each conversion is dated here.
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. 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. If any line on a dated statement is later found to have been false when signed, that is the one failure mode this page has, and it is treated as an incident under PB-19.
Previous statements: none. This is the first.