MIZAN · changelog

Shipped, dated, on the record.

Every item below is dated by its own source: its entry on the public ledger, the engine eras page or the verdict changelog. Open any link and check the date yourself. The ledger now holds — entries.

  1. Daily service rollupledger

    One day of measurements for every service the recorder measured, committed to the ledger by a single root.

    entry #3169 →

  2. Service recordsrecorder

    The recorder opens a record for each agent service at its first measurement: facts measured by MIZAN, graded recorded.

    entry #1473 →

  3. The verdict protocol, mizan.verdict/1protocol

    Decision first, a compact signed token, one reason code on every refusal, status and revocation routes, and carriage through x402, AP2, ACP and an HTTP header.

    verdict changelog →

  4. Signed spending limitsdecide

    A principal signs what an agent may spend. The verdict can carry the limit, and it can be revoked on the record.

    entry #1230 →

  5. Acts fordecide

    A principal’s signed authority for an agent, so an answer shows who stands behind it.

    entry #1226 →

  6. Release, end to endmove

    A held payment can now be redeemed once, settled, cancelled or voided, each step an entry on the ledger.

    redeem #1223 → · settle #1224 →

  7. The release guardmove

    Money is held and moves only on a signed ALLOW against a published bar; a REFUSE keeps it held.

    hold #595 → · release #601 →

  8. An AI score proven from every attemptprove

    Every attempt of a counted evaluation re-graded inside a zero-knowledge proof, so the score is not anyone’s word.

    entry #518 →

  9. The counter counts itselfcount

    Every hour the ledger seals how many checks it served, committed as a Merkle root.

    entry #256 →

  10. Bars applied by id and hashmeasure

    A buyer’s bar is applied to a check by its fixed id and hash, so it cannot be reshaped after the fact.

    entry #223 →

  11. Counted AI evaluation runscount

    A run is declared before its first attempt and sealed after its last; every attempt counts.

    declared #188 → · sealed #189 →

  12. Requirements agreed in advancemeasure

    Two parties agree a bar with milestones on the ledger, fixed before it is used.

    entry #157 →

  13. Daily service probesrecorder

    Live agent services watched all day, each day committed by root.

    entry #154 →

  14. Successor signing key pre-committedtrust

    The hash of the next signing key is published ahead of any rotation, so the key cannot be swapped silently.

    entry #148 → · continuity →

  15. Agents on the ledgeridentity

    Agents register an identity in one call; each registration is an entry.

    entry #136 →

  16. Every attempt weighed, refusals includedcount

    Each attempt against a bar is recorded with its sequence number, and refusals are published like passes.

    entry #85 →

  17. Engine v12 liveengine

    The twelfth numbered engine release, stamped live. Earlier eras stay verifiable forever.

    engine eras →

  18. Engine v11engine

    The last of six canonical engine eras shipped in fifteen days, 11 to 25 July.

    engine eras →

  19. The public ledger opensledger

    Entry #0: the first credential on the record. The ledger has counted every day since.

    entry #0 →

  20. The first zero-knowledge credentialengine

    The genesis flagship: a result proven inside a zero-knowledge proof, the method never revealed.

    engine eras →

Protocol-level detail: verdict changelog · as JSON · every ledger entry