Weave docs are built for agents as first-class readers. Agents should start by loading the machine-readable endpoints, then follow the package-specific pages for the capability they need.

​
Agent-Readable Endpoints

EndpointUse
/llms.txtCompact directory of all navigable documentation.
/llms-full.txtFull documentation context in Markdown form.
/skill.mdCapability summary for agents and agent skill systems.
/.well-known/agent-skills/Skill discovery endpoint when custom skills are present.

​
Recommended Agent Flow

  1. Read /llms.txt to identify the relevant library.
  2. Fetch the target library overview, its custom workflow pages, and the API Surface page.
  3. Use /llms-full.txt only when broad architectural context is required.
  4. Prefer source repositories for code-level details and docs pages for system boundaries.

​
Capability Map

GoalPrimary pages
Locate peersweave-dht, weave-dht-daemon
Message peersweave-swarm, zer0-secret-stream
Share filesLocus, AgentFS
Store eventsTrace, Trace Blobs
Build social appsWOVEN, Nexus, Lens

​
Constraints

Agents should not assume global consensus, chain finality, or token economics. Weave is designed around local verifiability, signed events, and peer-to-peer replication.