What changes when agent routing is fully deterministic?
I’ve been exploring what happens if you treat agent routing as a deterministic
problem instead of a dynamic or heuristic one.
I built a small routing runtime (IntentusNet v1.0.0) that is intentionally limited:
- synchronous execution
- explicit routing strategies (direct, fallback, broadcast, parallel)
- deterministic agent ordering
- no retries, no workflows, no scheduling
It’s useful only when multiple handlers can satisfy the same intent and the
fallback path needs to be predictable.
Code and documentation:
https://github.com/Balchandar/intentusnet
I’d appreciate feedback on where this approach breaks down or isn’t worth
the trade-off.
I built a small routing runtime (IntentusNet v1.0.0) that is intentionally limited: - synchronous execution - explicit routing strategies (direct, fallback, broadcast, parallel) - deterministic agent ordering - no retries, no workflows, no scheduling
It’s useful only when multiple handlers can satisfy the same intent and the fallback path needs to be predictable.
Code and documentation: https://github.com/Balchandar/intentusnet
I’d appreciate feedback on where this approach breaks down or isn’t worth the trade-off.