Pipeline watch — NW-PROJ-12 Checkout rebuild · 11 September 2026
Produced by: Run EXAMPLE-PW-01 · read-only · document on the project's watch ticket · demo values
- Needs a person
- 5 things, worst first, each naming the ticket it came from. NW-201 is first because it waits on NW-205, which nobody has touched for 216 counted weekday hours — the row is graded on the blocker, because the blocker is what somebody has to go and unstick. NW-210 had its last blocker finish and has not moved in 144 hours; nothing in the product tells anyone when a final blocker closes. NW-225 was commented on an hour ago and has sat in its column for 192 hours, which is the row that reads as healthy until somebody asks when it ships.
- What was checked
- At least 8 pieces of work on this project, of which at least 2 open ones raised nothing at all and are simply moving. "At least", because 1 ticket is owned by a team this reader is not in: it is counted here and named nowhere. 1 dependency could not be looked at for the same reason, so no claim is made about what that work is waiting on. Stale means 72 counted weekday hours here — the same rule the rest of Aestus grades a waiting ticket by — and the digest prints whose ladder that is. A bar chart puts the quiet count beside the four problems, which is the whole shape of the morning in one glance.
- What this watch cannot see
- Printed in every digest, because this one is named after a report people run in a CRM. No CRM is connected to Aestus, so nothing here comes from one. This watch reads the work on your own board: there is no deal, no amount, no pipeline value, no owner quota and no logged customer contact anywhere in this digest, and a line that looked like one would be invented. A ticket in Aestus records no due date, so this watch can never say a date moved or a date was missed. What it can say is how long something has gone without anybody touching it, and how long it has sat where it is — both judged on the same ladder the rest of the product uses.
- Checked and clear
- The checks that ran and raised nothing, named one by one. On this morning all four raised something, so this section is empty and says so — a class that raised a row is never also reported as clear.
- Sources
- One numbered row per ticket behind the lines above. Every count in the digest was computed before the model was asked to write anything, a review step checks the written digest back against them, and the numbers as code computed them are recorded on the run so the two can be compared.