The digest format Shipped
High Signal, Interesting, Worth Watching — with a hard item cap, because an uncapped digest is a feed.
The cap is the design. A digest that returns everything relevant has not filtered anything, and the reader does the work the team was supposed to do. Roughly twelve items across three named tiers, each cited, each with a concrete angle rather than a summary — the angle is the part a human cannot generate quickly from a headline.
Two contracts it applies and never edits
An interest profile (explicit track and exclude lists) and a digest format carried over verbatim from a reference run. Both are supplied by you and fixed at runtime. That is what makes the output comparable week to week — and it is also what the improve loop learned the hard way, when a prose instruction about recency kept getting overridden until it was moved into fixed doctrine.
Its five specialists are lenses, not workers
interest-filter, source-verifier, digest-shaper, angle-smith and recency-caller are not separately dispatched — they are the lenses a single authoring agent has to satisfy, and the specialist files say so in as many words. Useful precedent: a team's roster describes its standards, not necessarily its process topology.