The Governance Operating System

Every enterprise now runs software that decides. Models summarize, agents act, and both do so against an architecture that nobody has written down in a form a machine can consult. Governance lives in documents; execution lives in systems; the gap between them is where the next decade of enterprise risk will be paid for.

Enterprise AI has a vocabulary for models and a vocabulary for risk. It has no vocabulary for the thing between them. That thing is the knowledge of what an organization is, how it is built, what it has decided, and what it would take to prove any of that to a machine at the moment the machine acts. We call the absence the control gap, and the three scenes this document opened with are the gap seen from three chairs. The agent cannot consult what was never written for it. The board cannot be answered from a record that does not exist. The acquirer cannot price what the seller cannot show.

The gap is not a lack of policy. Most large organizations have more governance documents than anyone can read. It is a lack of a governed, consultable record of the architecture those documents are meant to govern. A policy says what should be true. An architecture diagram says what was true when it was drawn. A control framework says what must be evidenced. None of them can answer, at runtime, a question an agent is about to act on.

#Three vocabularies, no translator. The board asks about posture: are we exposed, are we ready, can we prove it. The architect answers in systems, interfaces and dependencies. The engineer, and now the agent, works in calls, permissions and data. Each vocabulary is correct in its own frame. None of them translates into the others without a person doing the translation by hand, and that person's translation is the governance. When the person is in the room, the organization has governance. When the person is not, it has documents.

#Governance by document. The prevailing practice is a periodic survey. Assessors ask, owners answer, a scorecard is produced, and the organization is scored on what its people believe about it. The practice has three costs. It is stale on the day it ships, because the architecture moved while the survey ran. It cannot be consulted by a system, because a slide is not an interface. And it is unfalsifiable, because nobody can trace a score back to the evidence that produced it; the score is a consensus, not a computation.

The costs are paid in familiar currency. A transformation program stalls because nobody can say which dependencies the new platform will break. An audit finding arrives as a surprise because the control that was attested to on paper was never wired in practice. The same assessment is commissioned three times in a year, once for the regulator, once for the board and once for an acquirer, and the three answers disagree. Each of these is the control gap, paid for in time and credibility.

Those costs were tolerable when the only consumers of governance were people, who read slowly and act rarely. They are not tolerable when the consumers are agents, which read nothing they are not given and act continuously. An agent cannot open a policy binder before it provisions a resource or drafts a commitment. Either the governance is available as something the agent can call, or the agent acts on an assumption.

#Why the gap is acute now. Regulators have begun to ask for evidence of control over AI systems rather than statements of intent. Auditors ask how a decision was made and what it was checked against. Acquirers ask what they are buying when the thing being bought runs on models the seller does not own. Each of these questions has the same shape: show me the governed state of the enterprise and the evidence behind it. Almost no enterprise can answer in that shape today, and the ones that can answer do so by hand, once, for one audience.

The remainder of Part I argues that this gap will not be closed by better models, that it belongs to a layer of its own, and that the layer has a name.

Models commoditize. Each generation is cheaper, more capable and more interchangeable than the last, and the enterprise that bet its advantage on a particular model has already watched that advantage depreciate. What does not depreciate is the organization's knowledge of itself: its architecture, its decisions, the evidence behind them, and the capacity to put that knowledge in front of a system at the moment it matters. That knowledge compounds. Every decision recorded, every dependency mapped and every control evidenced makes the next question cheaper to answer and the next agent safer to deploy.

This is the argument for treating governance as a layer rather than a function. A function is staffed; a layer is built. A function produces documents; a layer produces answers. A function is consulted when someone remembers to; a layer is consulted by every system above it, every time, because the systems are built on it.

#Why the adjacent categories cannot own it. Four categories sit near the control gap, and each has a reason it cannot close it.

Governance, risk and compliance platforms hold obligations, controls and attestations. They are the system of record for what must be true and whether someone has signed to say it is. They do not hold the architecture, and they do not compute from it. Their posture is declared, not derived.

Model and machine-learning operations platforms govern the lifecycle of a model: its data, its training, its evaluation, its deployment. They stop at the model's boundary. The enterprise the model acts within, with its systems, its decisions and its obligations, is outside their frame.

Agent frameworks orchestrate actions: they route tasks, call tools and manage memory. They are built on the assumption that the governance question has been answered somewhere else, and they offer a place to plug that answer in. They do not produce it.

Model providers govern the behavior of their own models, which is necessary and is theirs to do. They do not know your organization, cannot see your architecture, and should not be the authority on your intent.

Each of these categories is necessary. None of them holds the layer where intent, structure and evidence meet, and none of them is positioned to: a provider cannot be the governor of its own customers, an orchestrator cannot be the judge of its own actions, and a system of record cannot compute what it was only built to record.

#What the durable layer has to be. If governance is the layer that outlasts any model and any vendor, four requirements follow. It has to be computed from evidence rather than surveyed from opinion, or it is stale on arrival. It has to be linked to that evidence end to end, or it cannot be audited. It has to be consultable by agents as readily as by people, or the systems that most need it will be the ones that cannot reach it. And it has to be certifiable in a form a stranger can verify, or every claim it makes is a claim the buyer has to take on faith.

The category that meets those four requirements did not exist as a category until recently. The next chapter defines it.

An operating system is the layer that other software takes for granted. It holds the state, enforces the boundaries, exposes the interfaces, and lets everything above it act without re-deriving the rules. Enterprise AI needs that layer for governance, and the name follows.

The definition has four properties, and a system is in the category only if it has all four.

#Governance is a first-class artifact. It is not a document about the architecture; it is a governed model of the architecture, with the decisions and obligations attached, held in a form that can be queried. When the architecture changes, the artifact changes, and the posture computed from it changes with it.

#It is auditable end to end. Every reading the system produces traces back to the evidence that produced it. A rung on the Governance Ladder is not an opinion that happens to carry a number. It is the output of a computation over evidence that a reader can open, and the computation is the same for every organization that is read.

#Its outputs are deliverable instruments. The system produces things a person can hand to someone else: an assessment report, a certificate that can be checked publicly, a roadmap that an architecture team can execute. A governance layer that only produces dashboards for its own operators has not left the building.

#Its trust compounds. Because the artifact is governed and the readings are computed, the second reading is cheaper than the first and more valuable, and the tenth is cheaper and more valuable than the second. The organization accumulates a verified history of its own governance posture, and the credential it earns is designed to be renewed on evidence rather than to expire into a new survey.

#The metaphor, taken seriously. The operating-system metaphor is not decoration; each part of an operating system has a counterpart in the category.

