Object types

Things, not tables

Discern describes an operation as objects with types. An asset, an order, a customer, a door, a camera. Each has attributes, and each attribute knows where it came from and when.

DISCERN · THE ONTOLOGY IS THE PLANE One typed model of the operation. Everything reads from it; only a human promotes into it. Consoles Every role sees the same facts Ontonio Voice and presence on the appliance Reports & automations Read the graph, queue the action reads ONTOLOGY · DIGITAL TWIN OF THE OPERATION places for emits sends generates observed at Customer Order Asset Message Invoice Accessevent Incident POLICY + HUMAN promotes · never the model SOURCES · TYPED AT INGEST ERP CRM SMS Access control Cameras Accounting every fact carries provenance proposes facts MODELS · A WATERFALL, NOT A CHATBOT Graph → Edge SLM → Heavy → Frontier 92% of questions are answered by the graph and never reach a model. proposes, never promotes KNOWN · promoted, provenance on file CONFLICTED · two sources disagree, surfaced not hidden UNKNOWN · proposed, awaiting policy and a person

A relational table stores rows. An ontology stores things. In Discern every thing has a type from a small, fixed vocabulary, a stable identity that never changes even when its label does, and attributes that each carry a source and a time.

Types are locked, labels are not. An asset renamed from "Line 3" to "North line" keeps every order, access event and message that ever referred to it, because they point at the identity, not the name.

Five kinds of capability touch these objects, each defined by its relationship to the graph. An engine serves it. A connector proposes facts into it. A sensor proposes events. An actor proposes actions. A view only reads. Nothing but a person or a policy promotes.

Worked example · A work order is created

A scheduling system sends a work order. It becomes an Order object with a stable id, typed attributes for the requested date, the site and the crew size, and a link to the Asset it serves. The customer's identity is pseudonymised before anything leaves the appliance.

a worked example in generic terms; every operation renames the labels, the shapes do not change