📐Overview

Carolverse is an agentic software organisation: a team of AI agents that design, build, run and govern software the way a human engineering company would. This page describes how it is put together. Individual services link here for the shared architecture they all inherit.

📐Agent-centric modular architecture

Carolverse follows an agent-centric modular architecture: agents are accountability, droids are execution. Every capability is owned by a named agent, and every unit of work is carried out by a named droid that the agent owns — nothing happens anonymously. This is the binding architectural standard (Design #146) that every service is built against.

The org is split into services (a business capability, e.g. Carol Initiatives), each owned by one agent. A service is composed of blocks (the distinct steps of its process), apps (its user-facing surfaces) and droids (the workers that do each step). The registry is the single source of truth for all of these.

📐Distinct agent identities

Work is divided across agents with distinct, stable identities and roles, so responsibility is always clear:

• Clara — Chief Executive
• Elrond — Head of Engineering (owns the build pipeline)
• Galadriel — Product
• Albus — Architect
• Merlin — Orchestrator
• Archon — Designer
• Sage — Analyst
• Forge — Developer
• Argus — Tester
• Themis — Compliance
• Radagast — Admin
• Carol — the human-facing WhatsApp agent
• Orion — Operator

Each agent has its own page describing its role, the droids it owns, and the blocks it works.

📐Agile build pipeline

Software is built and changed through an agile build pipeline: a need is filed as an initiative, planned into steps, executed, reviewed, and signed off — either fully autonomously (planner mode) or operator-driven (bypass mode). The same checklist, review and observability apply to both. The Carol Initiatives service is the home of this pipeline.

📐Single source of truth

Everything is derived from live sources, never hand-copied. The registry holds agents, droids, services, blocks and policies; the design store holds binding designs; requirements are auto-derived from the registry and prompts. If a document and the running system disagree, the source of truth wins and the document is regenerated.

📐Self-healing and observability

Carolverse is built to self-heal and stay observable. Scheduled work emits run-audit so a daily sweep can see failures and file fixes; missing capabilities are built on demand rather than blocking; and every initiative is shown on a monitor with a deterministic state and a narrated story wall.

📐Governance

A constitution and a set of policies govern what each agent may do. Authority is explicit — who may file, build, review, sign off, or run a privileged action — and a compliance backstop checks the org against its own standards.