Separate automatic and explicit routing
Automatic chat finds an appropriate route; the developer playground respects deliberate persona and provider selections.
Agent systems / Backend
The right expertise for the request.
Persona-aware routing and multi-provider orchestration, with an inspectable execution path.
A user should not have to understand every persona and model to ask a useful question. GRID07 separates intent, expertise, model selection, and execution so those decisions can be inspected.
A simplified view of the documented workflow. Select a node to inspect its role.
GRID07
A question arrives with its conversation context.
Automatic chat finds an appropriate route; the developer playground respects deliberate persona and provider selections.
Local feature-hashed embeddings, domain overlap, and conversation continuity inform persona selection. The implementation does more than keyword matching.
Routing decisions, node events, and execution records are persisted so the result is accompanied by an inspectable path.
The repository documents 84 backend tests and a reproducible benchmarking workflow. This portfolio’s routing walkthrough is deliberately a simplified, local illustration.
Built during my 8 Queens Software internship. The conceptual diagram below describes the documented architecture; it is not a live inference trace or a claim that a model request is running.