The kernel is the governed knowledge: the organization's architecture, decisions and obligations, held as a graph that the rest of the system reads. The engine is the physics: the computation that turns evidence in the kernel into a readiness posture, the same way for everyone, with public constants. The interfaces are the doors: one for agents, which consult the system as a tool before they act, and one for people, which present the posture as a reading and a report. The evidence record is the system's memory: the inputs, the readings and the decisions it has been asked to evaluate, kept so that an answer can be traced. And the certification is the system's output to the world: a credential that states which rung the organization has reached, issued from the same engine that computed the reading, and verifiable by anyone who holds the certificate's identifier.

None of those parts is new on its own. Graphs of enterprise architecture exist; scoring engines exist; agent tool interfaces exist; audit trails exist; certifications exist. What is new is the category that requires all of them to be one system, so that an agent asking a governance question gets the same answer the auditor would, computed from the same evidence, carrying the same credential.

OntoRamp is built to this definition, and Parts II and III say how far each property is live today. Five things distinguish the way it is built, and each is a public face of the system rather than a claim about its internals.

#What makes it different. First, governance gates in layers on every reading and every change. A proposed decision is evaluated before it is acted on; every answer that leaves the platform is held to a classification ceiling; and changes to the platform itself pass the discipline of chapter nine. Second, decisions as governed objects. A consequential decision is logged, evaluated and kept as a decision record an audit can open, and the Decision Integrity Scan reads how well that discipline holds across a leadership team. In the adjacent categories a decision is a line in a ticket; here it is an object the system governs. Third, valuation as a governed quantity. The published volumes on valuation cited in chapter eight connect governance to what an enterprise is worth, and the platform is designed to compute that connection from evidence rather than assert it. The translation of a change in posture into a change in what the enterprise is worth is a research line of chapter eight, stated there at the altitude of benefit. Fourth, a safety-pattern discipline. Our own controls are designed against a versioned set of named safety patterns, each tied to the harm it exists to prevent, and chapter ten says what a customer can rely on today and what is still direction. Fifth, continuity. When a system has changed, whether it is still the system that was approved is the question the published continuity framework cited in chapter eight answers in principle, and renewing a credential on evidence rather than by a new survey is the direction that framework points to; chapter eleven marks it as direction.

The rest of this document is the account of how, at the altitude a reader can act on, and with the evidence a reader can open.

A survey asks people what they believe about their organization. A computation reads what the evidence shows. OntoRamp Governance Physics is the second kind of instrument, and the phrase that defines it is short: evidence in, scores out.

The evidence is the governed knowledge of the organization: its architecture as modelled, its decisions as recorded, its controls as evidenced, and the relationships among them. The engine reads that evidence across the seven governance domains, Platform, Data, Application, AI, Security, Governance and Capability, and produces a posture: a position on the Governance Ladder, with the dimensions that put the organization there and the gaps that would move it.

The methodology is named physics for a reason. A physical law does not care who is asking. It applies the same way to every system it describes, its constants are public, and two observers reading the same evidence reach the same result. That is the standard the engine is held to: the same constants for every organization, the same computation for every reading, and a result that does not depend on who is asking.

#The Governance Ladder. The Ladder has five rungs, and every rung carries one number and two names: the rung name, which says what state the evidence has found, and the credential name, which says what that state entitles the organization to claim.

L1 Fragmented is the state in which governance exists in isolated pieces with no paths between domains; it is where most enterprises begin, a starting position rather than a failure, and its credential is Governance Baseline. L2 Stabilized is the state in which the core governance surfaces are active, the framework has begun to enforce its own rules and execution paths have emerged; its credential is Governance Readiness. L3 Coherent is the state in which integration paths connect the domains and the organization can reason across its boundaries rather than only within them; its credential is Governance Maturity. L4 Resonant is the state in which assurance is high across every dimension and the organization has begun to detect its own deviations before they compound; its credential is Agentic Readiness, because an organization that notices its own drift can be trusted to let agents act on its governance. L5 Harmonic is the state in which every dimension is at full assurance and governance adapts to context, so that the organization not only changes but knows why; its credential is Governance Autonomy.

A rung is not a score. It is a state the evidence puts you in, with a credential name that says what the state entitles you to claim. L3 Coherent is the state; Governance Maturity is the credential. This document never reports the arithmetic beneath a rung, and neither does the platform's public surface, because the arithmetic is not the claim; the state is.

#The six readiness dimensions. The posture that places an organization on a rung is read across six dimensions.

Coverage asks how much of the enterprise architecture, across the seven domains, the governed knowledge actually specifies. Governance asks whether the controls and decisions that govern the architecture exist, are recorded and are owned. Integration asks whether the domains depend on each other through governed paths rather than informal ones. Execution asks whether the organization has operational flexibility: more than one path to the same outcome, rather than a single fragile one. Assurance asks whether governance is conformed to and decisions hold their integrity, provably. Reflexivity asks whether the organization can assess its own learning and adapt, with evidence from comparable readings over time.

The dimensions are read across the seven domains, and the assessment reports standing by domain as well as overall, so a difference between an organization's data governance and its AI governance is stated rather than averaged away.

#The engine's constants are public. The engine simulates 800 agents under 10 semantic forces and applies 70 governance laws. Those constants are the same for every organization it reads, and they are published on the OntoRamp site.

#Calibration. The engine is calibrated against an exemplar: a synthetic reference architecture of 353 elements, 317 relationships and 4 viewpoints, modelled in the open ArchiMate exchange format. Computed against our exemplar calibration corpus — a synthetic reference architecture, not customer data. The exemplar is what lets a prospective customer see a full reading before any of their own evidence is loaded, and it is what lets us show the engine's behaviour without showing anyone's architecture.

Governance Physics is the engine of the operating system. The next chapter turns to the interface that matters most now: the one the agents use.

The positioning line of the platform is this: Governance integrity for agentic AI. The word that matters in it is integrity. Integrity, in the engineering sense, is the property that the parts of a system agree with each other: that the governed knowledge, the computed posture, the evidence behind it and the action an agent takes on it are consistent, and that any disagreement is detectable. Governance integrity for agentic AI is that property applied to an enterprise in which software acts.

#What agentic readiness means. An organization is ready for agents when an agent can consult the organization's governance before it acts, and get an answer it can act on. Not a document, which it cannot read, and not an assumption, which it cannot check, but a reading: the governed state of the relevant part of the enterprise, the posture that state implies, and the evidence behind it. L4 Resonant is the rung at which the organization can be trusted with that, and Agentic Readiness is the credential that says so. Readiness is not a property of the agent. It is a property of the organization: whether it has made itself consultable.

