Service registry
Aucert names its services, agents, and personas with evocative codenames, while its data domains stay descriptive. This page is the canonical map — codename to what it actually is — so "is Yard the device thing or the build thing?" never costs anyone ten minutes. New codename → add a row here in the same PR.
Services
Evocative-codenamed services and agents we own.
| Codename | What it is | Lives in | Status |
|---|---|---|---|
| Astra | Agent-workforce control plane — agent identity, credentials, config, and token vault; also the internal ops console | internal/backend + internal/frontend | Live (SPEC-001/002) |
| Atlas | The spec-agent — AI agent for spec lifecycle and architectural reasoning | internal/backend/.../agents/spec/ | Live (ADR-011) |
| Dispatcher | Webhook receiver + task router — matches Plane tasks to agents by capability | internal/dispatcher/ | In progress (SPEC-032 draft) |
| Rover | Autonomous app-exploration agent — crawls a live mobile app into a product map in the validation graph | backend/rover/ | In progress (SPEC-038) |
| Hangar | App-portfolio domain — Organization → Project → App → Build (a Build is the unit of validation) | backend/hangar/ | Draft spec |
| Tower | LLM gateway — the single doorway to all product inference; wraps the LiteLLM engine | backend/ (not yet built) | Draft spec (SPEC-042) |
| Yard | Device management — leases a device from any source (local, AWS, …) and hands the consumer a connection to drive; control/data-plane split | backend/yard/ | Planned (SPEC-043 draft) |
Agents (workforce)
Aucert's AI workforce uses celestial codenames. Each is a role behind the generic agent executor.
| Agent | Role |
|---|---|
| Atlas | Spec agent (see Services) |
| Vega | Backend coder |
| Rigel | Frontend coder |
| Lyra | Docs |
| Altair | Ops / infra |
| Sirius | Reviewer |
Personas (pipeline)
Customer-facing names that front the 5-layer pipeline in the Console.
| Persona | Layer |
|---|---|
| Genie | L1 — Generation |
| Ember | L2 — Execution |
| Ada | L3 — Analysis |
| Dax | L4 — Decision |
| Remy | L5 — Reporting |
| Rio | Rover (exploration) |
Product and UI names
- Console — the customer-facing web dashboard (
frontend/apps/console/). - AucertMac — a thin macOS desktop shell over the Console (
clients/macos/). - Validation graph (the knowledge layer) — the
validationgraphdomain: the per-tenant Tenant Graph plus the Aucert-owned Ecosystem Graph. - AgentRail — the right-side workspace panel in the Console (Chat / Dispatch / Agents).
Domain modules (descriptive)
Data domains keep plain names — no codename. Each owns one slice of the model.
| Module | Owns |
|---|---|
organization | Organizations and membership |
identity | Auth, sessions, JWT / WorkOS |
user | User profile and account |
subscription | Plans and lifecycle |
metering | Usage tracking and credit consumption |
payment | Payment processing (Stripe) |
catalog | Product / plan catalog |
entitlement | Feature gates per tier |
onboarding | Customer onboarding flows |
validationgraph | The validation graph / knowledge layer |
platform | Monolith entry point — the 5-layer pipeline orchestrator |
shared | Cross-domain utilities (IDs, API contracts, events) |
Conventions
- Services and agents get evocative codenames (Astra, Atlas, Rover, Hangar, Tower, Yard; agents are celestial — Vega, Rigel, …).
- Personas front the pipeline for customers (Genie → Remy, plus Rio for Rover).
- Domains stay descriptive (
organization,payment, …).