Story: Account for the grid's usage
Table of Contents
This page documents a story in Sprint 29, carried unfinished from Sprint 28 at close. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
The grid's global view answers which tenant is using what, from what the installation observed about its own operation. No policy is widened, no cross-tenant read is added, and no tenant's content leaves its tenant.
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 29 |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-11-08 |
3. Acceptance
The story closes on the tasks it finished:
- Reconcile the grid stories with the code.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Reconcile the grid stories with the code | BACKLOG | Compare the grid stories and backlog captures with what the code does, and correct the paperwork. |
5. Decisions
- 2026-10-21: The counts of work per tenant and party are served by entering each tenant (9ff9426cab) after the system tenant's read of every tenant's grid work was removed (7cebe734ac). This met the first question, who uses the grid, without a ledger of usage rows. The second question, how much compute a tenant used over a window, still needs the run statistics of Draw the node heatmap and carry the engine run statistics. The usage row of the first task is open until that story decides whether the statistics on the result replace it.
- Closed on 2026-11-08 at sprint 29 close with its done tasks. The open tasks and the original acceptance moved to Account for the grid's usage — the remaining work.