Bounded · one receipt
Research with limits
Your team needs competitive context and lessons — not another infinite research thread. One bounded gather, one stable file, one receipt that says what was saved and where.
How it respects your time
Archive search hands context in. Research runs in a bounded scope — one named output, then stop. No registry sprawl, no "helpful" side files.
What your client receives
Benchmarks, pitch stats, lessons — attached where they belong, with a PASS receipt that proves the gather completed under policy.
When to use it
Before a build, before a board deck, before you paste a megachat into a worker prompt. Context first — governed — on disk.