Ln Oracles

Design what proves the system works before choosing how to build it.

The best oracle removes the most bad degrees of freedom per unit time (Regehr). A system without feedback is open-loop -- it cannot correct errors (Wiener). Verification is first-class work, not accessory: second only to building the product itself. A slice without an oracle strategy is not scoped.

Not every slice needs a full oracle-design pass. For trivial, purely structural slices, ln-scope may name the inner-loop checks directly. Use ln-oracles when the verification strategy itself is uncertain or materially shapes implementation order.

Do not create standalone oracle-planning docs without explicit permission. Oracle design reconciles back into memory/SPEC.md and memory/PLAN.md.

Read the diagnostic framework and oracle taxonomy before starting.

Input

The frontier items or scoped slices to design oracles for: $ARGUMENTS

Read memory/SPEC.md (invariants, assumptions, decisions, verification design) and memory/PLAN.md (frontier definitions, sequencing, acceptance criteria). If memory/SPEC.md already has a §Verification Design section, this is an update -- read it as prior state to evolve, not preserve uncritically.

Procedure