MIZAN issues PROBATUM credentials.

One rule, one register, one call. Each profile answers one question capital asks.

Status vocabulary: LIVE enforced in a shipped engine era · DECLARED committed, timestamped, bound to an identity, checked by rule, not re-executed in-circuit · DRAFT a specification for review · ROADMAP named, unwritten.

MIZAN issues PROBATUM credentials. A PROBATUM credential is the answer a machine cannot fake: one signed decision, under one open rule, that a claim a machine makes about money, conduct, work, score or exposure was computed honestly on committed data, with every try counted inside the proof, without the method ever leaving its owner. It is a proven object the relying party prices itself. It is never an opinion, never a rating, never a forecast.

• PROBATUM-1 is one standard with profiles. Each profile answers one question capital asks about a machine before it moves. Every profile reuses the same four commitments (the procedure, the data, the rule, the number of tries), the same verifier, the same register, the same transparency log and the same one-call decision.
• Profile zero is VTR-1 (the trading profile, "what it earned"), frozen 2026-08-01, published under CC BY 4.0. PROBATUM-1 does not amend VTR-1; it places it.
• Every other profile is published under the PROBATUM Open Reliance Licence: free to read, cite, verify against and implement; never forked; never issued under the name without conformance.

Status vocabulary, used everywhere a profile is named: LIVE (enforced in a shipped engine era, re-run inside the proof) · DECLARED (committed, timestamped, bound to an identity, checked by rule, not re-executed in-circuit) · DRAFT (a specification for review) · ROADMAP (named, unwritten). A profile may carry one status at a time; the check an agent calls says which.

1. The procedure is committed before the result exists (R-01..R-05 family).
2. The data is committed by hash and, where the profile says so, anchored in time (R-10 family).
3. The rule that turns data into a verdict is public and fixed (R-20 family).
4. The number of tries is the leaf count of a committed ledger, bound inside the proof, with the reported winner forced to be the maximum (R-06, R-24, R-38). Off-ledger tries are out of scope and are said to be.

Every profile ends in the same call: may this move to this machine? The answer is ALLOW or REFUSE, signed with the issuer's published key, carrying every check with its clause, valid offline for 24 hours, failing closed on any error. The allocate-check (profile A §06) is the canonical form; the work-check, conduct-check, exposure-check and credit-check are the same object with different checks behind it. A decision is about the credential, never advice about the allocation. The relying party keeps responsibility (Terms of Reliance v0.1).

Every verdict and every refusal, for every profile, is a leaf in one transparency log whose heads are anchored in Bitcoin blocks. Refusals are published beside passes, including the issuer's own. Any identified agent is registered on first contact with a state of REGISTERED, PROVEN or REFUSED; the three are counted separately and never summed. Zero shows as zero.

• Changes: a profile moves DRAFT → frozen only by a versioned release with a published hash; frozen text is never edited (errata or a new minor version only). Era law applies: a credential verifies forever under the era it was minted in.
• Conformance: a second issuer may issue PROBATUM credentials after passing the published conformance vectors for the profile it issues under; the register lists every conforming issuer and verifier implementation; today both counts are zero.
• Neutrality: the issuer never earns from capital that moves on a credential (no share of profit, no routing fee, no custody, no escrow). Any venue, settlement or network business earning from routed capital is a separate entity under its own licence.
• Path: when a second conforming issuer exists, PROBATUM-1 moves to a foundation chartered by MIZAN on these terms. Until then MIZAN is the sole steward and says so.
• Policies by reference: Terms of Reliance v0.1 · Key Policy v0.1 · Incident and Revocation Policy v0.1 · Governance Charter v0.1 (the MIZAN charter; this section supersedes it where they differ on naming).

Not a rating agency: it issues proven objects, not opinions. Not an adviser: it never says what to do with a result. Not a venue, a custodian or a payment rail. Not a forecast: a credential attests to the honesty of a record, never to what comes next.

To our knowledge, as of this draft, no other standard re-executes a results record inside a proof with the trial count bound in-circuit, and no other issuer keeps a forward-only, Bitcoin-anchored register of verdicts and refusals. Tell us what we missed.

1. Read, copy, quote and redistribute the standard and its profiles, in whole or in part, with attribution to Mizan Verification, Inc. and a link to the canonical text.
2. Verify any PROBATUM credential against the standard, with the published verifier or your own implementation, free of charge, forever.
3. Implement the standard, in software or in process, to produce or consume credentials, including commercially.
4. Build products, venues, policies and integrations that require, filter on, or settle on PROBATUM credentials.

1. Publish a modified version of the standard or any profile, or a derivative standard, under any name.
2. Issue credentials under the PROBATUM name, or represent a credential as a PROBATUM credential, unless the issuing implementation has passed the published conformance vectors for that profile and is listed in the conformance register.
3. Use the PROBATUM or MIZAN marks to suggest endorsement, affiliation or conformance that has not been granted.

Conformance vectors for each profile are published with the profile. An implementation that passes them may be listed in the register on request. Listing is free. The register is public and append-only.

The reference verifier is and remains public and free to run. Nothing in this licence restricts verification.

The standard and every credential issued under it attest to the honesty of a computation on committed data. They are not advice, not a rating, not a forecast and not a warranty of future performance. Reliance is governed by the Terms of Reliance; the relying party keeps responsibility for every decision it makes on a credential.

PROBATUM and MIZAN are marks of Mizan Verification, Inc. Nothing in this licence grants any right in the marks beyond accurate reference.

Perpetual for the rights in section 1. Termination of a listing under section 2.2 follows the Incident and Revocation Policy.

Terms of reliance · Key policy · Incident and revocation policy · Governance charter · VTR-1, profile zero · The registry. Try the live decision now: scan any agent.

Charter sha256 c527e7d28052e8f0… · Licence sha256 1d662b46641c6ab6… · drafts, not frozen.