Design note: scope-aware routing (load the background only when needed)#110
Closed
anth-volk wants to merge 1 commit into
Closed
Design note: scope-aware routing (load the background only when needed)#110anth-volk wants to merge 1 commit into
anth-volk wants to merge 1 commit into
Conversation
Draft design note (no implementation) proposing a scope router that picks which background tier a question needs — passing the user's prompt through the model in every case, but loading the full reference.md + tools only on the "needs computation" branch. Frames the router as the convergence point for the topic gate (#109), the scope/refusal contract (#102), and the confirm-first proposal: off-topic, unmodelled, and partial/confirm-first turns get a light-background model call (no reference doc, no tools) rather than a canned string. Hinges on a compact scope descriptor auto-derived from capabilities(), failing safe toward the full model when uncertain. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Beta preview has been cleaned up because this PR was closed. |
Contributor
Author
|
Closing — rather than keep this as a standalone design note, the routing approach is being built directly into #109. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Design note only — no implementation. Adds
docs/design/scope-aware-routing.md, a draft for discussion.It proposes a scope router that decides which background a question needs rather than what to say: every branch still passes the user's real prompt through the model, but only the "needs computation" branch loads the full
reference.md+ tool schemas. Off-topic, unmodelled, and partial/confirm-first turns get a light-background model call (small system prompt, no reference doc, no tools) instead of a canned string.Why open it
It's the convergence point for three things already in flight:
run_economy_simulationuntil the user agrees).Load-bearing idea
The router carries a compact scope descriptor (~a few hundred tokens) instead of the ~20k-token reference doc — and that descriptor is auto-derived from
capabilities()at build time (viascripts/build_reference.py) so it can't drift from the engine, with the router failing safe toward the full model whenever it's unsure.Status
Draft for discussion — I'd like agreement on the shape (router-as-second-model vs. progressive disclosure within one model; where the descriptor lives; how much of #102 collapses into it) before any code. Phasing and open questions are in the doc.
🤖 Generated with Claude Code