Carol — back to Apps ← Apps

Carolopedia

A friendly guide to Carol, her ecosystem, and the agents who built her.

📖 CarolopediaServicesGovernance
Governance

Governance

Service The rules and oversight layer of Carolverse

📖About & Usage

About

Governance is the rulebook and watchtower of the Carol ecosystem. Think of it as the place where everyone agrees on how things should work — and the system that checks that they actually do. It holds the Carolverse’s Carol Constitution, its Carol Policies, its Carol Requirements, and its Carol Design blueprints. It also keeps a single source-of-truth catalog (Source of Truth) so every service knows what the official version of anything is. And it runs a constant monitor that makes sure every part of Carol stays accountable to those rules. This service is operated by Orion (Orion).

Note: Governance is currently being built — the foundation is laid, but many of its enforcement and oversight features are still under construction. Once complete, it will be the backbone of how Carol ensures consistency, compliance, and clarity across all its agents and apps.

---

Usage Patterns

Governance fires whenever a rule needs to be created, changed, or enforced. For example, say a new service like the Build Cookbook wants to add a policy about how tool versions are recorded. That request would flow into Governance — Orion would review it against the existing constitution and requirements, update the relevant policy document in Carol Policies, and log the change in the source-of-truth catalog. Later, the monitor would double-check that the Build Cookbook actually follows the new rule.

A more everyday scenario: an agent like Forge (Forge) wants to design a feature that touches data handling. Before coding, Forge checks Governance to see if there’s a relevant requirement or design guideline. If not, they submit a proposal — Governance reviews it and either approves it or sends it back with changes. This keeps everything aligned without anyone having to guess the “right way.”

🏛Architecture

The Governance service is built following the agent-centric modular architecture of Carolverse. It is the rules-and-oversight layer that every other service is accountable to — the constitution, the policies, the requirements and designs, the source-of-truth catalog, and the monitor — operated by Orion. It is work in progress: the pillars exist as concepts and as the stores other services already read, but Governance has not yet been assembled into its own self-contained service.

View the full architecture →

📚Recent initiatives

Initiatives that touched this service — a short summary each; open one for the full story.

CAROL-INI-2166-02: Hard gate: attribute all LLM calls to registered droids + trim bypass list
Enforce policy P.04.01.06.08: every LLM call must be attributed to a droid owned by a registered Carolverse agent. 1) Fix ~81 LLM call sites across 65 files to pass agent_id. 2) F\u2026
Orion · 2026-07-04 04:15
CAROL-INI-2168-02: Elrond wakes Albus on initiative review failure — align with cookbook #134/#86
Cookbook #134 says Elrond should invoke Albus during his domain (initiative review, phase boundaries). Cookbook #86 says Ir_s1 should route non-pass verdicts through Albus's phase\u2026
Orion · 2026-07-04 04:11
CAROL-INI-0251-02: Glover governance scaffold — constitution, agent roster, initial policies, designs database on glover-vm
Bootstrap Glover's own governance stack: a constitution describing Glover's mission and roles, an agent roster mirroring Carol's pattern (CEO, Engineering head, Architect, Designe\u2026
Orion · 2026-07-04 03:50
Browse all initiatives →

🛰️Updates

Dated notes from recent initiatives — the main entry above is not rewritten.

Change2026-07-02

Governance rules have been reverted: the block-breaker threshold is back to 1 and max concurrent executing is back to 1, and the dispatch engine is off, affecting how initiatives are handled.

New Capability2026-06-29

New policy established: Carol app directories must contain only symlinks or empty stubs for data files, never real SQLite files. Enforced through Albus.

Fix2026-06-29

Initiative dispatch process now re-validates the original problem premise before execution, eliminating wasted runs when issues resolve before dispatch.

Correction2026-06-29

Initiative status routing now consistently enforces status_router guards across all code paths, ensuring compliance with governance controls.

Fix2026-06-27

Monitor cards (Recent Executions, Current Execution) and close-hooks now route initiatives DB reads through Elrond's relay instead of direct sqlite to the stale on-disk fallback file, eliminating crashes from periodic clobbering and schema drift.

👤Owner

Orion · Deputy Admin

🧩Apps

Apps owned by this service's team.

Admin MonitorCarol AppsCarol ConstitutionCarol PoliciesCarol RequirementsCarol's OrgCarolopediaOrion's LogbookSession InductionSource of Truth