Research from what is known, within budget

The idea

Research opens with the area notes, earlier research and rules for the named paths, and reads only what they leave open. At its effort budget it gets one turn to ask for more.

The problem
Research read known code again and ran past its budget.
Why it matters
Research time goes to what is still unknown.
Where it stands
In production as of

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

  • Area notes and knowledge that stays current

    Research writes a note for each package or folder it touches, kept while the files do not change. Facts tied to a page or ticket go stale when it changes, and pushes to the default branch update ties and notes.

  • One effort allocation per item and stage

    One decision per item and stage picks low, medium or high effort. That level sets the stage's turns, time, cost, rounds and consultations, and the worker can ask for more.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.