capability
A draft authority statement schema, with agreed invariants and explicitly provisional representation.
Fetching schema…

DRAFT — schema definition only; this page issues no grant or revocation. See authority design notes.

DRAFT signed capability union: closed irrevocable-admin and revocable reader/writer variants. This authority statement is separate from mutable placement resources.

This authority statement extends the existing signed Blob envelope directly. Placement and integration with mutable resources remain separate, open design questions.

{ "anyOf": [ { "type": "hm://z6MkiAKDcRSzQ4zPZfnJcS5HYx5MwgN6MU9foHihJGrhqNBj/hm26/capability-admin" }, { "type": "hm://z6MkiAKDcRSzQ4zPZfnJcS5HYx5MwgN6MU9foHihJGrhqNBj/hm26/capability-revocable" } ], "description": "DRAFT signed capability union: closed irrevocable-admin and revocable reader/writer variants. This authority statement is separate from mutable placement resources." }

Learn this in the sync playground

Sync playground extension · 2026-10-23. Teaching prototype; no production protocol or schema adoption.

A Grant card is capability evidence, shown in the Permissions view. Its outgoing proof arrow identifies the evidence needed to validate its issuer’s authority. Being physically stored is different from being a valid active grant.

Read next: Grant · Proof edge.

Grant

A signed capability giving a principal a role on a resource.

The tentative roles are reader, writer and irrevocable admin. A grant depends on its issuer’s admin proof. Reader/writer grants are independently revocable by a same-scope admin; permanent admin ancestry is not revoked. Rights from independent active grants combine.

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

Unsubscribe anytime

Attributes
name
capability
summary
A draft authority statement schema, with agreed invariants and explicitly provisional representation.
Schema definitionThe schema this document defines, for other documents to use.
Fetching schema…