Private preview

A hosted control surface for AI agent actions.

A2B Operator is being built to evaluate an agent action before it affects a business system, route sensitive decisions to a human, and preserve a reviewable trace of what happened.

Product boundary

  • A2B is the umbrella protocol and architecture.
  • Operator is the first hosted control product.
  • Workflow examples do not define the whole product.
  • Public subscriptions are not open yet.

The problem

Agents are gaining execution rights faster than businesses are adding control.

Once an agent can send a message, change a record, access data, or trigger infrastructure, the business needs to know who requested the action, which policy allowed it, whether approval was required, and what actually happened.

The intended Operator role

A control surface for governed agent execution, review and evidence.

  • Register agents and their declared capabilities
  • Evaluate proposed actions before execution
  • Return allow, deny, or approval required
  • Review sensitive actions through a human decision queue
  • Inspect the trace from request to decision and outcome
  • Separate agent activity by workspace

What exists and what remains open

The current implementation evidence is separate from public SaaS readiness.

Demonstrable today

  • Workspace, agent, policy, review, action, and ledger surfaces exist
  • Action-evaluation API routes exist
  • File-backed and optional PostgreSQL storage paths exist
  • Policy decisions and ledger traces can be demonstrated locally
Open work

Required before public SaaS

  • Production-grade user authentication and session enforcement
  • Server-side workspace membership and tenant authorization
  • API keys or service identities for external agents
  • Rate limiting, idempotency, monitoring, backup, and recovery evidence
  • Verified billing, entitlement, onboarding, support, and cancellation flows
Commercial status

Private preview, not a public subscription.

This page documents the product direction without claiming that onboarding, billing, tenant isolation, or production operations are complete.

Follow the build notes →

Operator implements A2B; it does not replace the A2B concept.

Start with the protocol definition, then follow the implementation evidence as the product matures.