Item F3: A layer's theory is authoritative and its only code is in a disposable tree

projects/normativity/consolidation-aug9/ states the answerability ledger and the case docket in Theory 9 and carries their rows in its ledger. Its src/ does not implement either. The only executable version of both is projects/normativity/forward/src/, whose own FORWARD.md says the tree "may be changed, rewritten, or deleted wholesale at any time without loss" and that "nothing here is evidence for anything."

So a round building on that layer must either import from a disposable tree or reimplement it. The φ-regret preparation round reimplemented the obligation fields it needed and recorded the adapter as architected rather than verified, because no cross-check against the original is meaningful when the original is not evidence.

Three ways out: consolidate the two modules into a frozen tree; promote them to a stable path outside the disposable one; or rule that the theory rows stand without executable support and that adapters are the expected pattern. The choice turns on whether the program means to keep building on that layer, which is why it is in DECISIONS.md's queue rather than taken here.