VerifableStart a recordOpen app
Docs · Agent-assisted publication

The agent may draft. It may not publish.

Today an agent can prepare a draft from a public Product Passport URL, but it cannot publish. A person must review disclosure and use the normal publish action. Portable mandates and production Wallet authority are not available in this flow yet.

What a real mandate must say

A real mandate must become a verifiable record naming, for one agent against one connected account:

  • a purpose — what the agent is for, in plain language;
  • independent may-read, may-draft, may-publish, and may-reply flags;
  • the record types, projects, and passports the mandate is allowed to touch;
  • a validity window — a start, and an optional end; and
  • a human-approval requirement — always, only for external publication, only for replies, or never.

Every flag will default closed. That enforcement is not yet supplied by a portable Wallet mandate in the AT Protocol feature, so the public product does not claim it today.

The current executable boundary

The integration-tested behavior is narrower than a general mandate:

May prepare a draft from the selected public passport URL. May not publish. The draft endpoint has no AT Protocol OAuth authority.

A later, controlled mandate

A future mandate may allow an agent to propose factual availability updates, but only when those updates are derived exclusively from already-approved public passport fields, and only after a human previews the exact text before it goes out. Nothing broader is available to the current agent.

Provenance and confirmation

The current composer marks an adopted draft as "Suggested by an agent" and routes it through human disclosure review. The publish request can retain the draft identifier in its in-memory audit entry. Confirming is a deliberate act by the person, not something the agent can satisfy on its own.

Before production use

Durable mandate, draft, decision and publication receipts; immediate revocation; production Wallet-session binding; and policy enforcement still have to replace the current in-memory development records before agent-assisted publishing is presented as a production capability.