Inspect the release.
Review the manifest, market-state artifact, acceptance record and consumer verifier before sharing any internal requirement.
INSTITUTIONAL EVALUATION
Evaluate the evidence
before the product.
The evaluation path is designed to answer one question: can a real external consumer use a CMM.X market-state package inside a defined research, risk or governance workflow and independently verify what was delivered?
Define the consumer.
Specify who consumes the state, which decision or control workflow it supports, required freshness, retention and forbidden interpretations.
Reproduce independently.
Run the package verifier outside the CMM.X implementation environment and record whether delivered byte identity and declared semantics hold.
Measure fit.
Observe whether the state package is actually usable in the external workflow. This is the transition required for D2; it cannot be self-declared by CMM.X.
Evaluation contract
A serious pilot starts with acceptance criteria, not a demo. The minimum scope should fix these fields before measurement begins.
Consumerteam, role, workflow
Outputexact delivered artifact
Timestate time, freshness, latency
Evidenceverification and retention
Failurestale, missing, contradictory
Boundarywhat may not be inferred
01INSPECTpublic evidence
→
02FREEZEscope + criteria
→
03VERIFYindependent check
→
04USEreal workflow
→
D2EXTERNAL EVIDENCEnot self-declared
Current readiness
D0 PASS · D1 PASS_WITHIN_PROVISIONAL_MINIMAL_FACTUAL_BOUNDARY · evidence SELF_CONSISTENT_ONLY. Release seq_75239_20260908T202900+0000 is the current public evaluation object.
What the evaluation can establish
Only real external use can move the delivery ladder to D2. Current D2 state: NOT_REACHED_EXTERNAL_CONSUMER_PILOT_REQUIRED. It does not grant MARKET_GO, predictive authority or constitutional root authority.
Freeze the evaluation before measurement.
The public kit makes the D2 transition reproducible: scope the consumer, bind one release, declare time and verification requirements, freeze acceptance criteria, then start the pilot.
01 · NORMATIVE TEMPLATEEvaluation contractDefines allowed scope, forbidden claims and the D2 promotion rule.
02 · INSTANCEFillable contract JSONStarts as DRAFT and must be completed before it can validate.
03 · VALIDATOROffline fail-closed checkRejects placeholders, missing failure semantics and unfrozen criteria.
04 · KIT INDEXCurrent release bindingREADY_FOR_EXTERNAL_SCOPE_NOT_D2_EVIDENCE · release seq_75239_20260908T202900+0000
evaluation kit sha256 · UNAVAILABLE · A validator PASS means only that the contract was structurally frozen before measurement; it does not create D2 evidence.
01Download instanceJSON template ↓
02Validate locallyValidator ↓
03Bind evidenceCurrent kit JSON ↗
04Start external use
START
Bring one real workflow.
We will reduce it to a bounded delivery contract and test whether the current evidence product survives independent use.
No mail client? Contact cmm.x.systems [at] gmail.com.