#Agents consult governance before acting. On the OntoRamp platform, an agent reaches governance the same way it reaches any other tool: through a front door it can discover and call. Through that door it can search the governed knowledge base, ask where the organization's knowledge is thin, log a decision it is about to make, have that decision evaluated before it acts, and request a full assessment. The free decision-intelligence plugin exposes the decision tools to any agent at no charge, so that the habit of consulting governance costs nothing to form. Free-tier queries return results from the client-safe tier of the knowledge base.

The sequence matters. The agent consults, then acts, and the consultation is recorded. That ordering is what turns an audit trail from a reconstruction into a record: the question the agent asked and the answer it was given exist before the action does.

#One engine, three doors. The same engine serves three kinds of reader, through three doors built for them.

The developer door is the agent's: discover the front door, connect with a key, start on the free tier, and move to the plugins as the questions get harder. The developer gets governance as an interface, which is the only form in which an agent can use it.

The compliance door is the assessor's: load evidence, receive a reading across the seven domains, receive the report and the roadmap, and earn the credential. The compliance lead gets governance as an instrument, which is the only form an auditor will accept.

The executive door is the board's: ask the one question that matters, what is our governance posture and can we prove it, and receive an answer with a rung, a credential and a roadmap, in the vocabulary of risk and readiness. The executive gets governance as a position, which is the only form a board can act on.

Three doors, one engine, one answer. The agent, the auditor and the board are reading the same evidence through the same computation, which is why their answers agree.

That is the thesis. Part II is the system: what is live today, offering by offering, what evidence a reader can open for each, and the research it rests on.

Part I defined the category. This part describes the system OntoRamp runs against that definition, at the altitude a buyer or an architect can act on: what exists, what it does, what evidence a reader can open, and where the boundary of what we describe sits. Every figure is a public constant. Where a capability is specified but not yet live, the text says so.

#The governed knowledge base. Beneath every reading is a governed corpus of enterprise-architecture and governance knowledge: 30,000+ governance knowledge artifacts and 7,500+ extracted entities, distilled from 4,500+ source documents across seven governance domains. The entities are governance concepts, patterns, systems and roles, linked to each other and to the sources they came from, so that an answer can carry its provenance. Free-tier queries return results from the client-safe tier of the knowledge base. The corpus is the kernel of the operating system: the thing every door reads and every reading is computed from.

Two things about the corpus matter more than its size. It is classified, so that every artifact carries a tier that says who may see it, and that classification governs what leaves the platform through any door. And it is governed, so that additions are reviewed, duplicates are being resolved, and the knowledge carries the provenance an auditor can follow.

#The agent front door. An agent reaches the platform through one discoverable gateway, the front door at mcp.ontoramp.com, built on the Model Context Protocol so that any agent runtime that speaks the protocol can connect without custom integration. The front door exposes 14 tools across 4 plugins, including the free decision-intelligence plugin. The purchasable catalog is 10 tools across 3 plugins: the Knowledge Graph, Governance Evaluator and Projection Engine plugins described in the next chapter.

Through the door an agent can search the governed knowledge base, look up an entity and its relationships, read an organization's position on the Governance Ladder and the gap to the next rung, log and evaluate a decision, request an assessment and, on the plugin tiers, run a forward projection. Each tool answers in a shape an agent can act on, with the classification ceiling applied before the answer leaves.

The capabilities an agent most often needs on their own are also listed as standalone servers on the public Model Context Protocol registry, under the identities graph-query, decision-intelligence, knowledge-cartographer and governance-assessment, so that an agent that finds OntoRamp through a registry search can connect to the capability it needs. A key issued for the free tier works on every one of them.

#Agent-native by design. The platform treats agents as first-class readers, which means it has to be discoverable by them as well as callable. The site publishes machine-readable discovery descriptors, so an agent or an answer engine that asks what OntoRamp is and how to connect receives an answer in the form it can parse, kept in step with the same public-claims source as the human-readable pages. The live agent demo shows that path end to end: an agent discovers the front door, connects, consults governance and acts.

#Verification. Every credential the platform issues is engine-validated, publicly verifiable. A certificate carries an identifier, and anyone who holds the identifier can open the verification page and see the credential, its rung and its status, issued from the same engine that computed the reading. There is no second system a reader has to trust: the verification reads the same record the certificate was issued from.

#Security posture, stated as posture. This document describes what is enforced and where it is checked, and avoids the vocabulary of absolutes.

Customer evidence is scoped to the customer. Anonymous access to scoped data is denied, and that denial is tested by the platform itself rather than assumed from its configuration. Every external door, whether a plugin, a registry server or the front door, applies a classification ceiling: the free tier is served from what the free-tier scope note on the quickstart page under the docs pages calls the "client-safe tier of the knowledge base", and classification governs what leaves the platform regardless of which door it leaves through. Those are the two posture statements we make, and both are checked by the platform itself rather than attested on paper.

The next chapter takes each offering in turn.

The platform is sold as offerings in three groups. The self-serve group is the developer door: the plugins, a bundle of them, and a free plugin that any agent can use. The assessment group is the compliance and executive door: an enterprise assessment, a quick scan that leads into it, and a standalone certification. The third group is a single deliverable, the Architecture Pack. Every offering reads the same governed knowledge and the same engine, which is what lets them compose. No price appears in this document, because prices move and the pricing page is their single source.

Each offering is described the same way: who it is for, what you get, how it composes with the rest, and the evidence a reader can open.

Knowledge Graph #

#Who it is for. Developers and architects who want an agent, or themselves, to ask architecture and governance questions in plain language and get answers grounded in a governed body of knowledge, with the provenance attached.

#What you get. Search over the governed knowledge base; lookup of an entity and the things it depends on and relates to; the governance constraints that bear on a decision; and the evidence behind a particular claim. It works from the first call on the shared corpus across the seven governance domains, and it reads an organization's own knowledge, kept private to that organization, once another offering has loaded it. It only reads; it changes nothing it draws on. A free developer tier carries a generous monthly allowance. Free-tier queries return results from the client-safe tier of the knowledge base.

#How it composes. The Knowledge Graph is the kernel the other plugins read. The Governance Evaluator's reading and the Projection Engine's projection are computed over the same graph an agent searches, so an answer from any of the three can be traced to the same knowledge. The registry identity graph-query exposes the same capability as a standalone server, and knowledge-cartographer tells an agent where that knowledge is thin before it relies on it.

Governance Evaluator #

#Who it is for. A platform or architecture lead who needs a maturity reading they can defend, and an agent that needs to know an organization's posture before it acts on it.

