nordisk/facett

facett-log — crate card

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

• One-line pitch: A generic timestamped event-log / console pane: a bounded ring of kind-coloured rows, themed, factored out of nornir's action-log overlay.
• Does: LogView keeps a bounded ring (DEFAULT_CAP 256) of Entry (seq, stamp, kind, detail) painted as kind-coloured rows in a scroll area. The Kind enum is a small greppable vocabulary matching nornir's action_log::Kind. The host owns all sinks (file/warehouse/stderr) and feeds entries via push; this crate keeps NO I/O, no clock, no threads — the timestamp is a string the host stamps (FC-7: injected time). Canonical Facet: local()/remote()/state_json()/caps()/set_title.
• Key deps: facett-core (Facet, theme), egui, serde/serde_json. Dev: egui_kittest.
• Shape: lib, single module (~381 lines). Key types: Kind, Entry, LogView.
• Observed role in the workspace: The reusable UI half of nornir's action log; a host attaches its own durable sinks and pushes entries.

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: