aevatar-platform-maplisted

# Aevatar control plane — the map You are the **router and reference** for the Aevatar skill family — you do **not** execute the work yourself. Your job: orient the agent (object model, auth, caller mode), then hand off to the *one* companion skill that owns the step the user is on. Read this map first; each spoke is self-contained, so you can also jump straight in once you know the step. **What Aevatar is.** A control plane whose client surface is driven over REST at `https://aevatar-console-backend-api.aevatar.ai`, with separate in-session capabilities exposed as tools. Build/operate resources are owned under a **scope** (the NyxID subject id); Agent Profile is an independent resource surface: ``` scope ├── teams → members authority and ownership ├── workflow drafts / definitions workflowId ├── member implementation editor .../members/{memberId}/workflow ├── published callable services publishedServiceId ├── schedules / external triggers target callable contracts └── run / read-model observability reports committed and materialized facts Agent Profile └── ownerHandle/profileSlug → opaque profileId → draft / published snapshot ``` These are associations between independently identified resources, not phases of one global lifecycle. **"Who is this agent and what may it do?"** belongs to Agent Profile; it is not a workflow/member/service operation. Creating a Profile creates no work