Repository navigation
feat(dashboard): dashboard from the October 2026 redesign (#901) - #926
Merged
Merged
Conversation
The redesigned dashboard quotes a worst plausible year (P95) beside the annualised exposure. The Monte Carlo already sorts its samples, so P95 is one more percentile read off them, added to the risk and portfolio distributions and to their currency-aware presentation. No input, sampling or seed changes. Signed-off-by: alex-dembele <alexandredembele16@gmail.com>
The tenant score is computed live and nothing kept its past values, so the redesigned dashboard had no way to draw its 12-month line or say how far the score moved in 30 days. - tenant_score_snapshots (migration 0069): one row per tenant per UTC day, a later computation on the same day replaces it. Unmeasured days store nothing and show as gaps, never as zero. - GET /score/history?months=12: the month-by-month closing value, today's value and the 30-day delta (null until a snapshot is 30 days old). It records today first, so the line always ends on the live figure. - A sweep records every tenant every six hours, so a quiet tenant's line stays continuous. The formula is untouched; this stores what /score already returns. Session-sufficient like /score, declared in the authz and isolation registries with its cross-tenant tests. Signed-off-by: alex-dembele <alexandredembele16@gmail.com>
The redesigned dashboard counts the risks still alive, which the stock counters cannot answer because they include closed risks so they reconcile with the full register. /stats gains four fields, the existing ones are unchanged: - live_risks: not closed - critical_live: critical band, still open or in treatment - without_mitigation: live risks with no plan other than cancelled ones, matched on the risk's own tenant - reviews_due_30d: next review within 30 days, overdue included Signed-off-by: alex-dembele <alexandredembele16@gmail.com>
…901) One layout for every member: the open critical or high incident with its running time and the way into its war room, the exposure score with its four factors and 30-day movement, the annualised exposure split by band with the residual and the simulated P95, four counters, the score over twelve months beside the 5x5 matrix, then the top priorities and the recent activity. The business role picks which four counters and which priorities show (RSSI, risk manager, auditor, executive), as the design's four views do; there is no switch on screen, per the owner. Each block fetches its own tenant-scoped source and renders its own loading, error and empty state. The score keeps its exposure direction (owner decision): it is labelled "Score d'exposition", a falling value shows green, factor bars are pressures coloured from the served band table, no threshold in the client. The matrix tint is a grid legend; the binning is the server's CEIL(p x 5), CEIL(i / 2). The period control is gone: no block of the redesigned page is period-scoped, so it would filter nothing. The five persona dashboards, the action-center panel and their helpers are removed; the panel's link safety (no unresolved or off-origin row) now guards the priority list, with its tests ported. The register opens on its matrix with ?view=matrix, which the dashboard links to. Signed-off-by: alex-dembele <alexandredembele16@gmail.com>
This was referenced Oct 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Second screen of the redesign epic (#899). Stacked on #925 (the shell): the base is
feat/900-console-shell, so this diff shows only the dashboard. Retarget tomasteronce #925 is merged.What the page does
One layout for every member, as drawn: the open critical or high incident with its running time and a link into its war room, the exposure score with its four factors and 30-day movement, the annualised exposure split by band with the residual and the simulated P95, four counters, the score over twelve months next to the 5x5 matrix, then the top priorities and the recent activity.
The business role picks which four counters and which priorities show, which is how the design's RSSI / risk manager / auditor / executive views map onto real accounts. There is no switch on screen (owner decision).
Backend added for it
GET /score/history?months=12andtenant_score_snapshots(migration 0069): the tenant score had no stored past, so there was nothing to draw a year with. One snapshot per tenant per day, written by the endpoint and by a six-hourly sweep. Declared in the authz and isolation registries, with cross-tenant tests at the repository and use-case level./statsgainslive_risks,critical_live,without_mitigation,reviews_due_30d. Existing fields are unchanged; a test covers the closed / cancelled-plan / foreign-tenant-plan cases.Choices worth a look
/score/model's own bands.Verified
go test ./...: all packages pass, including the authz and isolation route ratchets.npx tsc -b --noEmitclean,npx vitest run110 files / 1000 tests passed, lint ceiling lowered to 96./score/historyread back from Postgres, column types identical between the SQL migration and AutoMigrate, 414 px without horizontal overflow, axe onmainwith 0 serious or critical issues in both themes.Not done here
Closes #901