Skip to content

0012 — Geometry colors on the wire

Status: Accepted Date: 2026-11-04 Supersedes: the “client themes per indicator” part of ADR-0007 Amended by: ADR-0026 (lines and histograms carry colors too)

ADR-0007 put fills, hbars and divlines on the format=series wire but dropped their colors, on the grounds that “the client themes per indicator”. ADR-0010 then implemented that theming in web/src/components/geometry.ts.

In practice the client-side themes drift from the server. The PNG renderer (src/renderer.rs) uses the colors each indicator sets, and the web heuristics guess them back from the indicator name and fill index: Cipher B colors are wrong when toggles such as wt_show=false change which fills are emitted, volume-profile tiers are a POC/value-area guess, divergence colors come from slope, and Ichimoku gets a TradingView-style green/red cloud while the PNG used a single blue. Separately, hlines (RSI 70/30, profile POC/VAH/VAL) are on the wire but the web chart never drew them.

  • The web chart should look like the PNG; the server’s colors are the source of truth.
  • Additive wire change: existing fields stay, older servers must still work with a newer web build.
  • One helper on the Rust side, no per-indicator color tables on the web.

Keep client theming and fix the heuristics. Needs every Rust palette change mirrored by hand and cannot know which optional fills were emitted.

Serialize the color of each fill, hbar, divline and hline (chosen).

Chosen option: serialize colors. Every item of fills, hbars, divlines and hlines in format=series gets a color field, a CSS string "rgba(r,g,b,a)" produced by a single helper from the RGBAColor the indicator set. divlines already carry dashed. A fill may also carry an optional color_below, used where y1 < y2 (color applies where y1 >= y2). It is omitted when absent, so existing fills behave as before. Ichimoku uses it for the TradingView cloud, green rgba(76,175,80,0.2) above and red rgba(239,83,80,0.2) below. The PNG renderer picks the color per bar and the web chart reuses its existing split-at-crossings polygons. lines and histogram are unchanged and still carry no color; the web keeps its palette rotation for them.

On the web, the wire color wins. geometry.ts validates it (an unparsable string would make a canvas silently keep its previous style) and falls back to the existing theme heuristics when it is absent, so a newer web build still works against an older server.

hlines are now drawn by the indicator draw callback as full-width 1px solid lines in the wire color, clipped to the pane, as the PNG renderer does. The server does not mark any hline as dashed, so none is.

Y-axis rule: hline levels do not feed the auto-scale, in any pane. The PNG renderer’s auto-range ignores hlines, and a level far from the data (CVD’s zero line, a distant volume-profile node) would squash the series or candles. The web therefore matches the PNG: hlines are drawn where they fall inside the visible range and are clipped otherwise. Oscillators that need their levels in view (RSI 70/30) get them from y_range.

  • Good: web overlay geometry matches the PNG, including toggled-off Cipher B fills; the Cipher B index and Kalman heuristics remain only as a fallback.
  • Good: RSI 70/30 and similar reference lines appear in the web chart.
  • Bad: payload grows by one short string per fill, hbar, divline and hline (volume profiles emit a few hundred hbars).
  • Bad: web and server share one more piece of the wire contract; the Zod schema and docs/reference/mcp.md must follow any change.