Customer Ontologies

A versioned overlay of your own document types and field concepts that augments the built-in Talonic ontology. List and create ontologies, then author, publish, and project them.

A customer ontology is your own overlay on top of the built-in Talonic ontology: a versioned container of custom document types and field concepts specific to your domain. You define the doctypes you care about (a "Lieferschein", a "Rahmenvertrag") and the fields that matter on them, anchor each doctype to a Talonic type, and publish. Publishing projects your authored fields and doctypes into the field registry and the classifier, so extraction and classification start recognizing your vocabulary.

Ontologies are versioned with a draft/publish lifecycle. Editing a published ontology auto-forks a new draft, so the published overlay your pipelines read never changes underneath them mid-run. The overlay is additive: an empty or unpublished ontology leaves capture and classification byte-identical to the Talonic-only path, so adopting ontologies never regresses existing behavior.