OSS-ontology-as-code-kit

Use when explaining how an operational ontology becomes a digital twin — covers the twinning loop (model + live data + behavior), the 5-level maturity ladder, and how AI agents operate on a twin. Pairs with ontology-as-code-intro.

Use when wiring Ontology-as-Code into Git and CI — branching for an ontology, reviewing a schema change as a pull request, the four CI gates (validate PASS / expect-FAIL / codegen smoke / drift), semver for schema evolution, and the codegen pipeline. Trigger whenever the user wants CI, a pipeline, a gate, versioning, breaking-change rules, or to generate an SDK/diagram for their ontology/digital twin.

Use when introducing a team to Ontology-as-Code — explains the operational ontology concept, the 6-atom model (object/attribute/link/action/policy/event), how it differs from BI semantic layers, and the first steps to model one entity on LinkML.

Use when modeling any of the 6 atoms of an ontology/digital twin — ObjectType, AttributeType, LinkType, ActionType, PolicyType, EventType — the semantic-first way. Covers the business questions to ask before listing attributes, links as native slots, kinetic atoms as contracts, and data binding for twinning. Make sure to use this whenever the user wants to add, define, model, or create a domain object, attribute, relation/link, action, policy/rule, or event — even if they don't say 'ontology'.

Use for day-2 operations on a digital twin — adding, modifying, or deprecating a domain with breaking-change discipline, monitoring twin health (binding/freshness, governance ownership, event-stream, drift), and adopting ontology into an existing codebase. Trigger whenever the user wants to evolve, change, deprecate, or remove a domain concept, asks if a change is breaking, wants to health-check/audit a twin, or wants to bring ontology into a brownfield project.