lakehouse

Go to file

root 1bee0e4969 Qwen 3 integration + agent plan + playbook loop

Pulled qwen3 (8.2B, 40K context, thinking, tool-calling). Created
agent-qwen3 profile. Ran structured plan: 5 contracts (16/16 filled
via hybrid), 5 intelligence questions (2/5 — same RAG counting gap).

Key playbook entry generated: "count/aggregation questions must use
/sql not /search. RAG returns 5 chunks from 10K — cannot count the
full dataset." This routing rule is now in the playbooks database
for future agent runs to learn from.

Pattern confirmed across qwen2.5, mistral, AND qwen3: the structured
matching path (hybrid SQL+vector) is production-ready across all
models. The RAG counting gap is a routing problem, not a model
problem — the fix is query classification, not a better model.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-04-17 00:08:48 -05:00

crates

Hybrid SQL+Vector search — the gap is closed

2026-04-16 22:49:48 -05:00

data

Ingest Ethereal 10K worker profiles — domain data in the substrate

2026-04-16 22:26:19 -05:00

docs

PRD: hybrid search is operational, Ethereal data integrated

2026-04-16 23:10:56 -05:00

inbox/processed

Scheduled ingest: file watcher auto-ingests from ./inbox