OpenProse · Run Traces
Topology encodes causality. Line weight encodes intensity. Node type encodes role. Orchestrators, scouts, evaluation gates — drawn at the dispatch level, then drawn again at the verdict.
d3-force · canonical run An agent run is a directed graph of delegations. So we draw the graph — only this time, with a real chart library. The figure beside this sentence is a tiny canonical run laid out by d3-force: eight nodes (one orchestrator, three scouts, one synthesizer, two evals, one terminal) settle under charge-repulsion and link-attraction. The same five-shape vocabulary closes every diagram on the page. The figure is still the trace. Across the fleet, the harness dispatches — orchestrators , — scouts , — evaluation gates , and one synthesizer per run, reconverging on a single terminal verdict . Each run below uses its own connection pattern. Read horizontally: the same eval diamonds close every run.
Sankey shows the shape of a run; the radar shows the shape of its eval. The cross-section shows the shape of the fleet's evals — every dimension across every run, on one shared scale. Row means tell you which run was strongest overall; column means tell you which dimension the harness reliably nails and which it struggles with. Cells below 75 trip the amber threshold.
The vocabulary is small and bears all the meaning. Shape is the noun, colour is the role, weight is the verb.
Every glyph below is rendered by the same drawShape() call the sankey nodes use, and every weight is read off the same W constant the link ribbons use. Legend and chart can't drift — they share the source.
drawShape(g, {type})linkColor(kind)W + TOPOLOGIESdata/syntax-charted.js. Charts by d3@7 + d3-sankey@0.12.3 over the shared drawShape() vocabulary. Visual grammar after Oliver Byrne's Elements of Euclid (1847), Feynman diagrams, and Edward Tufte, Beautiful Evidence (small multiples, p. 47; heatmap-as-cross-section, p. 110). Layout is data, paint is library.