# A finding written in a doc doesn't change the system

A finding has not landed unless you can name the executable line it changed.

By Ki Moon · 2026-08-03 · finding · current
Canonical: https://kihmoon.com/bench-notes/p/finding-in-a-doc-changes-nothing/

**Symptom:** A lesson already written in a process doc's notes gets rediscovered, while the doc's scoring step is unchanged.

My account-selection process had a pain-points section. Early in the year it recorded a clear insight about which kinds of accounts fit best.

Five months later I derived the same profile from scratch, because the finding never reached the line the process runs.

Its scoring still weighted a signal that pushed exactly those accounts down, and every quarterly run repeated the miss.

The step now calls my shared fit rubric instead of hand-rolling its own scores. A rubric edit reaches every run the same day, because the rubric is the mechanism.

The reverse direction drifts too. When I retired three holds from a daily sweep, four prose copies kept describing them as live:

- the runbook
- the root instructions file
- a memory note
- the script's own header comment

Anyone reading those trusted a net that no longer existed, and agents read the same docs.

## Check your setup (read-only)

Take the 5 newest lessons in each process doc's notes or pain-points section. Search the scoring rubric, filter or gate code that the process runs for a line that encodes each lesson. A line encodes a lesson if it names the same field, value, threshold or condition the lesson names. More than 1 of 5 with no such line is a gap.

**Passes if:** 4 or more of 5 sampled lessons per doc map to a scoring, filter or gate line. Each line is in the code or rubric the process runs.

**Access needed:** local-config

## If it fails (changes to make later, not part of the check)

1. Name the scoring, filter or gate line a finding changed, after you land the finding. A finding that changed no such line has not landed.
2. Replace hand-rolled scoring inside a process with a call to the shared rubric.
3. Search docs, instructions, memory and script comments for the old phrasing when a gate or threshold changes in code. Do the search in the same session as the change.
4. Correct every restatement you find before you call the change done.
5. Close the old documented findings that a changed mechanism now resolves.

**Applies if:** Your setup has process docs with a notes or pain-points section, kept apart from the code or rubric the process runs.

**Skip if:** Every process in your setup is code, and each process doc is generated from that code.

Tags: drift, deterministic
