---
term: admin
category: service
status: canonical
authority: admin.elonn.local
---

Admin

The architectural component responsible for administrative observation, control, and management of Elonn's architectural components. Admin operates on the Admin Plane and is not a Service.

Owns:
- administrative observation (metrics, events, execution records, diagnostics, audit records) reported by other components
- authorized administrative operations issued to a component's administrative interface
- administrative and operational history (Admin Storage)
- administrative identity, authentication, and authorization

Allowed:
- Admin
- Admin Plane
- administrative interface
- administrative operation

Forbidden:
- admin dashboard (there is no single Admin Dashboard Object; see service dashboard)
- operator (unqualified; use Admin)
- admin service (Admin is not a Service)
- control plane / data plane (not Elonn vocabulary; use Admin Plane / Member Plane)

Notes:
- Admin has no Service Publication and no Service Contract, and is not indexed by Conductor's Service Registry. Conductor never selects Admin to fulfill a Member Call.
- Admin directs the component that owns the affected state to perform an administrative operation through that component's own administrative interface. Admin never bypasses a component's administrative interface to write to its storage directly.
- A component reports only the operational facts it is authoritative or uniquely positioned to observe. For example, Conductor reports the Service and Models transaction records it orchestrates in both directions, while Find reports only its own internal search performance (query latency, index health, Provider failures) rather than duplicating the reasoning requests Conductor already observed.

Related:
- admin plane
- member plane
- administrative interface
- conductor
- service dashboard