aevatar-agent-profile-management

To create and publish an Aevatar agent profile, draft the profile, configure routing policies and tool ceilings, then validate the draft. Publishing requires exact Ornn skill binding facts like skill GUID, literal version, canonical name, and publisher ID.

ETag-based concurrency control for agent profile mutation prevents conflicting updates by requiring exact profile identity handling. You must provide the correct ETag during creation, updating, or publishing to ensure safe, closed request body mutations across agent management workflows.

Before publishing an agent profile, you must verify the exact Ornn skill binding identity facts including the skill GUID, literal version, canonical name, and publisher ID. This deployment-gated capability check ensures exact profile identity handling and prevents accidental overreach.

Yes, when managing agent profiles you can set tool authority ceilings, routing policies, and activation modes. These safety and routing controls enforce validation rules that prevent an agent from exceeding a strict tool allowlist during deployment-gated capability checks.

An Aevatar agent profile defines what an agent is, what it may do, and which exact Ornn skills it may bind. This distinction prevents confusing profiles with workflows, services, or schedules by focusing on strict identity handling and capability boundaries.

Agent profile validation fails when Ornn skill bindings lack exact identity facts. You must confirm the exact skill GUID, literal version, canonical name, and publisher ID, alongside a valid ETag and closed request body, to pass deployment-gated capability checks.