Overview

What TP Social is and how to navigate these docs.

What you'll find here

These docs cover everything you need to publish to a TP Social registry, verify a signed page yourself, or implement a client that talks the protocol.

If you're new, start with Quick start — it walks through claiming a handle, installing the desktop client, and publishing a first page in about ten minutes.

If you're building tooling, Protocol is the canonical reference for handle naming, the resolve endpoint, the signing scheme, and the sandbox model that lets clients render untrusted HTML safely.

If you're integrating an existing system, the API reference lists every HTTP endpoint this registry exposes, the bodies they accept, and the responses they return.

If you're building the TrustPlane app or anything on the social layer, the API reference has three sections for you: The app: pairing and what a side sees, Experiences, people, groups inside a group, and A group's look. This registry is also the namespace authority for trust://sa/@handle names — see Names on the trust web.

A few principles to set expectations

The registry is one node, not the network. We host signed pages and resolve handles. We don't own your content, your seed, or your identity. If we ever go away, your pages remain verifiable against any copy.

The desktop client is the only thing that holds your seed. This registry will never ask for it, and there is no recovery mechanism for losing it. Treat it like a hardware wallet.

The spec is plain English. We try to keep it short, exact, and free of optional behaviour. If you find ambiguity, file it — that's a bug in the doc, not a bug in your implementation.

Conventions in these docs

Code blocks contain text you can paste verbatim.
§9.3-style references point at the canonical Protocol Spec sections.
We use @alice for the example handle and hello for the example slug throughout.