ora-0161

14.4 A repair ledger

A persistent learner should store repair as an object rather than erase it after updating. One useful ledger entry has the form

\[ \begin{array}{c} \text{boundary and missing face}\quad |\quad \text{defect decomposition}\quad |\quad \text{repair-space profile}\\[2pt] \text{selected component}\quad |\quad \text{preserved obligations}\quad |\quad \text{new probes and accommodation map}. \end{array} \]

In the crossword example, a candidate word is a local filler, crossing letters are settled boundary data, and a contradiction localizes to the smallest incompatible across–down overlap. In an agentic team, the missing face may instead be a revocation composite: the declared stop action exists, but no coherent filler shows that it reaches a delegated process. The ledger then records a structural safety obstruction rather than merely a failed command.

Guiding question.

Which failed fillers can be repaired inside the declared decision diagram, and which require changing the declaration itself?