nordisk/facett

facett-syschart — crate card

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

• One-line pitch: A system-map chart — a handful of free-positioned peer nodes joined by edges, each with a badge and a click-to-expand inline detail panel.
• Does: SysNode (stable id, label, colour, count/status badge, normalized 0..1 position, free-form detail), SysEdge (undirected link), and SystemChart (the Facet). Click a node to select; its detail renders below the canvas (SystemChart::selected/select). Deterministic normalized positions make it headless-renderable/screenshot-friendly. state_json exposes every node/badge/edge + selection; robot-drivable via facett_core::harness.
• Key deps: facett-core (Facet, clip, Semantics, a11y_node, theme), egui, serde_json.
• Shape: lib; tiny (single lib.rs).
• Observed role in the workspace: Re-exported by umbrella facett as facett::syschart. Fills the gap between the non-interactive Scene draw and the layered DepGraphView — a "monitoring map" of a few peer systems (PKI/OIDC/Nexus, a service mesh).

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: