Route backend tasks to specialists

Route backend tasks to eight specialist architecture spokes

Routing backend work when the specific concern (REST design, testing, deployment) is not yet named.

• · backend task description
• · system context

• · spoke recommendation
• · architecture model reference

• · task explicitly mentions backend/server/API work

• · task boundaries ambiguous across multiple spokes
• · mismatch between stated task and actual layer

• · 8 documented specialist spokes
• · routing heuristics explicit in task→spoke map
• · cross-cutting dependency-inversion model