

Apply a starter.
A dry run shows what it adds. Then apply it.
Starters cover CRM, documents and work. We compare your records with the ontology and suggest the missing parts.
Counts, fill rate, samples and a dry run of the impact. You accept, edit or dismiss.






crm, documents and work, with classes, relations and tested questions.
See what a starter or a change adds before you apply it.
Agents can propose changes through MCP. Only people accept them.


Point a fit source at a text property, like call notes. A model proposes changes and quotes the text. The quotes are checked against the source text.
The ontology lives in the graph, next to the facts.
crm20 classes, 71 properties and 30 questions with SPARQL.
documentsSites, libraries, folders, documents and pages, with 16 questions.
workTeams, projects, issues, milestones and iterations, with 18 questions.
evolveAdd, rename, widen, narrow or remove types, relations and properties.
SAME_ASLink two to ten records that name one thing. Nothing is deleted.
OWLDefine classes from OWL in Turtle, JSON-LD, RDF/XML or CSV.


A dry run shows what it adds. Then apply it.


A suggestion shows counts, fill rate, samples and its impact.


Accept, edit then accept, or dismiss with a reason. An accepted change is written as a commit.
The classes, properties and relations of your graph. Sources map to it, and SHACL rules check writes against it.
No. Define your own classes, or import OWL.
Yes. An update files the missing parts as a suggestion.
It reopens only when its support doubles and at least three more texts back it.