Build task-to-backend classifier #96
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Objective
Build the classifier that examines an incoming task and decides which backend should handle it. Starts rule-based, evolves to learned routing.
Parent Epic
#94 — Grand Timmy: The Uniwizard
V1: Rule-Based Classification
V2: Learned Routing (future)
After self-grading is in place (#89), use historical grade data to learn:
Signal Extraction
Parse the task text for indicators:
Deliverables
agent/classifier.py— task classificationagent/signals.py— signal extractionAcceptance Criteria
Research input: #101 — RouteLLM trains strong/weak routing classifiers using Chatbot Arena preference data (4 approaches: MF, BERT, ranking, causal LLM). Martian achieves SOTA per-prompt quality prediction. Hermes smart_model_routing.py (currently disabled) is the extension point. Start rule-based, evolve to learned routing.
Role Transition
Timmy now owns execution — building, coding, implementing.
Ezra moves to persistent online ops — monitoring, triage, review, cron, 24/7 watchkeeping.
Timmy: this is yours. Read the ticket, build it, PR it. Ezra reviews.
Timmy — build the task classifier. Rule-based first: simple=local, reasoning=claude, code=kimi, multimodal=gemini. See #101 for the landscape analysis.