See which product logic changed, compare results with intent and inspect the version of Intelligence used without reading every underlying file.
Four things a person can read without opening a file: what changed in the product since your last visit, a build-by-build account of what it started or stopped doing, what each closed task promised set against what actually changed, and the places the product itself says are worth a look — a state nothing leaves, an event nothing listens for, one concept living in two areas at once.
Open a project and read the summary for your last visit, a day, or a week.
Open a repository and compare two builds.
Open Work and read the closed items against what they promised.
Read the attention list and decide what to act on.
This watches the product, not the agents: no transcript, no per-agent feed, no alerting. History compares builds, not commits — several pushes in a row are folded into one rebuild, so a change between two builds is what you see. The attention list is derived from what was read in the code, so it knows nothing about an outage, a slow query or a customer complaint.
Three models are published in full and open without an account. Ask one of them the question this page is about.