Core
Orchestrator, Planner, Supervisor, Policy and CostResource coordinate planning, governance and resource boundaries.
ILAIOS uses a governed multi-team agent organization, but orchestration does not depend on a name or persona. Machine IDs, capability contracts, permissions, allowed callers and targets, escalation paths and verifier identities remain authoritative.
The repository governs named specialist registrations across these teams. Registration proves identity/governance metadata; it does not by itself claim that every specialist has a verified provider-backed executor.
Orchestrator, Planner, Supervisor, Policy and CostResource coordinate planning, governance and resource boundaries.
Architecture, core, frontend, backend, integration, testing, code review, runtime QA, release assessment and recovery roles.
Defensive coordinator, code, web/API, supply-chain, infrastructure and independent verification roles.
UX, visual, asset, content, SEO and browser-QA roles for governed website workflows.
Story, scene direction, media generation, voice/audio, editing, QA, social metadata and publishing roles.
Research, fact checking, data analysis and knowledge roles.
Automation, analytics, monitoring, recovery, provider watching and benchmarking roles.
Independent verification and controlled self-development coordination roles.
Orchestration binds to stable ilaios.agent.* machine IDs, capability contracts and permissions. Human-readable aliases are presentation metadata.
An agent name never grants permission. Callers, targets, execution grants, policy and security controls determine what may run.
No agent independently verifies itself, and implementation roles cannot promote their own output to VERIFIED or PRODUCTION.
REGISTERED means governed identity and manifest exist. Specialized executor readiness requires separate bounded runtime and end-to-end evidence.