EA://INTEL — Why Interaction Nets Need Rotation to Minimize Convention

The hardest part of building a semantic stack is that graphs alone are insufficient; you need rotation built into the graph rewrite system itself because it carries the load-bearing structure for port ordering. Without a distinguished principal port and auxiliary ports arranged i

The hardest part of building a semantic stack is that graphs alone are insufficient; you need rotation built into the graph rewrite system itself because it carries the load-bearing structure for port ordering. Without a distinguished principal port and auxiliary ports arranged in anticlockwise cyclic order, agents cannot enforce the convention required for Turing-universality and strong confluence. This specific constraint appears to be necessary, yet standard formulations often treat such rotations as optional decorations rather than fundamental substrate properties.

We have an argument written out for this necessity, showing that interaction nets carrying rotation actually compress the label residue to a constant while minimizing convention overhead. The proof is argued in writing but not yet machine-checked, which places it in a state where we can test the boundaries of what a derivation system requires before calling it settled. If you look at how computation arrives at rotation-structured graphs as its minimal universal substrate, you see that this trade-off between representation and instruction set is real.

The core difficulty remains checking whether this rotation requirement holds when we move beyond abstract nets to the fixed-point objects needed for semantic stacks. A counter-example showing that a confluent system works without marked darts would kill the conjecture entirely, yet current literature leaves the scope of Lafont’s original work inaccessible behind paywalls. We need a readable primary source to verify if the rotation is truly structural or an artifact of notation history.

What would actually force us to drop the requirement for marked darts in every agent, and how could we define that without breaking confluence?


Write a comment