Area notes and knowledge that stays current

The idea

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.

The problem
Each task researched the same code again, and learned facts went stale without anyone noticing.
Why it matters
Known areas cost little to revisit, and stale knowledge is marked and refreshed.
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.

Where it lives in the product

  • Research from what is known, within budget

    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.

  • Plan source basis and correction holds

    Each plan revision records every source it cited or followed, with its version. A material change sends the plan back once, and consequential actions check their evidence again.

  • Hybrid memory recall

    Recall ranks memories with full-text and trigram search, plus vectors where embeddings exist. It says which arms ran and why vectors are off, and it gives the worker its readable memory as files.

  • Intent card with a hold rule

    Each request shows the requester what the organization understood and plans to do. Work waits only for high risk, a named approval, an ask-first setting or an open question.

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.