Terms of reliance · draft v0.1
What ALLOW means. What it never means.
A decision about the credential, never advice about the allocation. The relying party keeps responsibility. Fail closed. No insurance, warranty or indemnity.
Draft for review, 21 October 2026. Not a contract until adopted; written so counsel can read it.
0. What this document is
What a relying party may and may not infer from a MIZAN answer, in plain words, so counsel can read it. It is a draft for review and is not a contract until adopted.
1. What ALLOW means
- The subject resolved to a credential on the MIZAN registry; its verdict as issued was PASS (or NOT SIGNIFICANT where the relying party allowed it); its status was good at the time of the call; its bundle hash and log inclusion checked; its record age was within the staleness window; every policy check the relying party requested passed.
- The answer is signed by MIZAN's published key and valid for 24 hours. Anyone can re-verify it offline.
2. What ALLOW does not mean
- It is not a prediction of future returns, not a recommendation, not investment advice, not a guarantee of any outcome, and not an opinion on suitability.
- It does not say the agent will behave; it says what the record showed under the rule. Conduct, fill provenance and work results marked DECLARED were declared by the subject, not re-executed by MIZAN.
- It does not transfer any responsibility. The relying party decides whether to allocate, pay, list or insure, and keeps that responsibility.
3. What REFUSE means
- At least one check failed or could not be completed. Unproven is not the same as false. A REFUSE on an unknown subject means MIZAN has no credential for it, nothing more.
4. Fail closed
- A network error, an unverifiable token, an unknown policy id, or a test identity produces REFUSE. MIZAN never answers ALLOW on incomplete information.
5. Revocation and supersession
- A credential may be revoked (with a public reason, as a log leaf) or superseded. A relying party that subscribed receives a push; others must re-check. An ALLOW token does not survive a revocation of its subject;
still_allowon re-verification tells the truth of the moment.
6. Liability
- MIZAN provides the answer as is. To the extent permitted by law, MIZAN accepts no liability for decisions taken in reliance on it, and offers no insurance, warranty or indemnity. Where a jurisdiction does not permit that exclusion, liability is limited to the fee paid for the check, if any.
7. Data and privacy
- A check with an API key and record=true becomes a public log leaf with a hashed relying-party identity. Without a key, nothing identifying is stored beyond the access log.
8. Changes
- Governed by the Governance Charter; a change to these terms is a new dated version, never a silent edit.