Admin & agent

Orjanda brings human operators and AI agents to the same business model. Permissions and approval gates keep that relationship explicit.

Admin surface

The admin UI is derived from registered Documents. It gives people a place to inspect and work with the same entities represented in the Go model, rather than maintaining a second hand-built back office.

Agent tools

The same Document declaration can inform the tools exposed to an AI agent. A tool should be understood as an operation over a business entity, with the same context and permissions as its human counterpart.

Permissions

Permissions are the boundary that determines which people and agents may access or change a business object. Keep authorization decisions close to the operation, and test them for both human and agent callers.

Approval gates

Submittable Documents can represent a workflow in which a change needs explicit review before it becomes effective. Approval gates are a product boundary: make the transition visible to operators and require the right authority.