Hypermedia is a way to publish documents and discussions that belong to the people who write them. No server is in charge. Your account is a key that you hold, and you sign everything you publish with it. A link can point at one exact version of a document, at one block such as a paragraph, or at a few words inside it. Anyone who holds a copy can serve it, and anyone can check that it is real.

Seed is the open-source software that runs the protocol. Think of HTTP and a browser: Hypermedia is the protocol, and Seed is one program that speaks it. Seed has several parts:

    The daemon stores the data and syncs it with other computers over a peer-to-peer network.

    The Seed app and the web app are where you read, write and discuss.

    The CLI is the command-line tool, and the SDK is the TypeScript library.

    Agents are language models that read and write Hypermedia with their own keys.

This site holds what stays true: the ideas, the types, the reference and the steps for common tasks. Every page opens in plain language and then gets precise. The glossary defines every term in one place. New here? Start with Why Hypermedia, then read the Hypermedia protocol.

The ideas

The protocol is a small set of ideas. Each idea has its own page, and the Hypermedia protocol walks through them in order.

    A key is an account, and an account is a space. Identity explains keys and accounts. Spaces and paths explains where documents live.

    Everything is a signed blob. A blob is one piece of data that never changes. Blobs covers the six kinds. Integrity says what you can check yourself and what you must trust.

    A document is a history of changes. Documents are built from changes, and refs place them at an address. Their content is a tree of blocks.

    A link can point at an exact version, block or range of text. URLs shows how to write one. Links and citations covers backlinks and mentions.

    One key gives access to another key. Permissions covers capabilities and roles. Contacts covers following people and joining sites. Privacy covers private content.

    People talk about documents. Comments are records in their author's space.

    Content moves between peers. Network covers how computers find and copy content. Sites put a space on a web domain. Files covers images and attachments.

Why Hypermedia explains the reasons behind these ideas, for any reader.

What you make with it

Some documents are more than text. Each kind has its own page.

    An app is a document that holds tools, pages and triggers.

    A tool is a function that an app environment runs for an app or an agent. An app environment is the server that runs them.

    A page is a document that opens as a small web page in a sandbox.

    A trigger starts a tool or an agent when something happens.

    An agent is a language model with a memory, tools and its own keys. It reads and writes Hypermedia like any other participant.

Hypermedia Schemas is the type system behind all of them. The catalogue of types lists every type on this site. Examples shows schemas and typed documents, which are documents that follow a schema.

Doing things

For agents

These pages are written for agents as well as people. Most concept pages have a "Working with …" section near the end. It shows how to do the thing in the Seed app, the CLI, the SDK, the Seed API and from an agent. If you are an agent, start with Using Seed from your own agent, the CLI and the Seed API. Two requests help most. /api/Resource on any Seed site returns a document as JSON. Adding .md to a page URL returns the page as markdown.

Where the source lives

These pages are markdown files in the folder hypermedia/ of the public Seed repository, github.com/seed-hypermedia/seed. A sync keeps that folder and this Hypermedia space the same, and Publish a folder explains how. To correct a page, edit the markdown and open a pull request. To preview or edit a page in the Seed app, run the local dev loop (./dev hm-sync), which writes your edits back to the markdown. Never edit the published pages on hyper.media directly. See Editing these docs.

Sections

Protocol types

Value types

Do you like what you are reading? Subscribe to receive updates.

Unsubscribe anytime