dsh-ontology-kernel

Building business plugins on DeepSeek Harness often means juggling ontology concerns—registering object types, link types, Functions, and Actions—while local persistence and browser-side projection live in separate, ad-hoc pieces. dsh-ontology-kernel collapses both into a single installable bundle that exposes one unified ontology interface, keeping adapter mechanics out of the way for upper-layer developers.

Two internal paths do the heavy lifting: business plugins contribute versioned object types, link types, Functions, and Actions through ctx.ontology.register(...), and the local adapter persists them via the Harness storage domain. When a front-end view is required, the remote adapter projects the active runtime to the browser through typed Typert Remotes, so browser plugins simply consume ctx.ontologyRemote without any dependency on the storage layer. The two adapters are inserted in a fixed order, and a later profile patch can replace either one without touching a single line of business code.

If you are writing a business plugin on Harness and need a structured ontology model to describe domain objects, their relationships, and executable actions—or if you want the front-end and back-end to share the same type definitions instead of maintaining parallel copies—this bundle is built for that. It does not opine on your domain logic; it simply guarantees a consistent, replaceable, and versioned registration path for every ontology definition.