Protocol Overview

WikiWe separates the collaborative relationship from the infrastructure that supports it. A few architectural ideas carry most of the weight.

Verifiable Records

A Verifiable Record is a canonical data object whose content, issuer, context, and authorization can be checked by a recipient, independent of where a copy happens to be stored. Copying a record to another database, repository, wallet, or archive never creates a different record — its identity comes from its content and signatures, not its location.

Agreement Channels

A continuing agreement is tied to an Agreement Channel — an addressed, identifiable stream of records through which parties establish membership, give notice, record authority, document performance, and preserve amendments. The same channel can be projected into a conversation view, a membership roster, or a decision log without changing the underlying records.

Reputation Wallets

Reputation is retained by, or for, the person it describes. A Reputation Wallet holds credentials, contribution records, feedback, and other reputation events under the subject's own control. A distributed commitment registry lets a wallet later prove an event occurred — and that nothing responsive to a stated scope was omitted — without publishing the underlying content to everyone.

Selective Disclosure and Scoped Completeness

A person can disclose a single credential (an existence claim), or prove that everything within a declared time period or topic has been disclosed (a bounded completeness claim) — without exposing their entire history to answer a narrower question.

Checkpoints and Continuity

Signed, periodic checkpoints let members and Hubs hold independent, tamper-evident evidence of the latest state an Administrator published. If an Administrator fails or is compromised, that evidence — not a single operator's say-so — is what lets participants evaluate and choose a legitimate successor.

None of this requires a blockchain, a financial token, or universal public disclosure. It can be implemented incrementally with ordinary public-key cryptography, signed files, Git repositories, and conventional databases. See the full white paper for the complete architecture, open questions, and references.