Applications

The manifest model, capability composition, install registry, and TEE backends.

Concepts

How Apps Work — The full-shape app: frontend + TEE backend + agent, each its own DID, wired by one user-consented delegation fan-out. Start here to build.
Manifest Model — App/data contract: namespace, default applications space, declared perms, optional did delegation target.
Capability Composition — App + backend manifests composed into one capability request and a single wallet prompt.
Install Registry — App-install registry under the account space (applications/ key-prefix) plus an account SQL index.
TEE Backends — TEE backend acts as a subset-checked UCAN delegate, never the key-holder.
Example: Listen — Listen as a worked example of an application built on the protocol, with a “how it was built” trace.