pub struct LayoutBinding {Show 14 fields
pub nodes: usize,
pub edges: usize,
pub traversal_edges: usize,
pub shortcut_edges: usize,
pub one_way_edges: usize,
pub gated_edges: usize,
pub carry_edges: usize,
pub stations: usize,
pub gate_stations: usize,
pub beats: usize,
pub spine_beats: usize,
pub path_steps: usize,
pub brief_facts: usize,
pub plan: PlanBinding,
}Expand description
What a run’s map-pipeline checks bound to — stages 2, 3 and 4.
Stated on every run whether or not anything was found, because a count only means something when the run that found nothing prints it too (CLAUDE.md). It is one struct with one constructor, so the number the CLI prints, the number the build ledger records and the number a diagnostic quotes cannot disagree.
One ledger for three documents rather than one per document, and that is the point: a site plan’s boxes are counted beside the graph’s places, so a run that embeds five of six places states both numbers on one line and the mismatch is visible without arithmetic.
Fields§
§nodes: usizePlaces declared — what DW0816 examines.
edges: usizeConnections declared.
traversal_edges: usizeOf those, connections a body passes along.
shortcut_edges: usizeOf those, connections marked as closing a loop — what DW0820 examines.
one_way_edges: usizeConnections a body passes one way only — what DW0819 examines.
gated_edges: usizeConnections that demand something before a body may pass.
carry_edges: usizeConnections a body is carried over rather than walks (spec-0083 §7) —
what DW0934 matches against the campaign’s links.
stations: usizeNamed places inside places — stations declared across the whole graph (spec-0052 §4).
A station no quest references is legal mid-authoring, so this is the denominator rather than a count of what is used, and a zero is stated like every other: a site-plan campaign with no stations names its places at node granularity, which is a fact about that campaign and not a silence.
gate_stations: usizeOf those, stations declared as a gate — the ones open-gate,
close-gate, a shortcut and a timed-gate may address. The remainder
are points, which is what every other consumer resolves.
beats: usizeQuest beats bound to a place.
spine_beats: usizeOf those, beats on the mandatory quest spine — the number DW0817’s
obligation to visit them actually quantifies over.
It is carried separately because beats is not the binding: a graph can
declare a dozen beats and still ask DW0817 to check nothing, if none of
their quests is one the finale depends on. A zero here is the graph
before mission case and is reported as a finding.
path_steps: usizeSteps of the authored critical path — what DW0817 and DW0822
examine.
brief_facts: usizeFacts the geometry brief states — what a site plan’s identities bind to.
plan: PlanBindingWhat the site plan offers the stage-4 checks.