#What you get. A rung on the Governance Ladder with the dimensions that put the organization there, the gap to the next rung and what would close it, and a brief that can be handed upward. The reading is computed, not surveyed: it is the engine of Part I applied to the governed knowledge.

#How it composes. Its reading is the one the certifications are issued from, so a self-serve evaluation and a certified assessment read the same Ladder; the assessment adds evidence, scope and a human review, not a different engine. An organization that evaluates itself first arrives at an assessment knowing what it will find.

Projection Engine #

#Who it is for. Transformation leads and architects choosing between paths, and agents planning a change with more than one step, who want to know where a change would leave the governance posture before anyone commits to it.

#What you get. A forward projection: the rung a proposed change would reach, the dimensions that would move, and the gaps that would open or close along the way. The projection is computed over governed knowledge, not over a template, and it is stated at the altitude a decision needs: direction and consequence, not internals.

#How it composes. The projection reads the same graph and the same engine as the evaluation, so a projected rung means the same thing as an evaluated one. The Transformation Roadmap delivered with an enterprise assessment describes the same kind of path a self-serve projection describes: what moves the posture. Projection is available on the plugin tiers; it is not part of the free tier.

Governance Intelligence Bundle #

#Who it is for. Teams that want the whole loop in one subscription: know the architecture, evaluate the posture, project the change.

#What you get. The Knowledge Graph, the Governance Evaluator and the Projection Engine together, under one key at the one front door. The bundle is where the phrase governance intelligence belongs: it names the capability the operating system delivers, the ability to know, evaluate and project from one governed source, and it is the capability the three plugins deliver as a set.

#How it composes. The bundle is the three plugins, nothing more and nothing less, so everything said of each above holds for the set. An organization that later commissions an assessment keeps the bundle; the assessment reads the same knowledge the bundle has been reading.

The free decision-intelligence plugin #

#Who it is for. Any team running agents that wants the habit of consulting governance before acting, at no cost; and any developer who wants to see the platform answer before buying anything.

#What you get. A governed, auditable record to which an agent logs a consequential decision; an evaluation of a proposed decision before it is acted on, returning the earlier decisions that bear on it and a pass, warn or block verdict with reasons and suggested fixes; and a request for a full assessment when the record says one is due. Each organization's record is kept apart from every other's.

#How it composes. The decision record is the trail the audit asks for, and an organization that has been logging and evaluating its decisions arrives at an assessment with evidence instead of recollection. The plugin is the same decision-intelligence identity listed on the public registry.

Enterprise Governance Assessment #

#Who it is for. An executive, compliance or transformation lead who needs a defensible, board-ready reading of the whole enterprise, and the documents to act on it.

#What you get. A reading across all seven governance domains and three deliverables. The Governance Assessment Report states what was found in each domain and how it connects, where evidence is missing, where the organization stands overall and by domain, and how that standing would move if the leading gaps were closed; it opens with an executive summary and closes with a prioritized gap inventory, an action plan and a statement of what the analysis does and does not cover. The Readiness Certificate states the rung reached, with its credential name, in a form anyone can verify. The Transformation Roadmap sets out the path to the next rung. Timeline: Diagnostic by request; Full Assessment in 2–4 weeks.

#How it composes. The assessment is the Governance Evaluator's engine applied with full evidence, full scope and human review, so its rung is read on the same Ladder as the self-serve evaluation. The Decision Integrity Scan leads into it; the Agentic Readiness Certification can be taken from it or on its own.

Decision Integrity Scan #

#Who it is for. A leadership team that wants a quick, directional read on how well its consequential decisions are governed before committing to a full assessment.

#What you get. From a structured interview, a concise, board-readable report: a governance tier in the scan's own terms, the leading remediation themes, such as who holds the authority to decide, whether past decisions can be reconstructed, how exceptions escalate and how AI agents are overseen, a recommended window for the next assessment, and a business case an internal champion can carry to procurement. It is a directional read, not a formal assessment and not a credential, and its tier is not a rung on the Governance Ladder.

#How it composes. The scan is the entry point: a directional reading that becomes the case for the full assessment.

Agentic Readiness Certification #

#Who it is for. An organization that needs to show a board, a buyer or a regulator that it is ready to let agents act on its governance, and wants the standalone L4 credential without a full enterprise assessment.

#What you get. The L4 Resonant reading across the governance domains the standalone credential evaluates (the full assessment evaluates all seven), the Readiness Certificate at Agentic Readiness, and a certification badge. Every certificate is engine-validated, publicly verifiable: it carries an identifier, its verification page shows its status and offers a route to challenge it, and the badge leads back to that page, so a lapsed or replaced certificate is visible as such. Delivery is 5–7 business days. Issuance of the highest credentials is designed to follow a recorded human approval: the engine proposes, a person signs.

#How it composes. It is the same engine and the same Ladder as the enterprise assessment, read over the domains the standalone credential covers; an organization that later takes the full assessment is read across all seven.

Architecture Pack #

#Who it is for. Architecture leads who need a board-ready, standards-based model of their governance architecture, and teams at the start of a transformation who want to see the architecture they have before they plan the architecture they want.

#What you get. A one-time set of architecture deliverables built from the material the organization hands over and checked by a person before delivery: an ArchiMate viewpoint document, a posture report, a roadmap, an implementation brief, a private web viewer of the model, and a machine-readable export of the full model in the open ArchiMate exchange format. Secrets and personal data are screened out of submitted material on intake, as a best effort; what is submitted remains the customer's responsibility. The exemplar shows the shape of the model: 353 elements, 317 relationships and 4 viewpoints. Computed against our exemplar calibration corpus — a synthetic reference architecture, not customer data.

#How it composes. The pack produces the standards-based model of an organization's own architecture: the form in which that architecture is ready to be read as governed knowledge rather than as a shelf of documents.

#How the pack is made. The customer hands over its own architecture and governance material: the documents, diagrams and records it already holds. Before anything is built from it, that material is screened on intake: secrets and personal data are screened out, and a person checks that what remains is enough, in scope and quality, to build from. The screen is a best effort, not a certainty, so what a customer submits remains its own responsibility. The model is then built to the relationship rules of the ArchiMate specification and to our own standard for a complete, connected and traceable model. The exemplar that calibrates the engine is held to that standard, and its regeneration is reproducible. Where the exemplar falls short of a rule today, the shortfall is repaired in the model, never by relaxing the standard, and no conformance is claimed until the checks pass. The deliverable is rendered into the viewpoints an architecture team expects, current state, target state, network topology and migration among them. A person signs off before anything is delivered, for a customer's pack and for each public release of the exemplar. The model leaves the platform as an export in the open ArchiMate exchange format.

