Open routing diagrams of reactive polynomial machines #
A diagram contains typed components and routes without selecting a global environment. Parallel composition and wiring preserve the components themselves. Boundary maps translate only external traffic, and wiring resolves an outgoing shared-boundary packet to the receiving component's ingress. Every component retains its own polynomial effect and private state.
The designated environment and execution policy are supplied when a diagram is run. In particular, composing two fragments does not choose two competing recipients of yielded control. Boundary functions are structural semantic data; their executable cost is a separate obligation.
Typed open components and their internal and external packet routes.
- effect : Node → PFunctor.{0, 0}
Each component's declared local operations.
- ports : Node → PortBoundary
Each component's incoming and outgoing packet types.
- component (id : Node) : ReactiveProcess.Process (self.effect id) (self.ports id) Unit result
Initialized component machines with private state carriers.
- route (id : Node) : (self.ports id).Out.Packet → (target : Node) × (self.ports target).In.Packet ⊕ boundary.Out.Packet
Internal recipients or exposed outputs for every component send.
Component recipients of exposed input packets.
Instances For
Diagrams agree when their interfaces, initialized machines, and typed routes agree.
Relabel components and dependent packet recipients along an identity bijection.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Place one initialized reactive machine at a single node.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Adapt the external boundary without changing component interfaces or private states.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Parallel composition uses disjoint node identities and retains both external boundaries.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Wire a shared boundary directly to the other fragment's ingress. Sends still consume their ordinary local and delivery activations; no component or shared service is copied.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Close two opposite boundaries while retaining the identities of every component.
Equations
- One or more equations did not get rendered due to their size.