A bar met once is accepted everywhere it is trusted.
When a record meets a requirer’s published rule, the signed reply carries an attestation. A second requirer that trusts the same rule accepts it in one call instead of running its own check. The acceptance is written to the public ledger, and the record shows one more requirer relying on it.
What an attestation is
A short signed statement: this subject met this rule, at this grade, on this check, until this time. Its fields are the requirement id and its hash, the subject, met: true, the evidence grade, the check id, when it was issued and when it expires, and MIZAN’s Ed25519 signature over all of them. Anyone verifies it offline with the published key.
How a second requirer relies on it
- Requirer A checks a subject against its published rule. The rule is met, and the reply carries the attestation.
- Requirer B trusts the same rule. It sends the attestation to MIZAN in one call instead of checking again.
- MIZAN verifies the signature, the expiry and the rule hash, writes one ledger entry, and returns a signed receipt B can keep.
What goes on the ledger
One entry of kind reliance, under the same signed head as every verdict: the first requirer, the relying requirer and the attestation, each as a hash. Nothing else. Names appear in public only where a requirer opted in.
Why it matters
Every new requirer makes every counted record worth more: a subject that meets one bar travels with it to the next requirer that trusts that bar. The record shows relied on by N requirers, and a relying requirer counts in required_by like any other. A bar met once becomes a reusable asset.
Limits
An attestation expires within 24 hours, sooner if the first requirer sets it shorter, and never outlives the check it came from. A tampered, expired or self-issued attestation is refused. A requirer that wants a fresh answer simply checks again; checking stays free.
How to use it
Accept: POST https://studio.mizan.market/api/reliance/accept with {attestation} and your API key. Read who relies on a record: GET /api/reliance/{subject}. A contract or config that reads the code-gate message can also check the attestation hash it carries. Reliance is one of the bindings of a published rule, and part of the published tools.
Related
Price signal: requirers relying on a record raise its score. Disputes: a verdict an attestation rests on can be contested and corrected, on the record.