These packs are starting points — versioned, signed, installed like a model. The ontology that actually runs your business is built with you, in workshops led by people who have modelled businesses for twenty years — and then it grows, from the data it learns, like a living organism. It is the one part of this platform nobody can generate. Every pack sits on Discern, the semantic core we share with EdgeSec, and adds your vertical's entities, verbs and rules on top of it. Every pack ships as entities · links · actions · rules and keeps growing from the data that flows through it.
Every fact in your graph is typed when it arrives, records who asserted it and how sure they were, and is KNOWN, CONFLICTED or UNKNOWN. A model can propose a fact; only a sensor or a person can make it known. The same entities are visible to your operations and to your security team, because both sit on the same core.
A pack gets you to the first conversation. What it cannot know is what your business means by a confirmed booking, a sellable night, a returning guest — and who gets to decide. Those are decisions, not data. They are made in the room, and they are the ontology.
Discovery. We sit with the people who run the business and learn your systems, your vocabulary, the questions your people actually ask, and who owns each definition.
Modelling. We write the definitions, the rules and the exceptions — with the owner of every term named — and wire them to the systems that hold the facts.
Growing. Then it lives. Connectors feed it, it learns from the data that flows through it, and a person on your side reviews what it proposes. It does not stop growing. How we grow it is our trade-craft.
Why there is no shortcut. AI-generated code can wire a screen in an afternoon. It cannot sit with your general manager and find out that a dirty room is not inventory, or that a hold is not a booking until the slow channel acknowledges it. The complexity is in the business, not the software, and it takes human hours to model. We don't sell shortcuts here, because there aren't any.
Who does it. Ontologists with twenty years in the field — people who have modelled operations before there was a model to put them in.
| Entities | Guest · Booking · Unit · Party · Activity · Release · Task · Rate · Policy · Channel |
|---|---|
| Links | Guest holds Booking · Booking occupies Unit · Activity requires Release |
| Actions | book · reschedule · send-release · route-workorder · escalate |
| Rules | No activity without signed release · quiet hours · refund thresholds |
| Entities | Customer · Site · Equipment · Job · Technician · Invoice · Contract · Part |
|---|---|
| Links | Equipment serviced-by Job · Job assigned-to Technician · billed-as Invoice |
| Actions | dispatch · quote · order-part · schedule-maintenance |
| Rules | Warranty gates · SLA clocks · permit requirements by county |
| Entities | Policy · Insured · Carrier · Coverage · Claim · Renewal-Clock · COI · Producer |
|---|---|
| Links | Insured holds Policy · Policy written-by Carrier · Claim opened-on Policy |
| Actions | verify-coverage · open-claim · issue-COI · renewal-outreach |
| Rules | E&O-safe: graph-only coverage answers · licensed-state routing · catastrophe mode |
| Entities | Brand · Caller · Script · Escalation · Shift · Account · Ticket |
|---|---|
| Links | Caller reaches Brand · Ticket escalates-per Account rules |
| Actions | take-message · page-oncall · open-ticket · transfer |
| Rules | Per-brand greetings · HIPAA lines · on-call rotations |
| Entities | Truck · Driver · Load · Lane · Stop · HOS-Clock · Broker · Invoice |
|---|---|
| Links | Driver operates Truck · Load moves-via Lane · HOS constrains Dispatch |
| Actions | tender · assign · detention-claim · check-call |
| Rules | HOS-aware always · detention clocks · lumper approvals |
| Entities | Patient · Appointment · Provider · Insurance · Referral · Room |
|---|---|
| Links | Patient holds Appointment · Appointment with Provider |
| Actions | schedule · verify-coverage · recall · remind |
| Rules | PHI never leaves · consent gates · no-show policies |
| Entities | Part · Program · Measurement · Machine · Lot · NCR · CAD-Asset |
|---|---|
| Links | Measurement of Part per Program · NCR opened-on Lot |
| Actions | run-report · flag-drift · quarantine-lot |
| Rules | Design IP never leaves · calibration windows · sign-off chains |
Packs are starting points, not ceilings — the ontology we build with you has unbounded entities, links and action types. It is yours: open formats, Cypher export, documented, portable. Read the field guide →