Purpose
Definitions others can open, read, and maintain.
The standard
Canvas hygiene: left-to-right flow, groups with titles per stage (Inputs → Geometry → Analysis → Outputs), scribbles for intent, no wires crossing more than necessary.
Inputs at the far left as named parameters; outputs baked via a single, clearly marked bake group with target layers per 10.02.
Data trees documented at each stage boundary (a panel noting
{grid;floor}structure).Plugins: only those in 10.01's approved list. A definition needing another plugin lists it in a note at the top-left and gets approval first.
Script components (Python/C#) contain only glue; real logic lives in an importable module (10.03).
Versioned in git alongside a screenshot of the canvas; file named per 01.05; Rhino file with test inputs saved next to it.
Performance: profiler on before delivery; nothing over
[TEAM: 5 s]recompute without a "compute" toggle.
Anti-patterns
Everything in one group; magic numbers in sliders without labels; internalized geometry as the only input.
Owner: [TEAM] · Last reviewed: 2026-09