Module render

Expand description

2026-09-28: The stable text rendering of a plan: the golden files under kernels/circuits/plans/ and met circuit show.

Owner: metrale-circuit. Invariants:

The text is a pure function of its inputs, ASCII only, one group per line, with no widths that depend on terminal size, so a diff of two renderings is a diff of plans.
Every in-plan edge appears exactly once: as a fused edge of the group it lives in, as a written output of the group that stores it, or as a plan input.

Structs§

Notes: 2026-10-02: What a rendering adds to a plan: compute=<group> on each group line (the compute unit its kernels run on, venn::compute), and under it one line per member node (its pipeline, crate::pipeline).

render: 2026-09-28: Render plan of circuit.
render_noted: 2026-10-02: render, with notes.group(group) appended to each group’s line as compute=<note> where it answers, and under it <node>: <notes.node(node)> for each member node where that answers.
route_section: 2026-09-30: A runtime route’s arm, rendered after the primary plan: a heading that names the route, its condition and the settings it plans as, then the arm’s plan under header. 2026-10-02: With notes (render_noted).
with_settings: 2026-09-30: header with its settings line rebuilt from policy (after a device class re-reads its settings, or for a runtime route’s arm).

Header: 2026-09-28: key: value lines printed under the title, in order (recipe, checkpoint, policy). The caller decides what they say; the renderer only prints them.