Devory Agent User Interface

A governed interface for external AI agents — not a chat window

In active development

Devory Agent User Interface — AUI — is the governed interface through which external AI agents can act on behalf of authenticated users inside Devory. It gives an agent a structured way to discover approved capabilities, request scoped resources, submit operations and return auditable outcomes, without ever becoming an independent user or an unrestricted system principal.

What AUI is not

  • Not an unrestricted autonomous agent, and not an independent user
  • Not a replacement for human authority — every action traces back to a real user
  • Not a general-purpose chatbot
  • Not an agent with access to everything in Devory
  • Not production-ready or externally connectable without qualification and evidence

The delegation and audit model

Authenticated delegation

An agent never acts as itself — every operation is delegated by an authenticated human user and carries that user's authority, never more.

External-agent principal

A compliant AI agent is represented as a distinct, typed principal — never indistinguishable from a human clicking a mouse.

Capability discovery

Agents discover approved, catalogued operations by identifier — never a hidden or guessed action.

Resource scopes

Every request is bounded to explicit, granted resources — never open-ended access to everything in Devory.

Operation submission and lifecycle

Operations are submitted, tracked and resolved through a defined lifecycle, not fired and forgotten.

Confirmation and approval

Higher-risk operations require an explicit human confirmation boundary before they proceed.

Audit envelopes

Every operation an agent performs is wrapped in an auditable, traceable record.

Revocation and fail-closed enforcement

Access can be revoked at any time; when a check cannot be made, the operation is denied, not permitted.

Protocol foundations

These are the contracts AUI is built on today — not yet an externally reachable, publicly connectable service.

  • Capability protocol
  • Resource-scope protocol
  • Operation protocol
  • Operation lifecycle
  • Audit-envelope protocol
  • External-agent principal foundation

Current status

In active development

Protocol foundations are implemented — capability discovery, resource-scope and operation contracts, confirmation gating and audit envelopes. No externally reachable network transport exists yet, so external agents cannot currently connect to a Devory deployment over the public internet. External pilot integration is in development, not available now.

Building an agent integration?

Tell Devory what your agent needs to do — it directly shapes what AUI exposes first.