Agent Identity
Every agent has a governed identity, a lifecycle state, and a human accountability anchor. The human who sponsors an agent is recorded in every gate decision. That sponsorship cannot be disclaimed.
CLAIIM gives every AI agent a governed identity, binds it to a human accountability anchor, checks every action against policy, and records every ALLOW or DENY in Chron.
CLAIIM makes every one of those questions answerable before the action and after it.
Every agent has a governed identity, a lifecycle state, and a human accountability anchor. The human who sponsors an agent is recorded in every gate decision. That sponsorship cannot be disclaimed.
Every agent action passes through the gate before it happens. The gate checks identity, skill scope, and active policies. It returns ALLOW or DENY with a reason. Nothing bypasses it.
Every gate decision -- ALLOW and DENY -- is written to Chron immediately. Chron is designed as an append-only audit trail. The record exists before the action completes.
Without CLAIIM
ungoverned path
With CLAIIM
governed path
Every agent is sponsored by a named human. Their identity travels with every gate decision. Regulators see both the agent and the person who authorized it.
Agents belong to an organizational boundary called an AIORG. Agents cannot cross boundaries unless explicitly granted. Hierarchy is enforced at the gate.
Every change to a skill or policy creates a new version. Agents hold a pinned version -- silent updates are not possible. Chron records which version governed each decision.
Sensitive management operations require a second admin to approve. All actions inside the elevated window are tagged in Chron with the session ID.
CLAIIM deploys inside your infrastructure and uses your database. Chron, policies, agent records, and gate decisions remain under your control. Nivaya does not receive agent activity data.
Read install guideReady to gate your first agent?