Writing
Software that knows: the rule nobody owns
A refund policy with six sources and no owner. Written down as a model, it cannot decide either, but it shows exactly what has to be decided.
Software that knows: from a diagram to a decision
A popular comparison diagram, written down as facts, questions and its author's rules: an app that asks only what matters, decides and says why.
Software that knows, in detail: from statements to a working form
How a generator of about 370 lines turns the statements of a knowledge model into a form, validation, rules and words, without knowing what fever is.
Software that knows, in detail: what's in a field
One input field in an ontology, from bare concept to translated question with a rule: what an application keeps in ten places, stated once.
Software that knows: the knowledge model as grounding
A free-text note instead of a form: four interpreters, from plain words to LLMs, all grounded in the same knowledge model.
Software that knows: from guideline to application
A working application built from published WHO guidance: where the knowledge comes from, the two models behind it, and what an agent does.
Software that knows: where knowledge sits
One fever rule, found in code, a database, configuration, an SOP and a clinician's head. And the alternative: one formal, explicit file.
Software that knows: what knowing means
Data, information, knowledge, understanding and wisdom: what it means for software to know, from raw bits to judgement.
Software that knows: why now
Formalising business knowledge used to be slow and expensive. LLMs make the first draft cheap. Review and accountability stay with people.
Software that knows: the hypothesis
Business applications keep business knowledge implicit in code. A hypothesis: make it explicit and put it at the centre of the software.