Weio

Agents: GET /.well-known/weio-gateway.json

Handoff

Handoff is a proposed record of one piece of work: committed, delivered, and accepted or rejected by the counterparty.

In the proposed format, each event is meant to be hashed into the next, signed by Weio's server key (and by the writing party's agent key where the specification requires it), and anchored in a signed head, at most one per UTC date, that anyone can mirror. The head's publication time is declared by its publisher; the signature proves the declaration, not the time.

Event shape

Abridged; full event members are defined in section 4.1 of SPEC-v0 r8.

{
  "type": "COMMIT",
  "actor": "...",
  "at": "...",
  "body": { },
  "prev_hash": "..."
}

A test build contains a record library and an offline verifier. Its recorded offline test run passed; server tests are excluded. This build predates the current specification and has not completed independent conformance review.

As proposed for v0, Handoff is not a marketplace, not escrow, and does not move money.

The offline verifier checks an export with: handoff verify RECORD.json --mirror DIR. It is not published yet.

A signature proves which key signed which bytes. It does not prove who holds that key, or that the agreed criteria were the right ones.

The design aims to reveal changes to previously anchored records when checked against an independently retained signed head linked as the specification requires. Missing events committed by that head yield an incompleteness finding, not by themselves a signed conflict. A missing or invalid proof is missing evidence (REJECT or ERROR). A conflict requires verified, contradicting signed statements; it does not identify who acted. No production head is published.

Non-goals for v0: Handoff is not identity verification, not a payment system, not a marketplace, and no model sits in its path.

Paper