From the source

How it works
- The talk account reports over 80% background workload and approximately five-minute median and twenty-minute 90th-percentile task latency. The sample has no calendar dates or task denominator.
- The separate operator post reports about 10 billion October tokens across thousands of tasks. It is not the same seven-day sample.
- The video-page screenshot does not verify the talk’s figures. They remain operator-reported, with no independently reproduced outcome.
- The architecture combines interactive questions and background research. No business improvement for Thrive or public Polymer implementation is established.
Workflow guide
Choose fixed research questions, monitored topics and companies. Approve access to notes, email, calendar context, financial and investment records, and public or partner sources.
Plan reusable retrieval and synthesis components in an isolated pilot. Treat Puck and Polymer as private architecture references, not downloadable software.
Use the same components to draft answers, topic updates and stored company briefs. Cite sources and separate confidential firm material from external research.
Keep traceable records for retrieval and draft generation. Check the fixed task set after source changes to detect silent regressions.
Have staff verify briefs and material alerts before external communication or investment decisions. Require separate scheduling approval. Publish nothing automatically.
Compare the pilot with manual research on the fixed tasks. Record acceptance, citation accuracy, review minutes, alert precision and cost per accepted brief separately from token use.