Agent stack build plans · № 3 · part 1
What you get
One message in Telegram every morning. The mock below is the target — build nothing until this shape looks worth waking up to.
The deliverable is a dated markdown report, rendered into your chat. Three design decisions make it an intern rather than a search-results firehose: every claim carries a source link; a “new since yesterday” section is computed against the archive, not vibes; and a skipped line proves the dedupe is working — silence about repeats is indistinguishable from a broken memory.
New since yesterday
- ▲ Toyota’s Q2 investor deck (PDF, 84 pp) moves the sulfide-electrolyte pilot line date from “2027” to “H1 2027” — first time a half is named. — investor PDF, p. 31 · via
pdf-deckskill - ▲ New arXiv preprint claims 4.2 mA/cm² critical current density at 45 °C in an argyrodite cell — above the 3 mA/cm² line most reviews treat as the fast-charge bar. — arXiv:2607.11xxx
- ↻ Follow-up: the Korean ministry grant list covered on 18 Jul now has amounts attached — the CSV puts the solid-state share at ₩142B of ₩310B. — ministry CSV · via
krg-csvskill
Steady state
- No new SEC filings from the three US-listed pure plays; QuantumScape’s next scheduled report is 29 Jul. — EDGAR
Housekeeping
Everything above is static example data — the dates, numbers and links are illustrative, not research.
Why each part earns its place
- The diff section is the product. Day one, everything is new. Day thirty, a good morning is two bullets and a skipped-count of nine. An intern that can say “nothing happened” in one line is worth more than one that pads.
- Scraper-skill credits (
via pdf-deck skill) show you which items came through the intern’s self-written tooling — so when a skill rots, you notice which coverage went dark. - The housekeeping line is your invoice. Portal tool calls are metered; printing the count in every report is how a daily cron stays a known cost instead of a surprise one.
- Saved to
reports/— the file is the archive. Tomorrow’s run greps it before writing a word. That directory is a convention you set up, not a Hermes feature; the architecture page is honest about which is which.
This mock is also the plan’s shareable artifact: in the final prompt stage you’ll have the intern render a real report to HTML and share it for human review before you let the cron run unattended.