Your subject is not for rent
The harness post left a question open: if your project's knowledge lives inside the harness profile, switching harnesses means losing it. The market's answer — move it out to an external knowledge base — solves one coupling by introducing another. This post walks the harness layer by layer through the pairings nobody decides and everybody assumes, and proposes the change of regime: from renting to owning. No villain: every step of the enclosure is reasonable on its own, and that is exactly the problem.
Your Ontology Should Live With Your Code
Enterprise knowledge graphs live in a triplestore maintained by a dedicated team on a vendor's platform. When the team changes, the budget gets cut, or the vendor pivots, the knowledge disappears. Ontoref takes the opposite approach: sovereign, local-first knowledge that lives alongside its subject, versioned, queryable across four surfaces, and federated without a central broker.
2 items