Home
Tamper-evident records of machine state. A UST is a self-contained signed JSON object: some data about the world, at a moment, signed by whoever observed it. TLS secures the pipe; UST secures the payload — the guarantee travels with the data, so a transcript verifies the same whether it arrived from the publisher, a cache, a mirror, a file, another agent, or a chat paste.
It answers a question logging and tracing can't: "how do I prove to a third party that exactly these inputs, sources and results existed at that time, were signed by that key, and were not changed since?" Seal at creation → store anywhere → verify independently of the storage, offline, in one library call. No blockchain, no consensus, no per-record fees — the LIGHT tier is a key, a canonical form and a signature.
One signal the protocol never emits: "true." UST proves fixation, not truth — a publisher committed to these bytes at this time and cannot silently rewrite them. Whether the reading was correct is out of scope by construction; you learn whom to hold accountable and that nothing was tampered.
-
Concepts — the vocabulary (
ust_id, genesis, key-log, anchor, witness, partition) in one page. -
Assurance Tiers —
LIGHT → HIGH → TOP: what each verdict actually proves. - Verifying a UST — browser, Node, CLI, MCP — and the rule for AI agents.
- Chains and Layered Shards — one state as a hash-linked chain, graduated visibility.
- Reference Checker — the independent second derivation that is the trust boundary (the TCB).
- Tools and Surfaces — MCP, CLI, web-signer, connectors.
- Formal Model — verification as a measurability test (the precise semantics of a verdict).
-
Spec (normative):
spec/UST-1.0.md - Web verifier (nothing uploaded): https://thelabmd.github.io/UST-Protocol/
-
npm:
ust-protocol· Porting:PORTING.md - README (the full narrative): repo root
Status: release candidate. The wire format
ust:"1.0"is stable across all rc's — pin exact versions. External AI reviews are folded in structurally; an independent human cryptographic audit is pending. This wiki is the map; the spec and README are the territory.