None of this came ready-made. The open standard says what a valid relationship is. It does not say how to turn a shelf of documents into a model that is complete, connected and traceable. We built that part ourselves, over successive releases of the exemplar: the standard for a complete model, the discipline that holds a model to it, and the sign-off that puts a person between the process and the customer. The open tools and formats we draw on are used as published; the process that joins them is our own, and it is the part a customer cannot get by downloading the standard.

Anything that needs time with our team, a diagnostic session above all, is by request rather than self-serve; the closing chapter says how to ask.

The methodology has a name because it has a literature. Governance Physics is not a brand applied to a scoring spreadsheet; it is the operational form of a body of published work on what governance is, what it conserves, where its limits lie and what it is worth. This chapter names that work by its public titles and identifiers, says what each contributes to the category, and then describes the research lines still in progress by what they will let a customer do, with direction marked as direction.

#The published work.

#The Physics of Governance: Thermodynamic Limits of Autonomous Agents (10.5281/zenodo.22151454) is the volume behind the methodology's name. Its argument is that the governance of autonomous agents has limits that can be reasoned about the way a physical system's limits are reasoned about. There are quantities that are conserved, costs that cannot be avoided, and states a system cannot reach without paying for them. That is why the engine is computed rather than surveyed, and why its constants are public: a law that depends on who is asking is not a law.

#Ethical AI Series — Conservation of Intent, Volume I (Doctrine) (10.5281/zenodo.18930091), Volume II (Ontology) (10.5281/zenodo.18930283) and Volume III (Limits + Closure) (10.5281/zenodo.18930366) set out the doctrine the platform is built on: that an organization's intent is a thing to be conserved through every transformation of the systems that carry it, the vocabulary needed to say what intent is and where it lives, and the limits of what any system can conserve. Ethical AI Series — Conservation of Intent, Volume IV (Companion): Alignment & Safety Ontology + Intent Preservation (Non-Operational) (10.5281/zenodo.19304640) extends the series to alignment and safety and to the preservation of intent as a property that can be stated without describing any mechanism, which is the discipline this document follows. Intent preservation is among the earliest foundations of this work, and the one the goals of chapter eleven rest on most directly. A conservation law names what may change by naming what may not. An organization that can state the intent it approved, keep it and check it through every change to the systems that carry it is free to change everything else. Posture queried at any moment, a board question answered from evidence, a credential renewed rather than re-surveyed: each follows from that one fixed thing. What is conserved can be checked; what is only remembered must be asked again.

#The Geometry of Governance: Volume III — Topology, Swarms, and the Physics of the GPU-G (10.5281/zenodo.18665381) treats governance as a matter of structure: the shape of a system determines what can be governed in it, and systems of many agents have a geometry of their own. It is the structural view behind the category's concern with integration across domains and with systems of many agents.

#Intent-Aware Continuity in Evolving AI Systems: A Typed, Provenance-Aware Framework for Continuity Judgments in AI Governance (10.5281/zenodo.21539741) answers a question every certification has to answer: when a system has changed, is it still the system that was approved? Its framework for continuity judgments, typed and carrying provenance, is the published basis for renewing a credential on evidence rather than re-surveying from scratch, a direction chapter eleven records.

Three volumes on valuation, Ontology of Valuation (10.5281/zenodo.18663952), Structure of Valuation (10.5281/zenodo.18664069) and Harmonic Law of Valuation (10.5281/zenodo.18664118), connect governance to what an enterprise is worth: what valuation is made of, how it is structured, and the regularities that hold across it. They are cited for what they contribute to the category: a published account of how governance bears on what an enterprise is worth.

The published work is the visible part of a larger body. Behind it stand further volume series and theory that we have not released: on valuation and how governance enters what an enterprise is worth, on the discipline of decisions and the records they leave, on the identity a system keeps or loses as it changes, and on the theory that joins the three. Nothing of their contents is described here, and nothing is cited that cannot be checked. They are named as a class because they are already at work. The offerings of Part II, the research lines below and the bands of the roadmap draw on them, whether a surface is live, in progress or planned, and the depth a customer meets in the product is the depth of that work.

#The research lines, by what they let a customer do. The research lines in progress are described below, each by its benefit; none is described by its method. Where a line is live it says so, and where it is not, a Direction callout says so.

#Projection. A customer can ask what a proposed change would do to the governance posture before making it, and receive the rung it would reach, the dimensions that would move and the gaps it would open or close. The process behind the answer is a computation over the organization's governed knowledge under the engine's public constants; the internals of that computation are not part of the public description and are not needed to act on its result. This line is live as the Projection Engine.

#Governed multi-agent execution. A customer will be able to put a bounded group of agents to work on a pre-defined governance scenario without giving up control. Before anything starts, the customer knows what the run will cost and sets its limit. Each run returns a decision packet and a governance attestation, with its cost accounted for in a record a reviewer can trust. A person, not the agents, makes the decision, and a run that meets a safeguard stops for human review rather than deciding on its own.

#Intent preservation. A customer will be able to check a system that has changed against the intent that was approved for it, and see where the change has drifted from that intent before the drift compounds into a violation. The doctrine is ours, published in the four Conservation of Intent volumes and among the earliest foundations of this work; the capability that applies it to a customer's systems is in progress.

#Executable-opportunity derivation. A customer will be able to ask the operating system what it could do next with it and has not yet done. The answer is a prioritized list of concrete next actions, each ready for an agent to run or a person to fill in, and each showing the knowledge it rests on. It is advisory: a reading of what could be done next, not proof of what has or has not been done.

#The governance agent. A customer will be able to keep its governance picture continuously current from the systems it already runs. A governance agent maintains the graph, checks each change as it happens, and warns early of a violation or of risk to a certified rung. At the higher rungs it holds automated processes and other agents to governance boundaries before they act. The agent acts within limits the customer approves, and what it did and did not do is reviewable. The customer approves what is observed; enforcement begins as advice; people keep the final say.

#Knowledge-graph quality, entity resolution and retrieval. A customer will be able to ask the Knowledge Graph a question and get a complete, evidence-backed answer rather than one with silent gaps because the same concept was held in several fragments. That means duplicate entities resolved into one, each concept held once with all of its evidence together, and provenance kept through every repair and through every refresh of a source document. The benefit is trust that an answer today and an answer tomorrow refer to the same thing. It is also trust that each answer can be traced to its evidence across all seven governance domains, and that nothing becomes more visible by being cleaned up.

