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.