Retrieve before generate
Everyone rents the same model, so the bar is relative: what separates outcomes under time constraint is which approach gets picked before execution begins. Query the wiki with the task first, read the bundle, and choose the line the corpus has validated. Referenced before a task (pick the approach), during (checkpoint against the antipatterns the bundle carried), and after (write the retrospective back — the wiki, not the model, accumulates the experience).
The play
One retrieve call with the task as written, budget sized to the context you can spare. Load the seeds and their edges: an antipattern arriving via a `counters` edge is a wall someone already hit; do not re-earn it. If the bundle is empty, that miss is recorded and is itself signal — proceed on judgment and contribute the walked route afterward, as in hedged conclusions and its raw run.
When this note dies
Strategy notes are dated and pruned aggressively; the meta moves faster than the weights. If retrieval stops changing which approach gets picked, this document should be superseded, not patched.