#Governance in the deal. An acquirer or a portfolio reviewer asks three questions of a target that today are answered by hand, late and once. The first is the target's governance posture, computed from its evidence rather than surveyed from its data room. The second is the combined entity's posture before close. The third is what a change in posture does to what the enterprise is worth, so that governance enters the price as an input rather than as a judgment applied at the end. The benefit is a diligence answer that the deal team, the board and the regulator can read from the same evidence.

What these lines share is the shape of Part I's definition: each extends the operating system without changing what it is. The kernel stays governed knowledge; the engine stays public physics; the doors stay open to agents and people alike; the evidence record stays the memory; and the credential stays the output. The next chapter is about the discipline that keeps it so.

A company that sells governance has to be able to show its own. This chapter describes the discipline OntoRamp applies to itself, at the altitude of what it is and what it produces rather than how it is run day to day. The short form is that the discipline is the product, applied to ourselves.

#Specification before build. The platform is built specification first: a change is specified, and a person with the authority to approve the specification does so, before the change is built. A specification states what the change is for, what it must do, what it must not do, and the criteria by which it will be accepted. The criteria are written before the work starts, so that acceptance is a comparison against a record rather than an opinion formed afterwards. The same discipline produced this document: its scope, its vocabulary and its boundaries were decided before a sentence of it was drafted.

#Evidence-linked acceptance. A change ships when the evidence that it meets its criteria exists, not when someone says it does. Each criterion is linked to the evidence that proves it, and a change whose evidence is missing is not done, whatever its author believes. The practice is the same one the platform applies to its customers: a reading is a computation over evidence, and so is an acceptance.

#One source for every public claim. Every figure on the OntoRamp site is drawn from a single public-claims source, and the site is checked against that source before it ships. The same source fills every figure in this document, which is why the figures here are written as named constants rather than typed numbers, and why the document cannot silently go stale while the site moves. When a floor is overtaken by the live count, the constant is refreshed in one place and every surface follows.

#Disclosure review before publication. Public surfaces, this document included, pass a disclosure review before they are published. The review has two layers: a mechanical check of the text against what may not be said, and readers whose job is to refute the draft, who read it for mechanism that should have stayed at outcome altitude, for claims the evidence does not support, and for vocabulary the first layer did not anticipate. A surface is released when both layers are clean, and a problem found by the review is resolved, not deferred.

#Agents within human authority. OntoRamp builds with agents, and governs them the way it asks its customers to. An agent operates within limits a human has approved. Autonomy is granted in bands and widens only by a recorded human decision. The record of what an agent did and why it did it is kept so that the limits can be audited and tightened. We govern our own agents by the discipline we ask customers to show.

Part III turns to the road ahead: what is complete, what is in process, and what is direction rather than commitment.

Part III is for the reader who has to decide something: whether to engage, when, and on what evidence. It opens with the roadmap, because the honest answer to where the platform is going is also the honest answer to how much of it exists. The roadmap is stated in three bands rather than on a calendar. The active-complete band is what is built and live; refinement continues, but a reader can open it today. The in-process band is what is specified and under construction, with parts already live where the text says so. The future band is direction: themes we intend to pursue, with no schedule, no price and no promise attached, and each marked as such. Every entry is a theme, not a ticket. The record we plan from carries far more detail than this chapter, and that detail stays internal. A public roadmap that names dates will be held to them. A roadmap that names internal work items will be misread as a feature list.

#Active-complete.

#The agent front door and discovery. An agent can find OntoRamp, connect to it and consult governance before it acts. It does so through one discoverable front door on an open protocol, with a free plugin for the decision tools and standalone registry listings for the capabilities an agent most often needs on its own. The pieces that make that a round trip are in place: discovery descriptors an agent or an answer engine can read, including how to authenticate; intake of an assessment request from an agent; and readback of the result in a form the agent can act on. The commercial step, from the free tier to a paid plugin, is taken on the pricing page.

#The assessment and certification ladder. The Governance Ladder is in place end to end: the self-serve evaluation, the Decision Integrity Scan that leads into a full assessment, Enterprise Governance Assessment across all seven governance domains, the standalone Agentic Readiness Certification at L4 Resonant, and the Readiness Certificate that anyone can verify. One engine issues every reading.

#The Architecture Pack and the open exchange format. An organization's architecture is modelled as a standards-based model and can leave the platform the same way: the pack is delivered with a machine-readable export in the open ArchiMate exchange format. The exemplar that calibrates the engine is published in the same format, so the shape of the model can be inspected before any engagement and without anyone's architecture on display.

#Governance gate evaluation and the physics engine. The engine that computes a rung from evidence is live behind every door. The evaluation of a proposed decision, the pass, warn or block verdict of chapter seven, is live through the free plugin. Changes to the engine and its gates go through the discipline chapter nine describes: specified, evidence-linked and reviewed before they ship.

#Answer-engine readiness and the public-claims discipline. Every figure on the OntoRamp site comes from one public-claims source, and the site is checked against it before it ships. The same source answers the machine-readable questions an answer engine or an agent asks about what OntoRamp is and how to connect. This document is a product of the same discipline: its figures are named constants filled from that source at the date in its header.

#Knowledge-base integrity and customer isolation. The posture stated in chapter six is live. Customer evidence is scoped to the customer. Anonymous access to scoped data is denied, and that denial is tested by the platform itself. Every external door applies a classification ceiling, so that classification governs what leaves the platform regardless of the door.

#In process.

#Web-native presentation and governance reports. The readings the platform produces are moving from documents into surfaces. The Governance Assessment Report and the Transformation Roadmap become navigable, linked presentations in which each finding opens onto its evidence, rather than files that are read once and filed.

#Governed multi-agent execution. Chapter eight described it. A bounded group of agents is put to work on a pre-defined governance scenario within a cost limit the customer sets, and returns a decision packet and a governance attestation for a person to decide on. Parts of it run inside our own operation; the customer-facing form is specified.

#The governance agent and the continuous mode. The agent that keeps a governance picture current from the systems an organization already runs is built and operating in a pilot, in observation mode. Enforcement is built and switched off, and the agent's limits are applied by people today rather than by the platform. The continuous mode of the assessment, described in chapter seven, is what this agent becomes once observation, evaluation and enforcement are turned on in that order. The agent is designed as a dedicated instance for each customer, set up for that customer alone rather than as one service shared across customers, and it is built that way today in a pilot. The approved direction is for that instance to run inside the customer's own environment. Governed multi-agent execution follows the same model: it is designed to start hosted by us, and the approved direction is for it to move inside the customer's environment.

