sico studioRouting decisions
| Request | First useful action | Possible handoff |
|---|---|---|
| “How does this save work?” | Trace code and explain | DOC only if requested |
| “It saves twice after restart” | Diagnose/reproduce | Bug TSK with evidence |
| “I want remote agent control” | Check settled decisions, grill gaps | Research/spec/wayfinder |
| “Show me alternative layouts” | Prototype against brief | Selected ART/SRT → spec |
| “Build the selected task” | Check assignment and criteria | Implement → Review |
| “Remember this preference” | Preserve exact context and classify scope | FDK/MEM proposal/application |
Example response: “The open question is whether duplicate delivery or duplicate local allocation causes the extra record. I’ll trace the command key through the writer, reproduce it and use diagnose. No model launch is needed for that inspection.”
A useful orientation names the destination, known evidence, blocking uncertainty, selected mode and next action. It does not list every available mode or create records just to make the dashboard look populated.