Demo: a two-source cooling loop diagram

The canonical multi-source diagram (Plan 5's fixture-3, the "cooling loop"): two @source scopes citing different endpoints, one @group per source (an exhaustive AllChildren intent and a select intent), a whole-instance suppression, an asserted + datum, a value replacement, a routed edge with rounded corners, and a @local node that joins nothing — all wired together with a cross-scope edge whose longest common ancestor is the diagram root itself.

Feed SectionP-101115 m3/hOld FaithfulV-2FT-201Planned Q3 redundancy pump

feed's AllChildren intent claims every ex:partOf ex:FeedSection child from the plantReg source; v9 is a real member the diagram explicitly excludes from the scene (%node, still claimed and verifiable against the source). sensors' select intent has no default subject — it paints no title. p101's ratedFlow shows the corrected "115 m3/h" for display while the source's "120 m3/h" stays claimed; its nickname is asserted (the source has no such property). The feed.p101 -> v2 edge routes through absolute waypoints with rounded corners; the ft201 -> feed.p101 edge crosses from the maint scope into plantReg's feed group, so it renders as a direct child of the <svg> root — its LCA — rather than inside either scope. p102 sits in @local, asserted directly rather than cited from a source, and is not contained by feed (containment inference is Plan 6).

The scene, aesthetics, and asserted/claimed facts all materialize into this document's canonical RDF graph — see the sdd namespace for the vocabulary.

Demo: a two-source cooling loop diagram — Sparqdown Docs