Categories and routing

Every task moves through the same steps: triage, then expansion, then execution. At each step tendant routes the task, either to an agent or to you.

Eligibility

Each agent declares the tasks it may take. For example, it might accept only tasks below a certain stakes score, or only tasks that need a capability it has. Tendant drops the agents that don’t qualify, then a model picks one of the rest. If no agent qualifies, the step comes to you.

Category bindings

Triage gives each task a category, such as communication/email. A category can bind a step to specific agents. It can also add a filter that applies only to that category. For example, the built-in communication/email category sends execution to the email specialist, but only when stakes are 6 or lower. Subcategories inherit their parent’s bindings unless they set their own.

Bindings fail closed

When a binding applies to a step, it decides which agents are allowed. If its filter rules out every bound agent, the step comes to you. Tendant does not fall back to the agents that qualify on eligibility alone. A high-stakes email is never handed to a general agent just because the email specialist was excluded.

The assignment tells you why it came to you. It says which category binding excluded which agent, for example:

category binding “communication/email” excluded all execution agents (email-specialist: stakes 9 > 6)

The same reason is recorded in the task’s activity timeline.

Eligibility alone is used only when no binding covers the step. That happens when a task has no category, during triage itself, or when neither the category nor any of its parents binds that step.