Case 0/8: the advice that never kept the answer

🕵️ Show the full case file → 📋 Session protocol →

Case file · Code Homicide Dept.

The broken mechanism was not just any mechanism: it was the cure of an earlier case. It fired eighteen times, was heard all eighteen, and evaporated all eighteen. It cured the half it was asked for.

The double ledger — what it cost, and what it left

The suspects — the false leads

The weapon — The hook, up to that line

# ~/.claude/hooks/onre-prompt-orient.nu — its own header, lines 18-19
#
# No ata. Inyecta un puntero, y un puntero es un consejo — la misma prosa que no ató las
# otras cuatro veces. Lo que hace es convertir «no sabía que existía» en «lo sabía y elegí».

print ($out | str join "\n")
# ← and here the function ended

And the layer where that was meant to be recorded had been finished for months. ADR-037: Accepted. Schema with a Hard constraint. Migration 0028, applied. Seven verbs exported. The file never came into existence.

The turn — The same file, two calls more

# the same file, lines 154-157 — after the `print`, where nothing was
for p in $served {
    let w = (do { ^$bin interaction pointer $"($p.k):($p.v)" --session $sid --quiet } | complete)
    if $w.exit_code != 0 {
        print $"  [on+re] warn: puntero no registrado \(($p.k):($p.v)\) — ($w.stderr | str trim)"

# and in `qa show`, at the point the entry is actually served:
interaction pointer $"qa:($id)" --consumed --quiet

#   served → status 'pending
#   read   → status 'ok
#   an unclosed 'pending IS the finding

Writing it cost three more defects, all three found by executing and none by reading: the sensor printed its confirmation inside qa show’s JSON; the cure lived for twenty minutes only in the source while the hook kept running the installed copy; and the detector for that very drift came back green over zero files on its first run — case 0/10 reproduced inside the gate written to prevent it.

The verdict

This hook is not just any instrument. It is the cure of case 8/4, «the discipline with no trigger» — that case was about four mechanisms nobody fired, and its cure was precisely this: serving what governs the task in the prompt itself. It fires. It fired eighteen times. It was heard. And it evaporated every time.

A project that cures and never verifies the cure accumulates half-cures, and that pattern is only visible if what was served and what was consumed are counted separately. Aggregated, this session reads «consumed half». Separated: the prose was read 4 times out of 8 and the procedure 0 out of 8. That is not distraction, it is a selection — reading is cheap and cedes nothing; running the DAG hands the wheel to steps with owners, two of them human.

The friction the procedure would have charged in twelve small instalments arrived whole at the end, in a single bill. The project’s own ontology had written it down before it happened: emergence with no floor is not wu-wei, it is drift; friction deferred, and deferred friction arrives as loss.

The reconstruction — the session, replayed with protocol

What was asked — reconstructed from ~/.claude/projects/-Users-Akasha-Development-ontoref-outreach-site/b791be36-….jsonl, first `type=="user"` record — verified that the three lines are one message, not three. Kept in the original Spanish: a verbatim prompt is evidence, and translating it would make it a paraphrase

no se supone que https://ontoref.dev/docs/expedientes/protocolo.html
debería reunir automáticamente los expedientes ?
por qué no están todos y esto no funciona ?

What should have been asked

The page collects replays, not case files. Before touching anything: tell me how many cases
there are and how many have a replay, with the command that counts it. If the answer is
«replays are missing», that is `mode:generate-case-file` step 6, and you run it — you do
not compose it on the side.

The gate before delegating: Compose nothing and delegate nothing until ontoref run status returns a run for this mode. It returned null for the whole session and nobody looked.

The ADR trigger: «May a mechanism declare itself advice and not keep the answer?» It is an architectural decision with a consciously rejected alternative — the blocking gate — and a lasting constraint on every future advisory instrument.

Case law — what enforces the lesson today

• ✓
  A machine format that does not parse is a broken surface, and the exit code will not say sogate:just test-machine-output
• ✓
  The source is not the running system until it is installedgate:just check-runtime
• ✓
  The record's shape was already written: 'Read with 'pending or 'okcontract:.ontoref/reflection/schemas/interaction.ncl#events
• ✓
  A number that cannot be traced is dropped, never estimatedmode:generate-case-file/gather_metrics
• ✓
  The howto governing the series, which this session did read 4 times out of 8qa:case-file-howto

⊘Declared debt: Nothing obliges anyone to look at the ratio. interaction pointers pairs and reports, and no gate reads it — deliberately: the tension it measures is a Spiral, and a Hard biconditional there is the pattern this project forbids by name. But the honest outcome is that this lesson ended up SERVABLE with its consumption UNOBLIGED, which is the same shape as the defect the case denounces, one plane up. And there is an uncollected bet: that the choice is recorded does not prove it will be chosen better. What would settle it is a ratio measured over time — the emergence proxy that the enforcement-vs-emergence tension declares absent. It would be falsified like this: with the trace present and read, if the DAG keeps being declined 8 out of 8 with the same wreckage, the cure is insufficient. Separately, filed as bl-051: the run store cannot record steps with two concurrent sessions, so today the evidence that a DAG was followed depends on nobody else working in the tree.

One bet remains uncollected, and the case does not hide it: that the choice is recorded does not prove it will be chosen better. That will be known by counting. If, with the trace in plain view, the procedure keeps being declined eight times out of eight, the fix was insufficient and we will be back here. That figure does not exist yet — and that it does not exist is exactly what this case came to repair.