#Knowledge-graph quality, entity resolution and retrieval. The corpus is being brought to a defined mature state, and the work is measured against it. In that state each concept is held once with all of its evidence together, every answer is complete and traceable, the same question gets the same answer today and tomorrow, and every door answers with the same quality for everything it is permitted to answer. Duplicate concepts are being resolved with provenance kept through every repair; retrieval quality is measured; and every answer that leaves the platform is being made to carry the evidence it rests on.

#Executable-opportunity derivation. The capability described in chapter eight, by which the operating system tells an organization what it could do next with it and has not yet done, is specified and not yet built. It will be proven in our own operation before it is offered.

#Autonomy in bands. The discipline of chapter nine grants autonomy in bands, by a person's explicit act, and widens it only behind a recorded human decision. It is in force in part of our own operation; bringing all of our own automation under its terms is in process.

#Operational self-governance. The tooling that governs our own work is under continuous construction. None of it is an offering. All of it is the discipline of chapter nine made mechanical, and it is listed here because a company that sells governance should say what it is doing about its own.

#Hardening customer isolation. The posture of chapter six holds today, and strengthening it further is part of the current work.

#Governance in the deal. The first of the acquirer's three questions of chapter eight, the target's posture computed from its evidence, is answered today: the due-diligence use case on the OntoRamp site describes how the assessment reads a target from its governance material and returns a diligence summary, and the Decision Integrity Scan is the directional read that leads into a full assessment. The valuation computation that connects posture to what an enterprise is worth exists within our own operation and is not yet offered as a surface.

#Future.

#Enterprise deployment of the front door. An enterprise's own front door, isolated from the shared one; self-serve provisioning of an organization's own governed graph; a recorded sign-off step behind the highest certifications; and stronger isolation of one customer's knowledge from another's. The customer-environment deployment of the governance agent and of governed multi-agent execution, stated with the agent theme above, is the same theme seen from the agents' side.

#Reaching the agent where it already works. Connection guides for more of the agent platforms teams already use; channel integrations, so that a governance reading arrives in the tools where decisions are made rather than on a page someone has to visit; and a third mode of the live agent demo that shows the operating system in a scenario shaped like a customer's.

#Deliverables for the board. Board-ready packaging of the evaluation and the decision record; an export of the decision record as an audit artifact; an evidence map that links a reading to its sources; and a counter that shows what unmade decisions cost over time.

#The combined entity and the price. A due-diligence pack for acquirers and portfolio reviews; a projection of the combined entity's posture before close; and the translation of a change in posture into a change in what the enterprise is worth.

#Policy made public. The policy that governs what we publish, the rules that govern how we name what we publish, and the policy that governs isolation between customers, each published in its own right rather than applied silently.

#Where autonomy sits in each band. The autonomy discipline runs through the whole roadmap, so it is worth stating once, at band level, how much of our own work agents do and under whose authority.

In the active-complete band, people decide, and standing automation that a person has approved runs on its own. In the in-process band, agents work on tasks a person opens and scopes, which is how most of the platform is now built, and running several agents at once is proven in part. Bringing every piece of our own automation under the discipline's terms is itself in process. In the future band sit the wider forms of autonomy the discipline names but does not enable; each is held shut until a person approves the specific widening.

Autonomy is also bounded by a safety-pattern discipline that runs across every band. Our own controls are designed against a versioned set of named safety patterns, each tied to the harm it exists to prevent. A change to production is held until a recorded human authorization is attached to it. The patterns themselves are internal; what a customer can rely on is that the discipline exists, is versioned, and shapes the controls that are built.

A category is defined less by what its first products do than by what it makes it reasonable to expect. Four goals define the governance operating system as a category. Each is stated here with what already exists against it and what remains direction, so that a reader can judge the distance between the two rather than take the goal on faith. None of the four names a customer, a count or a date, because none of the evidence is of that kind yet.

#Governance posture as queryable as financial posture. A finance lead can state the organization's cash position to the day and show the ledger it came from. Nobody can state its governance posture the same way, because posture has been a survey result rather than a computed figure. The goal is that governance posture becomes a quantity that can be queried at any moment, by a person or a system, with the evidence behind it one step away.

#The governance-posture question as a board question. What is our AI governance posture, and can we prove it, belongs beside what is our exposure and are we solvent. Today the question is asked rarely, because it cannot be answered in one line and defended in the next. The goal is that a board asks it as routinely as it asks about cash, receives a rung, a credential and a roadmap, and can hand the answer to a regulator or an acquirer unchanged. For the acquirer the same question is asked of a target, and of the combined entity before close, and the answer should arrive in the same shape from the same evidence.

#The knowledge base as infrastructure other systems address. A knowledge base that only people search is a library. One that other systems address by name, through standard interfaces, is infrastructure. The goal is that an organization's governed knowledge is a service its own systems and agents consult the way they consult identity or payments. They reach it by a known address, with a known shape of answer, and without integration work for each new consumer.

#Certification as a public, verifiable instrument. A credential is an instrument only if a stranger can check it. Most governance credentials are a logo on a slide, taken on trust because nothing behind them can be opened. The goal is a governance credential that anyone can verify, issued from the same engine that computed the reading, carrying its rung and its status, and renewed on evidence rather than re-surveyed from scratch.

What the four goals share is the shape of the definition in chapter three. Each asks that governance be computed rather than surveyed, linked to its evidence, consultable by systems as readily as by people, and certifiable in a form a stranger can verify. The evidence so far is the system of Part II; the distance that remains is the roadmap of chapter ten. The last chapter says how to engage with either.

There are three ways in, and the rule for all of them is the same: everything that is self-serve is self-serve today, everything that needs time with our team is by request, and no path requires a conversation before the first useful answer. Prices are not stated here, because they move; current pricing is on the pricing page.

#The developer path. Discover the front door at mcp.ontoramp.com; the agent-native page describes discovery and connection, and the docs pages carry connection guides for the agent platforms teams already use. Issue a free-tier key. The free tier carries a generous monthly allowance. Free-tier queries return results from the client-safe tier of the knowledge base. Start with the free decision-intelligence plugin, so that an agent logs and evaluates its decisions against governance from the start, at no cost. When the questions get harder, move to the Knowledge Graph, the Governance Evaluator and the Projection Engine, separately or together as the Governance Intelligence Bundle; the plugins are reached through the same front door. The path ends on the MCP page, which lists each paid plugin and its tools, and on the pricing page.

