From prompt to loop
Prompt, context, harness, loop — the sequence is not a ladder of improvements, it is a series of admissions. Each discipline exists because the previous one was caught assuming something it had no right to assume. And the last one still assumes one thing: that somebody declared what «done» and «safe» mean, and that the declaration is still true. A walk through what ontoref has been putting under each station — declared vocabulary, governed context provision, checks that declare their own coverage, a loop that proposes its memory and never applies it — with the counter-evidence included: four mechanisms that already forbade a failure, in writing, and not one of them fired.
A written rule does not apply itself
No rules were missing. There were four — written, canonical, consultable — and not one of them ran. A real case, with a log and timestamps, about the distance between a rule that is written and a rule that applies. The answer is not 'be more careful': it is a trigger — a hook that serves the rule where the decision happens, a gate in a chain somebody calls, a contract that rejects the file. And the honest part: ontoref, declared, was already there, and it was not enough.
Ontoref: Ontology and Reflection
The slides from the Ontoref talk: why a project's ontology and reflection should live with the code — versioned and verifiable. Navigable carousel + downloadable PDF.
5 items