Real applications combine many places, transitions, bindings, and guards into nets with dozens of interacting components. The principles are the same — state lives in places, transitions move tokens atomically — but the net topology itself becomes the coordination mechanism.
This scraper net has 24 places and ~14 transitions coordinating proxy leasing, domain rate limiting, resource discovery, and deduplication. Every constraint — "a proxy is either available or leased," "a domain can have at most N concurrent fetches" — is a structural property of the net, not an application-level check.
See also
- Places & Tokens — where state lives
- Transitions — how state changes
- Bindings — how transitions select specific tokens
- Guards — conditions on whether a transition fires