An SMB ontology is not a dictionary

A service owner does not buy an ontology. The owner buys a tool or workflow that may classify calls, route tickets, prepare invoices, or tell a manager what needs review.

That makes the first vendor question plain: show what one business word changes in the work.

Use “callback” as the test case. This is a hypothetical test, not a claim about one observed customer. It is useful because Hadto’s public home-services language already treats callbacks, dispatch pressure, invoices, and blocked decisions as operating surfaces. Hadto’s domain-research offer also promises domain maps, competency-question packs, and source-of-truth memos.

A vendor can define callback as “repeat visit” or “customer complaint.” That may be enough for a glossary. It is not enough for a workflow map. The buyer needs to know what the term is allowed to start, decide, block, or send to review.

Run the Term Walk-Through

Hadto’s judgment is narrow: do not let a term control workflow until the team can answer five questions.

1. Which records can use the term: dispatch board, call note, work order, invoice, warranty policy, photo packet, or manager note?
2. Which operating question does it answer: schedule this visit, bill this visit, hold this invoice, mark warranty review, or ask the owner?
3. What action is the term allowed to trigger?
4. Who owns the hard case?
5. What happens when proof is missing?

The last question matters because “unknown” is often the honest state. A customer saying “same issue again” can start a callback review. By itself, that sentence should not settle warranty status, labor billing, technician accountability, or customer-credit decisions. The tool should be able to say which proof is missing and who has to decide.

Behind this wording is Hadto’s 2026-06-05 internal study lane on Ludwig Wittgenstein’s Philosophical Investigations. The study source is not the reason a service owner should care. It is the internal source for Hadto’s wording: a word gets its role from use, examples, boundaries, training, and the activity around it. In this post, that becomes a buying rule. The label matters less than the work the label is allowed to do.

Use the Callback Test

Ask the vendor to walk through callback on screen.

The vendor should show which records can start the case, which records can decide the case, and which records only add context. A customer report may create a possible callback. A closeout note may narrow the symptom. A warranty policy may set the coverage question. An invoice may affect billing review. A manager or owner decision may be the only thing that turns the case into warranty rework, billable return, planned follow-up, or unresolved review.

Those states are examples for the test. They are not a universal service-business taxonomy. The point is to see whether the vendor separates evidence from decision authority.

Then ask what happens downstream. Does the term schedule a technician, hold an invoice, create a manager queue item, update a customer record, or do nothing until review? Where can an operator reverse the decision? What record explains the reversal?

This test does not prove the vendor is strong. It catches a weak answer. If the vendor can only show a clean list of terms, the buyer has seen a dictionary. If the vendor can show the source records, operating questions, review owner, missing-proof state, and downstream action for one important term, the buyer has a better next question: does the same discipline hold for the other terms that touch schedules, invoices, approvals, and customer commitments?

---

Source evidence used in this note: smb-ontology-platform/docs/plans/2026-06-05-wittgenstein-philosophical-investigations-value-extraction.md, for the accepted wittgenstein-meaning-as-use-for-smb-ontologies candidate and its remarks 1-88 source context; smb-ontology-platform/research/manifests/ontology-study/wittgenstein-philosophical-investigations.yaml, for source identity for Ludwig Wittgenstein’s Philosophical Investigations PDF captured 2026-06-05; src/data/serviceOffers.ts, for Hadto’s home-services language around callbacks, dispatch pressure, invoices, and blocked decisions plus domain-research language around domain maps, competency-question packs, and source-of-truth memos; src/data/terminology.ts, for Hadto’s operating-system definition.