# <Product> status as of <date>

Subtitle: the question this report answers, e.g. "Can it be promoted to production?"

| Field | Value |
|---|---|
| Date | <date> |
| Release measured | <tag and environment, with the timestamp of the engine or build> |
| Previous report | <date and its one-line verdict> |
| Last full regression | <date, version, result> |
| Business matrix in force | <name, version, count> |
| Tickets moved since last report | <count> |

## Verdict

One paragraph. Answer the question up front, then the fronts that moved and the fronts that did not, each with its ticket.

**Method.** Everything below was read live on <date>: which repositories, which APIs, which logs. Nothing was inferred from memory. Where a source was not observable, the report says so.

## What runs where

| Environment | Engine or service | Build or tag | Last activity | Note |
|---|---|---|---|---|

Three things that matter from this table, as bullets.

## What changed since <previous date>

| Repository | Commits | PRs merged | Distinct tickets | Detail |
|---|---|---|---|---|

Grouped by what it solves, as bullets with ticket numbers.

## Trail of earlier findings

| Finding (date) | Ticket | State today | In the measured release? |
|---|---|---|---|

## Notes on figures that changed

When a number differs from an earlier report, say which source moved and why, so the reader does not take a live-source change for an error.