nordisk/facett

facett-cfd — crate card

Reverse-engineered (from source — verify, don't trust the name)

• One-line pitch: A pure-egui Cumulative Flow Diagram facet: stacked status areas over time.
• Does: Draws Bands (one per status, bottom→top) as stacked areas across a series of daily Snapshots — band widths show case counts per status (a widening band = growing bottleneck), the top slope is throughput, horizontal distance across bands approximates cycle time. Fed by the daily status snapshots the event log makes free. Cfd follows the facett Facet contract (title/ui/state_json). Deterministic.
• Key deps: egui, chrono, serde/serde_json. Optional facett feature.
• Shape: lib, ~227 LOC single lib.rs (Band, Snapshot, Cfd).
• Observed role in the workspace: Standalone flow-report widget, no in-repo consumer yet. Built in ordning; destined for facett.

Fill in (one line each — only the human knows these)

• Primary consumer(s):
• Why it exists (vs the obvious alternative):
• Hard constraint (airgap / no-C-deps / no-FFI / pure-Rust / etc.):
• Release cadence & independence (rides a parent? own repo someday?):
• Status (production / prototype / experimental / stubbed):
• Must-NOT-change invariant:
• Biggest known gap or TODO:
• Anything a newcomer would get wrong about it: