Skip to content

feat(reports): close the report granularity vocabulary #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lessevv merged 1 commit into from
Jul 29, 2026
Merged

feat(reports): close the report granularity vocabulary #6

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions 10-functional/features/c-insight/c7-reports.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,18 @@ to monthly to quarterly — up to a maximum point count. It never silently
truncates the range, because a chart showing half the period the user asked for
is worse than a coarser chart showing all of it.

The granularity the user chooses is monthly or weekly, and nothing else.
Quarterly is a widening outcome the generator reaches on its own; it is never a
value the user picks and never one a saved report holds, so it is not part of
the vocabulary. A stored granularity outside the set is a defect rather than a
new case to handle, so the set is named once and the code is held to it.

The series cadence in [C2](c2-recurring.md) and the digest cadence in
[C8](c8-notifications.md) also say `weekly`. All three are separate
vocabularies that happen to share a word and a value, and none of them may
share a type — a report is not on a cadence, and widening its buckets has
nothing to do with how often a series recurs or how often a digest is sent.

### Currency modes are explicit

In base mode, values convert and merge, and rows with no available rate are
Expand Down Expand Up @@ -124,10 +136,13 @@ that would accept ambiguous input. An inverted range is rejected.
| **C7-R18** | Every write action MUST guard ownership explicitly and MUST return not-found for a report the caller does not own. |
| **C7-R19** | A chart segment MUST drill through to the transactions behind it, carrying the report's filters. |
| **C7-R20** | Custom ranges MUST be parsed strictly, and an inverted range MUST be rejected. |
| **C7-R21** | The report granularity vocabulary MUST be closed to monthly and weekly; it MUST be expressed as one named type rather than as free strings, a stored value outside the set MUST be rejected rather than defaulted, and the type MUST NOT be shared with the series cadence of C2 or the digest cadence of C8. |

## Related

- [B7 Split transactions](../b-ledger/b7-splits.md) — why aggregation is split-aware
- [B9 Full-text search](../b-ledger/b9-search.md) — the drill-through target
- [B10 Multi-currency](../b-ledger/b10-multi-currency.md) — the currency modes
- [C1 Dashboard](c1-dashboard.md) — pinned cards
- [C2 Recurring detection](c2-recurring.md) — the series cadence, a separate vocabulary that also says weekly
- [C8 Notifications](c8-notifications.md) — the digest cadence, the third one
Loading