The pack, at four cadences
Every report is built when you open it, from the same resolver the dashboard uses, scoped to Vu Tuan Minh (CEO). A report is a view, not a store — the moment it becomes a saved copy of the numbers, it is another place for a second NPL figure to live, which is the problem this programme exists to end.
Each one ends with what it cannot tell you, computed from your own scope rather than written once as boilerplate.
Today’s memo → What actually changed in twenty-four hours: alerts, deliveries, approvals, campaign days and the one metric in the registry with a genuinely daily series. It does not compare 140 metrics to yesterday, because 139 of them did not move — see the memo’s own standing line, and Q-32.
Weekly
Exceptions and feeds. Most metrics will not have moved — the series are monthlyMonthly
The pack. One reported point per metric, so this is the natural cadence of this registryQuarterly
Three points per metric — the first cadence where a trend claim is defensibleYearly
Twelve points. Restatements matter here, and the report names themEvery report offers CSV for its tables and a print view for the document. There is deliberately no PDF button: shipping a headless browser into a prototype to produce a binary nobody will diff buys nothing that print-to-PDF does not already give you (A-67). Every download is watermarked with the reader, their scope and the time, and writes an audit event — export is a permission (R-S-08), and the rule that grants it is a rule in the access table.