[ARCH] Adaptive Logic Router — classify queries to the right symbolic engine #42

New Issue

perplexity · 2026-03-27T22:48:35Z

perplexity commented

2026-03-27 22:48:35 +00:00

Source

"Integrating Symbolic Reasoning Engines into Hermes Agent", Section 1.2.
"Hermes Agent: The Definitive Neuro-Symbolic Blueprint for Mac M3 Max", Section 3.1.

What

Build the Logic Router that decides which symbolic engine (Z3, SymPy, Lean, or pure LLM) handles a given query.

Design progression

v0 — Rule-based: Keyword classification (constraints/satisfy → Z3, calculate/simplify → SymPy, prove/theorem → Lean, everything else → LLM)
v1 — Few-shot classifier: Small LLM (Distil-Hermes on E-cores) classifies queries into logical domains with few-shot examples
v2 — Learned router: Fine-tuned classifier trained on query→engine routing data collected from v0/v1

Architecture (from paper)

Problem Classification → Formalism Selection → Prompt Engineering for Formalism
The router selects both the engine AND tailors the system prompt to produce output in the engine's DSL (SMT-LIB, Python, Lean tactics)

Acceptance (v0)

Given a user query, the router returns {engine: "z3"|"sympy"|"lean"|"llm", confidence: float}
Routing decision logged for future training data collection

Dependencies

At least Z3 and SymPy tools registered before the router is useful

## Source "Integrating Symbolic Reasoning Engines into Hermes Agent", Section 1.2. "Hermes Agent: The Definitive Neuro-Symbolic Blueprint for Mac M3 Max", Section 3.1. ## What Build the Logic Router that decides which symbolic engine (Z3, SymPy, Lean, or pure LLM) handles a given query. ### Design progression 1. **v0 — Rule-based:** Keyword classification (constraints/satisfy → Z3, calculate/simplify → SymPy, prove/theorem → Lean, everything else → LLM) 2. **v1 — Few-shot classifier:** Small LLM (Distil-Hermes on E-cores) classifies queries into logical domains with few-shot examples 3. **v2 — Learned router:** Fine-tuned classifier trained on query→engine routing data collected from v0/v1 ### Architecture (from paper) - Problem Classification → Formalism Selection → Prompt Engineering for Formalism - The router selects both the engine AND tailors the system prompt to produce output in the engine's DSL (SMT-LIB, Python, Lean tactics) ## Acceptance (v0) - Given a user query, the router returns `{engine: "z3"|"sympy"|"lean"|"llm", confidence: float}` - Routing decision logged for future training data collection ## Dependencies - At least Z3 and SymPy tools registered before the router is useful

Timmy commented

2026-03-27 22:50:30 +00:00

⚡ Dispatched to claude. Huey task queued.

⚡ Dispatched to `claude`. Huey task queued.

gemini commented

2026-03-27 23:20:27 +00:00

🔧 gemini working on this via Huey. Branch: gemini/issue-42

🔧 `gemini` working on this via Huey. Branch: `gemini/issue-42`

grok commented

2026-03-27 23:20:35 +00:00

🔧 grok working on this via Huey. Branch: grok/issue-42

🔧 `grok` working on this via Huey. Branch: `grok/issue-42`

gemini referenced a pull request that will close this issue

2026-03-27 23:20:37 +00:00

[gemini] [ARCH] Adaptive Logic Router — classify queries to the right symbolic engine (#42) #46

gemini referenced this issue from a commit

2026-03-27 23:20:38 +00:00

[gemini] [ARCH] Adaptive Logic Router — classify queries to the right symbolic engine (#42)

grok commented

2026-03-27 23:20:41 +00:00

⚠️ grok produced no changes for this issue. Skipping.

⚠️ `grok` produced no changes for this issue. Skipping.

Timmy was assigned by Rockachopa

2026-03-28 03:52:20 +00:00

Timmy referenced this issue

2026-03-28 04:45:15 +00:00

[ARCH] Adaptive Logic Router — classify queries to the right symbolic engine #43

Timmy commented

2026-03-28 04:52:59 +00:00

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:53:00 +00:00

Timmy referenced this issue

2026-03-29 00:03:08 +00:00

[HARNESS] Z3 Crucible as a timmy-config sidecar (no Hermes fork) #86

allegro referenced this issue

2026-04-04 12:05:29 +00:00

[RETRO] Burn Down Night Retrospective -- 2026-04-04 #114

Sign in to join this conversation.