What lives in the hub
As work happens, its outputs are written back as durable artifacts:Every finding carries its evidence
A finding in the hub is never just a claim. Each one links back through an evidence chain to the task and agent that produced it: the run, the queries, the plots, the reasoning. This is what makes a finding safe to reuse: the next person can see exactly how it was reached and decide whether it still holds.Treat the evidence chain as the finding’s proof of work. A finding you can trace back to its run, you can build on; one you cannot, you have to redo.
Validation states
Not everything written back is equally settled. Each artifact carries a state, so you always know how much to lean on it:- Validated: checked and trusted.
- Unvalidated: produced by work but not yet confirmed.
- To verify: flagged as needing a look before anyone relies on it.
Re-scanning knowledge
Work spreads across many tasks and sessions, and the useful result is easy to lose track of. Re-scan pulls findings out of past tasks and back into the hub, so when you remember “last week a run found the five metrics correlated with six-month retention,” you can recover it without hunting through a hundred open tabs.How knowledge compounds
This is the payoff of the whole module. Because Agent Studio runs agents in parallel, a single effort can launch dozens of investigations at once, and each one produces knowledge. Fifty investigations become fifty findings. Your job shifts from doing every investigation to curating what the fleet produces: keep what matters, validate what is load-bearing, retire what was a dead end. Each kept finding is available to the next engineer and the next agent, which is how the system gets smarter about itself over time, instead of relearning the same things.Next steps
Best practices
How to curate what compounds without drowning in findings.
Overview
See how the hub closes the loop with the book and the bench.