New Money tab beside Trends, fed by the portal's /admin/money-series
(hourly-cached server-side). One fetch at full range; period (30/90/all)
and spend-mode (cumulative/daily) toggles re-render client-side.
- Cumulative mode: three lines — Revenue (OC contributions, green),
Token spend (blue), OC balance (amber). NULL balance days render as a
gap (the OC API exposes only the CURRENT balance; history accrues from
daily snapshots from the deploy date onward — stated in the caption
and in the balance legend key).
- Daily mode: token spend per day as bars (spend-only; the other series
are cumulative and would need a second axis).
- Money ticks use the 1/2/5 x 10^k rule; tooltips reuse the shared
chart-tip helper (all three series listed per day).
- The caption is a deliberate exception to the no-caption chart rule:
the operator asked for the honest data-history limits in the UI.
- Harness: tests/money-chart-harness.js (axis invariants, gap handling,
daily bars, period slice, single-point balance).
One shared, hand-rolled helper (no library, no CDN) replaces the native
SVG <title> tooltips: charts stamp data-tip-host/data-tip-i on their data
elements and register their exact values from the data arrays; one
delegated pointer listener set serves every chart, so re-renders need no
re-binding and new charts (the upcoming finance chart) join chart-by-chart
by following the two-step contract documented in the helper. The box is a
fixed-position div with pointer-events:none, clamped inside the viewport
(no edge flicker, never intercepts clicks); touch shows on tap/drag and
hides on release. Harness: admin-panel-chart-harness.js (exact values,
gap handling, clamping, multi-series contract) run via check-page-js.sh.
The co-op's panels do not put text under the pills. Replace the long
state-reason caption (and the over-long pill tooltip) with a single short
pill (in_grace -> 'grace') whose tooltip is one short line, matching the
existing pill vocabulary.
The Members Status column now renders the portal's per-member 'state'
(active / in grace / awaiting / inactive) instead of the raw active flag, with
the portal's reason shown beneath the pill. The portal owns the state; the panel
only displays it. Non-active states keep the member's access.
The totals cards showed spend that silently mixed members and the co-op's own
operator accounts. /admin/overview now returns operator_spend and
operator_all_time_spend beside the totals, and each spend card names its scope
("members + co-op's own") and states the co-op's own share beneath it, so no
figure has to be guessed at.
The agents table rendered the raw team spend field and labelled it 'Spend (30 days)', but that field is cycle-only and resets at budget_reset_at — for the agent teams, the 1st of the month. On 1 November both bot accounts therefore displayed as zeroed. It now prefers the all-time figure the portal supplies, and the label says what it shows.
- Agent accounts render without the "agent:" prefix, since the section header already
says Agents. The full alias is still in the payload as `alias`.
- The admin/operator table now carries the same columns as the agents table — Account,
Type, Spend, Budget — with Type "admin" and Budget "—". Activated and Reset are gone:
neither applies to an account that is not a member and has no member budget cycle.
Bot and sandbox teams had real spend that the panel structurally could not show: they
have no member row, and the all-time query filtered to member:% teams. They now appear
in an "Agents" category beside Admin, fed by the portal's new `agents` list, with spend
and budget. Kept out of member counts and member aggregates — a collective expense,
like the operator accounts already were.
Read-only on the reporting path; the set-balance and set-credits write routes are
untouched.
Two more metrics on the same chart, from the portal's new energy_wh and co2e_g
daily columns.
- Energy in watt-hours, carbon in grams CO2e, both for the day shown.
- Continuous metrics use the 1/2/5 axis rule (not the integer rule reserved for
counts), so energy ticks read 500 Wh rather than being rounded to whole
people-style numbers.
- Labels carry units, so a reader never has to guess what the axis measures.
- Same measured-vs-estimated provenance as the data layer: GreenPT models use
facts fitted from their own impact API, everyone else a labelled proxy. The
docs page on estimation is still to be written; the factor table and its
sources are in metrics_snapshot.py.
Harness extended: one bar per measured day for each, no NaN in markup, and axis
labels matching ^[\d,]+(\.\d+)? (Wh|g)$ so a unit prefix or a forced integer
axis fails the build.
Nathan: the disclaimers are not necessary, especially now that reporting is in
place going forward — and then, on the status line under it: remove that too.
Gone from both apps: the explanatory note paragraph, its per-metric config
strings, the status line ("55 days - 2 not measured"), the now-orphaned CSS for
both, and the gaps counter that only fed the status line. The period toggles
still say what range is on screen, so no information is lost.
The harness assertions that described the status line are replaced by stronger
ones: the rendered chart must contain no caveat text at all, and the 30-day view
must still end at the most recent measured day.
Nathan: the members axis should be whole numbers, since it counts people. It
was drawing fractional ticks (19.17 people) because the 1.08 headroom factor
fed straight into the label math.
Ticks now come from a step, with the axis top set to step x 4, so labels land
on round numbers:
- counts (members, requests): whole numbers, rounded up to a half power of ten
(requests read 3,000, not 2,888). Never below 1, so a near-empty series still
gets an integer axis rather than fractions.
- money: the 1/2/5 x 10^k rule, so ticks read $10.00 rather than $4.92.
Rendered now: members 0 | 20 | 40 | 60 | 80; requests 0 | 3,000 | 6,000 |
9,000 | 12,000; spend $0.00 | $10.00 | $20.00 | $30.00 | $40.00.
The node harness gained assertions for this, checked geometrically (tick values
ascend while their screen positions descend, the zero tick sits lowest, ticks
are evenly spaced) rather than assuming a text order, so a fractional
people-axis or a misplaced label fails before a deploy.
Nathan asked to see a chart. The portal now owns a daily metrics series
(metrics_daily, written 03:15 UTC by the portal's own scheduler); this is the
first surface to read it.
- New route /api/metrics proxies the portal's /admin/metrics/series (admin
token stays server-side, same pattern as /api/model-usage).
- New Trends tab, added to switchView in the same edit (every view toggled
there must be shown/hidden there). Lazy: the series loads on first visit, so
the panel's initial load is unchanged.
- Metric toggle (Members / Spend / Requests) and period toggle (30 / 90 / all
time). Fetched once at the widest range and re-rendered client-side, so the
toggles never refetch.
- Inline SVG, hand-rolled: no chart library, no CDN, no external dependency.
Colours come from the panel's existing CSS vars, so it matches the rest.
- Gaps are drawn as gaps. A NULL metric means "not measured" and the line
deliberately breaks rather than drawing through a day we never recorded
(backfilled members_active is NULL every day, by design). The sub-line says
how many days are unmeasured.
- Members shows the cumulative total; spend and requests are per-day bars.
Verified against the live 55-day series with a node harness running the real
page functions: 22 checks, including that a NULL breaks the line into two runs,
that no NaN reaches the markup, that the toggles do not refetch, and that the
SVG carries no hardcoded hex.
No manifest change yet — proxyAuth stays active, so get_identity() still works
via header. OIDC routes only activate when CLOUDRON_OIDC_* env vars are present.
Validates id_token signature (JWKS), iss/aud/nonce, exp/nbf.