Governed Intelligencethe body of work
The manifestos

Principles, written down

The two manifestos authored here, each with its values and principles on this page and its full text on GitHub, and the stack they belong to.

The Intelligence Governance Manifesto

Principles for governing the domain intelligence that AI systems depend on.

Reichhart and Gelas · version 1.5, May 2026 · CC BY-SA 4.0

Full text on GitHub →

Domain intelligence in a regulated institution is accidental, leaking, and missing. It exists where projects happened to be won, it walks out when people leave, and whole domains have none. Knowledge management worked on this for decades and did much of it well. What changed is the forcing function: once AI agents act on institutional knowledge, that knowledge has to be governed at the level of the claim, at machine speed, under supervisory scrutiny.

The manifesto defines governed intelligence as the operational discipline this requires. The unit is the claim, with provenance, an epistemic tier it has earned, temporal validity, scope, and governance status. The lifecycle runs continuously: ingest, consolidate, curate, expand, apply. Curation is the immune function, defending the substrate against pollution, staleness, fragmentation, amnesia, cascade failure, and structural distortion.

Six values

Governed claimsstored documents
Traceable provenancetrusted sources
Preserved contradictionsforced consensus
Continuous curationperiodic review
Organisational reasoning capabilityindividual expertise
Domain-specific intelligencegeneral knowledge

Twelve principles

The claim is the unit.
Provenance is non-negotiable.
Epistemic tier is earned, not assigned.
Contradictions are information.
Intelligence decays. Govern the decay.
Four authorities govern the graph.
Acquisition has modes. Match the mode to the source.
Expert knowledge is a point of view, not ground truth.
The graph must support structured inquiry, not just retrieval.
Every engagement feeds the domain graph.
Traceability is the response to acceleration.
No unfunded mandates.

Four integrity preconditions

Numbered 13 to 16 in the text for cross-reference. A substrate cannot be called operational without them.

Claims must be validatable, not only corroborated.
Claims are attack surfaces.
Architectural enforcement is assumed, not provided.
Containment is required for substrate-driven emergence.

The Agentic Enterprise Manifesto

Principles for governing AI agents at organizational scale.

Reichhart and Gelas · version 0.2, May 2026 · CC BY-SA 4.0

Full text on GitHub →

An enterprise that uses agents is not yet an agentic enterprise. The manifesto reserves the term for an organization where governed agents, operating on governed intelligence, exercise collective initiative: they perceive what matters, reason about institutional consequences, and raise opportunities for action before being asked. It depends on the Intelligence Governance Manifesto for the substrate and inherits the engineering principles beneath it, and it needs both in place.

Six values

Collective initiativeindividual agent performance
Governed substratemodel capability
Institutional reasoningtask execution
Compounding intelligencescaling compute
Governance relocationrule enforcement
Enterprise coherenceagent autonomy

Sixteen principles

The governed substrate
The domain graph is enterprise infrastructure, not an agent feature.
Intelligence is a system property, not a model property.
The substrate must support structured inquiry, not just retrieval.
The substrate deepens through use.
Enterprise agent governance
Agents share a substrate; they do not share a mind.
Initiative is earned through substrate depth; autonomy requires only capability.
Governance relocation is measured, not assumed.
Human accountability is scoped by consequence class.
Enterprise operations
Composite state is enterprise state.
Decay is managed, not prevented.
The enterprise responds by criticality, not by reflex.
Three lifecycles intersect; initiative emerges at the intersection.
Cross-cutting commitments
Governance is paid for.
Containment is multi-agent.
Right-size the agent portfolio.
Architectural enforcement is assumed.

The stack

Each manifesto governs one layer of the same whole, read from the top down. The two highlighted are the ones above; the engineering, delivery, and product layers are Arnaud Gelas's own work.

No layer is sufficient on its own. The enterprise layer assumes the four beneath it are in place.