How work gets routed
Niyatna sends each request down the right path — a person, an agent, a tool, or a review step.
Every request you make has a best path. Niyatna picks it for you, so you do not have to think about which tool, model, or person should handle what.
Routing is not just choosing a model. It is the decision about whether a job should go to you for a call, to an agent, to a quick tool, to a stronger reasoner, or to a step that waits for approval.
What it looks at
When choosing a path, Niyatna weighs:
- what you actually asked for;
- who is allowed to do it;
- how sensitive the attached information is;
- which tools the job needs;
- how fast and how cheap it needs to be;
- how much proof is required;
- whether it needs review before it is finished.
Where a request can go
A request might be routed to:
- you, if it needs a human decision;
- an agent working with you;
- a simple, low-risk automation;
- a stronger reasoner for a hard problem;
- a tool that only reads;
- a prepared action that waits for your approval.
The request stays put
The path can change — a job might start simple and need a stronger reasoner later — but what you asked for does not. Niyatna keeps your request, your acceptance criteria, and the proof you need as the fixed point, and routes the work around them.
Why it matters
You want your company to move fast without losing control. Routing is how Niyatna gives you that speed while keeping your limits, your proof, and your final say intact.