Complexity Router

Who the node is. The id is the key the DOT pins.

id

complexity-router

name

Complexity Router

type

decision

phases

none declared

What it does, and the prose the agent is handed when the graph runs.

action27 words

Decide whether the question in front of you needs the capable model or the fast one, and put that decision where a downstream fork can read it.

spec148 words

Read the question as it arrived and decide which of simple or deep describes the work it needs. simple means the answer is a lookup, a restatement, a short factual recall or a single step of arithmetic. deep means anything that needs more than one step held in mind at once, a judgement between competing readings, or work whose first plausible answer is often wrong. When you are not sure, say deep: the cost of the wrong call in that direction is money, and in the other direction it is a wrong answer. Emit the question unchanged on routed, payload untouched, and record the tier in your status file as well: put tier in context_updates, set to the value you picked, so the fork downstream can branch on context.tier. A run that leaves that key unwritten reads back as the empty string, and no tier name matches it.in full above

model

whatever the graph supplies

agent

Router

skill

not named

tools

none

mcp

none

params

tiers: ["simple","deep"], default_tier: deep

What arrives, what leaves, which nodes it expects to hear from, and what may not.

inputs

question : text

outputs

routed : text

dependencies

question-intake

cannot

no type is refused

will_not

change the question it routes, answer the question itself

The keys the static analysis reads. Nothing here instructs the agent.

risk_markers

none

notes32 words

The tier is configuration written into the run context rather than a port, because a fork reads context keys and a decision card writes no status distinction a guard could use instead.

The card's own version, and who wrote it.

version

1.0.0

author

autogen

provenance

not stated