Data Capabilities
Declare and publish your project's data world — what agents can see, safely change, and be told about. Published revisions are immutable; agents access them only through each agent's Data toggles.
View — Let the agent see current authoritative state. Read-only, curated to the fields you declare.
Action — Let the agent change real state safely — user-approved, idempotent by a runtime-minted action id, honest about ambiguous outcomes.
Event — Let the real world notify the agent that something changed. A signal, not a payload — current facts still come from Views.
These are not three HTTP methods but three agent-world primitives. Whether a given agent may use them is controlled per agent (Agents → Data); this page defines what exists.
Signing keys are minted on the first capability call.
Two credentials, two directions: your Project API key authenticates your backend calling Pouchy; this signing secret is what your backend VERIFIES calls from Pouchy with. They are deliberately separate.
The developer→Pouchy direction: your emitter signs each event with a per-source pesk_ key (POUCHY-SOURCE-V1), proving it came from the DECLARED source rather than any holder of a project credential. Required by capabilities published with signing: 'required'. Secrets are issued once — lost means rotate; rotation keeps the old key verifying until you retire it.
…
Published revisions are immutable — there is nothing to edit in place. Publishing a new version creates a new revision; sessions already pinned to an older revision may keep using it, and publishing is never revocation. To stop an agent using Data immediately, use that agent's live Data toggles.
Disable is the per-capability live lever: it takes effect on the very next turn for every session (existing ones included) and new plans see the capability as absent — while an in-flight reconciliation pinned to a revision keeps reconciling. Enable is just as live. Neither touches version history.
The durable record of every action the runtime dispatched: pinned revision, canonical intent, and the honest outcome — committed, rejected, or unknown. Unknown is never retried blindly; only reconciliation by the same actionId may move it. Journal rows are never swept.
Every accepted event, with its wake trail. Accepted means durably held and deduped — not that an agent turn ran, and not that anyone was notified; the wake column carries those separate truths. Receipts are kept for 30 days.