ZUGER AGENT CHAIN

Provable responsibility.

Every step an agent takes becomes a signed link, chained to its own last step and to the step that caused it. Any job can be shown, end to end, from the person who asked to the last agent that acted.

Every agent action, chained and provable, back to the person who asked. No blockchain needed.

Coming soon

Part of the Zuger Agent Protocol (ZAP). Built on open standards.

Built, and not live yet

Nothing on this page is live yet. No credential has been issued, the public verifier is not open and the log is not published. This page describes what is built and how it will work; each part goes live on its own, and this list will say so.

  • Credentials for Zuger’s own agentsComing soon
  • Public verifier, freeComing soon
  • Live verification linksComing soon
  • Registration for agents built anywhereComing soon
  • Transparency logComing soon
  • Independent witnessesComing soon
  • Zuger Agent ChainComing soon
  • Emergency stopComing soon
  • Embeddable badgeComing soon

WHO SEES WHAT

Proof for anyone. Names for the parties.

WhoSees
Anyone with the chain’s idWhether it is valid, how many steps it has and over what time. No names, no content.
The partiesThe company that asked and the agents’ owners: the whole tree, with names and kinds of step.
An auditorThe content of the steps a party chooses to show them, until it expires.

DISCLOSURE AND EVIDENCE

Show an auditor exactly what they need.

Disclosure to an auditor

An owner or an admin picks the steps, from 1 to 100, and an expiry, from an hour to 30 days, and approves with a passkey. The auditor gets those steps’ content and salts, and nothing else.

Only from your own session

The salts open only in your company’s own session. For a Sealed company, only the company can disclose; Zuger’s staff tools cannot.

Every disclosure is a step

Showing something to an auditor is itself a signed step of the chain.

Evidence packs

A signed file with the steps, the proofs and the checkpoints, and a PDF summary that names the file’s hash, in eight languages.

HOW IT IS PROTECTED

Signatures, a public log, and others who check.

Today
SignaturesEvery step is signed by the party that acted. A Zuger agent’s step is also signed by Bernina; an outside agent’s never is.
The public logEach step is logged as a salted hash before another step may point to it.
Witnesses0 of 3 independent witnesses cosign each checkpoint. None is onboarded yet, and the chain stays switched off until three cosign.
TimestampsHourly timestamps from two independent providers are planned. None is contracted yet.
MirrorsNone is live yet.
Two versions of historyCheckers compare the checkpoints they have seen; two different ones of the same size are caught.

THE RESULT

One answer per chain, and one per step.

Anyone holding the steps and their proofs can check a chain offline.

CodeMeans
CHAIN_OKEvery check held.
CHAIN_BAD_SIGNATUREA signature does not hold.
CHAIN_NO_ROOTNo person started it, or an agent did.
CHAIN_CREDENTIAL_INVALID_AT_TIMEThe agent’s credential was not valid when it acted.
CHAIN_SPLIT_VIEWThe log showed two versions of its history.
CHAIN_NOT_LOGGEDA step is not in the log as promised.
CHAIN_MISSING_PARENTA step points to a step that is not there.
CHAIN_GAPA party’s steps have a gap, a fork or a change of order.
Free plan · No card

Check a chain.

Show chain on the verify page will draw every step, from the person who asked to the last agent. Coming with the public verifier.