C.19:8 - Common Anti-Patterns and How to Avoid Them

• Using deployment readiness to settle research continuation. Judge active exploration and cheaper retention by their prospective contribution and remaining cost. Keep the actual qualification for deployment or transfer; past expenditure is not a reason to keep funding the line.

• Treating one scalarized top-1 as the frontier. Avoid by naming the governing lens and keeping the live frontier distinct from any lens-ranked pick.

• Running exploration without one explicit next treatment. Avoid by ending each pass with one explicit currentTreatment token: widen, keep_frontier, narrow_to_subset, or sunset_line. If the current question is no longer pool policy, name the next subject pattern instead of inventing another pool treatment.

• Letting Surprise or Illumination quietly become dominance criteria. Avoid by promoting them only through one declared lens or policy id and recording that promotion in provenance.

• Absorbing neighboring questions. Avoid by using the exact handoff values in C.19:4.4 instead of adding a neighboring result’s fields or claims to PoolPolicyResult.