Methodology should live in machine-readable artifacts

Keet Chapter 5 applied to Hadto: methodology matters only when the reasoning behind the model survives handoff.

Why this matters

This post shows how explicit models, workflow controls, and evidence trails make the business easier to inspect, teach, and run.

Why this note is here

Source check: Checks whether the source is useful before it shapes the work.

What supports it: Uses evidence, definitions, and cause-and-effect.

ontology engineeringmethodologyhadtoventure operations

A methodology is not infrastructure if it disappears when the first operator leaves.

Keet’s discussion of macro-level ontology development methodologies lands on a practical point for Hadto: the model is not enough. The decisions behind it have to survive inspection, reuse, and handoff.

For Hadto, the same rule applies to company-building. The platform is trying to help domain experts become owners by giving them systems they can actually inherit. Reasoning trapped in meeting notes or one founder’s memory does not transfer.

The handoff artifact

Methodology matters when it records what the system is for, what it must answer, and who is responsible for keeping it aligned with the business.

A concrete example is a competency-question register stored as machine-readable data:

artifact: competency-question
question: Which operating decisions can a shop owner delegate without losing control of quality?
linked_model_area: role-boundary
depends_on:
  - handoff-rules
  - service-quality-checks
owner: operations
last_reviewed: 2026-04-02

That artifact gives the next operator something to inspect. It shows what the model has to answer, which workflows depend on it, and who owns the decision when the business changes.

The artifact should preserve a small set of things:

the business problem the model exists to support,
the questions the model or workflow must answer,
the standards, sources, or reuse candidates that shaped the design,
the owner responsible for reviewing the artifact as the business evolves.

Those are not side notes. They are part of the operating contract.

The operating test

Venture creation only becomes repeatable when a future operator, apprentice, or teammate can see the structure, the reason it was chosen, and the part of the business it supports.

Many of the people using the platform will be domain experts first, not ontology specialists. A methodology buried in conversation history leaves the business dependent on a few interpreters. Machine-readable artifacts make it easier to teach, audit, and hand off.

That is the standard: reasoning that cannot survive in an artifact another operator can inspect is not yet part of the system.

Follow this concept

Compare services that make the work inspectable
Use the services page when the note points to workflow, source-of-truth, or handoff repair.
Read the operator path that depends on visible work
See how explicit methods become the basis for authority, accountability, and ownership.