What is the Operome?

The operome is the complete machine-executable normative rule set of an organisation. It is compiled from the documents that govern the organisation — its policies, contracts, regulations, procedures, charters, decisions — rather than inferred from observed behaviour. The act of compiling it is called operomisation. SynapseLayer built the compiler that produces it.

We coined both words in March 2026 to fill a gap in the language. Other words name other things. Knowledge graph names what an organisation knows. Process map names what it does. Context graph names the traces it leaves behind. None of these names what the organisation has decided should govern its operations.

That body of decisions, written down across thousands of documents and binding the people and systems that work inside the organisation, is the operome.

What the operome lets you do

An operomised organisation runs differently.

Work that was never automatable becomes automatable. Most operational work was never trapped by technology. It was trapped by the rules. Operomisation lifts those rules out of the documents and into a substrate that machines can run against.

The organisation becomes ruthlessly efficient. Every step that was slow because someone had to read a policy, check a contract, or interpret a procedure becomes immediate.

Discretion stays with humans. AI never gets it. Judgment, novelty, ambiguity stay with the people qualified to decide them. The operome refuses to let an AI agent exercise discretion on a question the organisation has already answered.

Errors are prevented, not detected. The action that would breach a rule never executes.

AI agents become reliable. An agent consults the operome, finds the rule that governs the action, and either acts within the rule or refuses. There is no probabilistic middle.

Operomes interact. The buyer's procurement operome speaks to the supplier's sales operome. Inter-organisational work that took weeks of human-mediated back-and-forth can be composed from rules both sides have already declared.

Audit becomes a side effect. Every rule carries a citation back to the document it was extracted from. Every action carries a trail back to the policy or contract that authorised it.

Normative, not empirical

The empirical description records what people are actually doing — process mining, observability, context graphs. They watch behaviour and infer the rules from what they see. The result is bloated and probabilistic, and tells you what is, not what should be.

The normative description starts from the other end: what the organisation has already written down about how it should operate. The operome is the normative one. Sharp, deterministic, and far smaller than any empirical model of the same operation.

What the operome is not

It is not a knowledge graph (those map what an organisation knows; they do not constrain action). It is not a process map (those show how work flows; they do not encode the conditions under which it is allowed to flow). It is not a workflow engine or a rules engine (those execute logic that humans wrote inside the engine; the operome is the rules themselves, compiled from the source). It is not retrieval over documents. It is not a model. It is not one universal ontology — the operome is yours, compiled from your documents.

How the operome is compiled

The inputs are the organisation's own governing documents. The compiler reads them and produces a structured ontology: entities, relationships, decision rules, validation logic. Every rule keeps a citation back to the document and clause it was extracted from. This compiler is what SynapseLayer built. It does not exist anywhere else.

Operomisation

Operomisation is what an organisation does when it stops paying consultants to interpret its own rules and starts compiling them directly from the source. It is not a one-off project. As source documents change, the relevant slice of the operome recompiles, and the systems running on top stay aligned with what the documents now say.

The terms "operome" and "operomisation" were introduced by SynapseLayer in March 2026. The compiler that produces the operome was built by SynapseLayer and is not available elsewhere.