#The executive path. Start with a Decision Integrity Scan if the organization wants a directional read before it commits: a structured interview and a board-readable report, with the business case for the full assessment. Commission Enterprise Governance Assessment for the reading across all seven governance domains and the three deliverables, the Governance Assessment Report, the Readiness Certificate and the Transformation Roadmap. Take the Agentic Readiness Certification, from the assessment or on its own, when the organization needs to show a board, a buyer or a regulator that it is ready to let agents act on its governance. Commission the Architecture Pack when the organization wants the standards-based model of its governance architecture before the plan. The assess page describes the assessment engagement; the certifications page and the agentic-readiness page describe the credential; the archimate page describes the pack; the pricing page carries the assessment services beside the plugins.

#Early access, by request. Anything that needs time with our team, the diagnostic session chapter seven mentions above all, is by request rather than scheduled. On the OntoRamp site the status reads Early access — by request. The request is made with the Request Early Access button on the assess page, and the note beside it says: Sessions are not self-serve yet. Your request joins the early-access list and we reply by email. Once a request is in, the acknowledgement says: You are on the early-access list. We review every request and reply by email. Those sentences are the whole of the promise, and this document adds nothing to them. The path ends on the assess page.

#Support. Questions on any path, about a plugin, a key, an assessment or this document, go to m@ontoramp.com, and we reply by the next business day. The support page states the same address and the same reply.

That is the whole of how to engage. The reader who wants to see the platform answer before deciding anything can do so now, on the free tier, with an agent of their own. The reader who wants a reading of their organization can commission one. The reader who wants our time can ask for it on the assess page.

Glossary #

The terms below are used in this document as the OntoRamp site spells them. Each appears in the body; the glossary fixes the sense.

• #The governance operating system. The category: the layer of an enterprise that holds its governance as a computed, evidence-linked, consultable artifact, with the engine that reads it, the interfaces through which agents and people consult it, the evidence record behind every answer, and the credential that attests to the result. Chapter three gives the full definition.
• #Governance integrity for agentic AI. OntoRamp's positioning line: the property that an enterprise's governed knowledge, its computed posture, the evidence behind it and the action an agent takes on it agree with each other, and that any disagreement is detectable.
• #OntoRamp Governance Physics. The methodology: evidence in, scores out; computed, not surveyed; the same public constants and the same computation for every organization read.
• #The Governance Ladder. The five rungs an organization's posture can occupy, each carrying a rung name and a credential name: L1 Fragmented, Governance Baseline; L2 Stabilized, Governance Readiness; L3 Coherent, Governance Maturity; L4 Resonant, Agentic Readiness; L5 Harmonic, Governance Autonomy.
• #Agentic Readiness. The credential name of L4 Resonant: the rung at which an organization can be trusted to let agents act on its governance.
• #The six readiness dimensions. Coverage, Governance, Integration, Execution, Assurance and Reflexivity: the dimensions across which a posture is read within each governance domain.
• #The seven governance domains. Platform, Data, Application, AI, Security, Governance and Capability: the domains the engine reads and the assessment reports on.
• #Knowledge Graph. The plugin that searches the governed knowledge base and returns entities, relationships, constraints and evidence with provenance; also the kernel the other plugins read.
• #Governance Evaluator. The plugin that computes an organization's rung on the Governance Ladder, the dimensions that put it there and the gap to the next rung.
• #Projection Engine. The plugin that projects the rung a proposed change would reach, the dimensions that would move and the gaps that would open or close.
• #Governance Intelligence Bundle. The three plugins together under one key; the phrase governance intelligence names the capability they deliver as a set.
• #The decision-intelligence plugin. The free plugin through which an agent logs a consequential decision, has a proposed decision evaluated before acting, and requests an assessment; also the registry identity of the same name.
• #Enterprise Governance Assessment. The full assessment across the seven governance domains, delivering the Governance Assessment Report, the Readiness Certificate and the Transformation Roadmap.
• #Decision Integrity Scan. The quick, directional read on how well an organization's consequential decisions are governed, delivered from a structured interview; not a credential, and its tier is not a rung on the Ladder.
• #Agentic Readiness Certification. The standalone L4 credential, evaluated across a subset of the governance domains, with the Readiness Certificate and a certification badge.
• #Architecture Pack. The one-time set of architecture deliverables built from the organization's own material, with a machine-readable export in the open ArchiMate exchange format.
• #Governance Assessment Report. The assessment's report: findings by domain, missing evidence, overall standing, and how that standing would move if the leading gaps were closed.
• #Readiness Certificate. The credential stating the rung reached, with its credential name, in a form anyone can verify.
• #Transformation Roadmap. The assessment's path to the next rung.
• #Registry identities. graph-query, decision-intelligence, knowledge-cartographer and governance-assessment: the standalone listings of the platform's capabilities on the public Model Context Protocol registry.

Publications #

The published work the methodology rests on, as cited in chapter eight, by public title and identifier.

• The Physics of Governance: Thermodynamic Limits of Autonomous Agents, 10.5281/zenodo.22151454.
• Ethical AI Series — Conservation of Intent, Volume I (Doctrine), 10.5281/zenodo.18930091.
• Ethical AI Series — Conservation of Intent, Volume II (Ontology), 10.5281/zenodo.18930283.
• Ethical AI Series — Conservation of Intent, Volume III (Limits + Closure), 10.5281/zenodo.18930366.
• Ethical AI Series — Conservation of Intent, Volume IV (Companion): Alignment & Safety Ontology + Intent Preservation (Non-Operational), 10.5281/zenodo.19304640.
• The Geometry of Governance: Volume III — Topology, Swarms, and the Physics of the GPU-G, 10.5281/zenodo.18665381.
• Intent-Aware Continuity in Evolving AI Systems: A Typed, Provenance-Aware Framework for Continuity Judgments in AI Governance, 10.5281/zenodo.21539741.
• Ontology of Valuation, 10.5281/zenodo.18663952.
• Structure of Valuation, 10.5281/zenodo.18664069.
• Harmonic Law of Valuation, 10.5281/zenodo.18664118.

The framework page on the OntoRamp site lists the published work with links; the three valuation volumes are cited here by identifier.

Provenance and notices #

Every figure in this document is a named constant resolved from the same public-claims source as the OntoRamp site, read on the date in the document header. Where a figure is a floor, it is stated as a floor, as the site states it. Where a figure describes the calibration exemplar, it describes a synthetic reference architecture, not a customer. When the source changes, the figure here changes with it and the header date moves.

Elements of the platform are patent-pending.

Revision cadence #

This document is revised in step with the public-claims source it draws on: a change to a constant it carries is a change to this document, and the header records the date of the figures. The roadmap chapter is re-read against the record it is drawn from at each edition, and the bands move only on evidence. A full editorial revision follows each material change to the platform's public surface, and the document is reviewed in full twice a year whether or not one has occurred. The status line in the header says which edition this is.