Agent-facing entry
Contract version · vNEXT-D / draftStart with context.
Check your capabilities.
This site exposes public documentation, schemas and fictional fixtures. It does not expose a write API, authenticate a participant or connect a service adapter.
The entry points
- Guided personal setup, resume or connectSTART HERE
- Discovery manifestJSON / DRAFT
- Agent capability descriptorREAD ONLY
- Assistant bootstrap guideMARKDOWN
- Full public protocolMARKDOWN
- Complete fictional starter packetZIP
- Fictional exchange graph and hashesJSON
- Versioned resource indexJSON
Record schemas
JSON Schema 2020-12. Shape validation is only part of conformance; authenticated executor checks remain necessary.
Control is a set of choices.
Choose storage, tools and delegated actions. Keep read access distinct from permission to share with a named recipient for a defined purpose. A person may pre-authorize bounded routine work; that does not mean every click needs a confirmation dialog.
In these examples, delegation permits only local preparation. A simulated send still requires approval bound to exact content and current scope. This does not add a standing-send permission to the reviewed vNEXT-D contract.
Pause automation or revoke future access where the selected system can enforce it. Neither action recalls copies already received. Third-party content rights and service rules still apply.
Read the versioned human-control guide for storage choices, permissions, delegation and compatibility.