The operating problem
Agent systems combine a human owner, application, agent version, session, model, tool, and downstream resource. Losing any link weakens accountability and revocation.
The intended control surface
This capability is part of the reviewed product architecture, not a decorative console module.
- Human-to-agent identity chain
- Per-tool permissions and argument schemas
- Time, cost, and concurrency limits
- Human approval for high-risk actions
What exists today
User and team RBAC plus tamper-evident audit are implemented foundations. Agent identities, sessions, approvals, and tool events are not yet shipped.
Work with the implementation team
Reallexi is accepting architecture conversations with teams whose requirements can shape this production slice. An inquiry does not imply that an unshipped feature is available.
Frequently asked questions
Is this capability generally available?
No. The page describes a reviewed implementation direction. The current capability boundary is stated above and in the public changelog.
Can Reallexi evaluate our requirements?
Yes. Use the enterprise inquiry form without including credentials, private payloads, or regulated data.