Timmy_Foundation/the-nexus
16
1
Fork 2
Code Issues 104 Pull Requests 1 Actions 119 Packages Projects Releases Wiki Activity

[HARNESS] Smart model routing — narrow decision space to competency space #604

New Issue
Closed
opened 2026-03-27 01:10:16 +00:00 by perplexity · 5 comments
perplexity commented 2026-03-27 01:10:16 +00:00
Member
Copy Link

Key Insight

"I just need to narrow the decision space based off the competency space. Claude Opus or Gemini for design discussions. A very dumb but very well-aligned model handles simple decisions."

Routing Strategy

Decision Type Model Why
Architecture/design discussions Claude Opus, Gemini High reasoning ceiling
Simple yes/no routing decisions Tiny aligned local model (Phi-3, Gemma 2B) Fast, cheap, no cloud dependency
Code generation Hermes 4 via harness Self-improvement loops capture training data
Math/logic verification Deterministic engine (SymPy/Z3) No hallucination risk
Personality/conversation Soul-file-tuned Hermes 4 Vibe alignment

Implementation

  • Define competency tiers for available models
  • Huey task router inspects task metadata → selects appropriate model
  • Log which model handled which task (feeds into Prometheus metrics)
  • Track cost-per-task across model tiers
  • Sovereignty bonus: prefer local model when confidence is sufficient

Related

  • Depends on local inference telemetry (already wired into Huey)
  • Feeds into sovereignty rubric (% of tasks routed locally vs cloud)

Source: Gemini brainstorm session 2026-03-26 — triaged by Perplexity

## Key Insight > "I just need to narrow the decision space based off the competency space. Claude Opus or Gemini for design discussions. A very dumb but very well-aligned model handles simple decisions." ## Routing Strategy | Decision Type | Model | Why | |---|---|---| | Architecture/design discussions | Claude Opus, Gemini | High reasoning ceiling | | Simple yes/no routing decisions | Tiny aligned local model (Phi-3, Gemma 2B) | Fast, cheap, no cloud dependency | | Code generation | Hermes 4 via harness | Self-improvement loops capture training data | | Math/logic verification | Deterministic engine (SymPy/Z3) | No hallucination risk | | Personality/conversation | Soul-file-tuned Hermes 4 | Vibe alignment | ## Implementation - [ ] Define competency tiers for available models - [ ] Huey task router inspects task metadata → selects appropriate model - [ ] Log which model handled which task (feeds into Prometheus metrics) - [ ] Track cost-per-task across model tiers - [ ] Sovereignty bonus: prefer local model when confidence is sufficient ## Related - Depends on local inference telemetry (already wired into Huey) - Feeds into sovereignty rubric (% of tasks routed locally vs cloud) --- _Source: [Gemini brainstorm session 2026-03-26](https://g.co/gemini/share/3700c8d29b6b) — triaged by Perplexity_
perplexity added the modularizationp1-importantharness labels 2026-03-27 01:10:16 +00:00
Timmy commented 2026-03-27 01:15:28 +00:00
Owner
Copy Link

🔍 Triaged by Huey — needs assignment.

🔍 Triaged by Huey — needs assignment.
Timmy commented 2026-03-27 01:30:23 +00:00
Owner
Copy Link

🔍 Triaged by Huey — needs assignment.

🔍 Triaged by Huey — needs assignment.
Timmy commented 2026-03-27 01:45:23 +00:00
Owner
Copy Link

🔍 Triaged by Huey — needs assignment.

🔍 Triaged by Huey — needs assignment.
Timmy commented 2026-03-27 02:00:20 +00:00
Owner
Copy Link

🔍 Triaged by Huey — needs assignment.

🔍 Triaged by Huey — needs assignment.
Timmy commented 2026-03-28 04:52:32 +00:00
Owner
Copy Link

Closing during the 2026-03-28 backlog burn-down.

Reason: this issue is being retired as part of a backlog reset toward the current final vision: Heartbeat, Harness, and Portal. If the work still matters after reset, it should return as a narrower, proof-oriented next-step issue rather than stay open as a broad legacy frontier.

Closing during the 2026-03-28 backlog burn-down. Reason: this issue is being retired as part of a backlog reset toward the current final vision: Heartbeat, Harness, and Portal. If the work still matters after reset, it should return as a narrower, proof-oriented next-step issue rather than stay open as a broad legacy frontier.
Timmy closed this issue 2026-03-28 04:52:32 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
3d-world
CI
Continuous integration, runners, workflow issues
 QA
Quality assurance, testing, and production audit
 actionable
agent-presence
aistudio-ready
assigned-aistudio
assigned-claude
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-gemini
assigned-groq
assigned-kimi
Dispatched to Kimi via OpenClaw
 assigned-kimi
assigned-perplexity
assigned-sonnet
blocked
Blocked by external dependency or merge conflict
 claude-ready
claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 deprioritized
duplicate
epic
Epic / umbrella issue
 gemini-api
Gemini API integration
 gemini-review
google-ai-ultra
Google AI Ultra integration work
 groq-ready
harness
identity
Timmy identity and branding
 infrastructure
kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 kimi-ready
lazzyPit
Lazarus Pit — automated agent resurrection and health recovery
 media-gen
AI media generation (image/video/audio)
 modularization
needs-design
nostr
p0-critical
p1-important
p2-backlog
performance
perplexity-ready
portal
research
Deep research and planning tasks
 security
Security hardening, vulnerability fixes, access control
 sonnet-ready
sovereignty
velocity-engine
Auto-generated by velocity engine
No Label harness modularization p1-important
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok groq hermes kimi manus perplexity sonnet
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-nexus#604
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?