04 / Engineering
Produce high-quality ontologies at scale, with a low barrier
Companies do not want a handful of one-off ontologies. They need semantic assets that move from "buildable" to "usable, manageable, operable". Domain experts need no technical skill; they answer questions.
Five linked rings of ontology engineering
- Pre-processTurn multi-source knowledge into standardized "semantic raw material"
- ModelAI and experts jointly generate the ontology
- RegisterSemantic assets stored centrally, verifiable
- PlatformVersions, permissions, reuse
- DeployPlug into business scenarios, serve AI agents
The "7+1" semantic specification × 29 sentence patterns: say the business clearly
Twenty-nine standardized natural-language templates are the "grammar" through which AI understands a business. AI reads forms, documents and manuals and extracts automatically; domain experts speak in the patterns and surface the implicit knowledge no document contains. Three kinds of expression map to three kinds of knowledge and three sets of open standards.
State "what objects exist"
Unify terminology, define attributes and relations, separate common, domain and instance layers.
SKOS · RDF · OWL
Conceptual knowledge
State "how tasks are done"
Decompose atomic actions and link them to objects; define how ontology data is operated on and queried.
OWL-S · SPARQL
Procedural knowledge
State "what rules apply"
Make business control points explicit as "if… then…"; set semantic boundaries and role permissions.
SWRL · OWL · ODRL
Rule knowledge
29 standard question types
- Who approves this step?
- When should a quote be marked up?
- Which machines does this operation depend on?
- Who decides when an exception occurs?
AI requirements engineer
FDE Agentinterview · probe · extract · structure
Generates the ontology directly
Domain experts only answer questions. The FDE Agent follows each answer to probe exceptions and boundaries, then distills the spoken material into conceptual, procedural and rule knowledge. FDE borrows from Palantir's Forward Deployed Engineer, the on-site role that translates client needs; we turned that role into an agent.
Why now: what agents consume has changed
- 2022Hard-coded flowsIn-house scripts · early LangChainHumans write thousands of lines; any business change means changing code
- 2023Drag-and-drop flowchartsDify · n8n · CozeHumans drag dozens of nodes; the flow is still fixed in advance
- 2024Graphs that loop and branchLangGraphBranching and retries, but every path still designed by a human up front
- 2026Just a goal and one documentClaude Agent SDK · Claude CodeA human writes a one-page process doc; the AI breaks it into steps and checks as it goes
- SoonNo document at allA trend taking shapeThe AI interviews business staff itself, writes the document and assembles the agent
Earlier agents consumed flows, and translating a business into a flowchart is exactly where tacit knowledge gets lost: a veteran's "depends on the situation" judgments cannot be drawn as nodes and edges. Only an agent that reads documents can catch them. Our approach: the newest agent engines, running on top of an ontology. A human gives the goal and the ontology; the agent reads the ontology to understand, plans, executes by querying data through the ontology, observes and corrects until done.