Concepts/Definition

Application context: a design graph and a runtime graph answer different questions

A code-review team may be designed around an accountable lead, several scanning workers, an independent reviewer, and a final adjudicator. In a workflow framework, that design may reduce to routing, parallel nodes, a gather step, and a conditional loop. If only the runtime graph survives, the team later cannot explain which edge represented delegation, who owned the final verdict, or who had to close a failure.

Definition

Topology Lowering compiles high-level collaboration designs such as hierarchical delegation, adversarial review, and hand-off chains into serial, parallel, routing, and loop primitives supported by the runtime. The representation changes; role, responsibility, authority, and acceptance semantics do not disappear.

Engineering mechanism

The design node records pattern, role, owner, authority, and acceptance. Runtime nodes retain references to those fields, and traces identify the design decision from which each node was lowered. A hierarchy can therefore execute as route, parallel workers, and gather while the lead and workers retain different authority. An adversarial review can execute as a conditional loop without collapsing generation, review, and adjudication into one role.

Boundary

Use lowering when the runtime vocabulary is smaller than the design language. It does not prove that every collaboration pattern is merely one of three low-level edge types. The same graph can carry different responsibility structures, so review the design graph, compilation mapping, and runtime evidence together.