AI tutoring systems in engineering labs face a tension between providing sufficient assistance and preserving learning opportunities. Existing systems typically offer instructors limited control over assistance timing, content, or cost. This paper describes a routing and governance system for LLM-based lab assistance comprising two components: Routiium, an OpenAI-compatible gateway that manages multiple LLM backends with configurable prompt modifications and usage logging, and EduRouter, a policy-aware routing service that enforces per-lab budgets, approval workflows, and embedding-based question matching. We evaluated the system using trace-driven simulation calibrated from two engineering labs (LED characterization, RC circuit analysis) and a 100-query replay through live models. In simulations, governed policies (P1/P2) increased challenge-alignment index from 0.90 to 0.98 and overlay-adherence score from 0.69 to 0.87 compared to ungoverned operation (P0). The productive-struggle window metric increased from 1.4 to 3.6 simulated turns before high-scaffold hints appeared. In the 100-query replay, EduRouter routed 75% of queries to a local model, reducing token costs by 66% (0.087vs.0.26 for all-premium routing) while maintaining canonical hit rate of 1.0 for the curated 89-intent question bank. We release Routiium, EduRouter, canonical-task tooling, and simulator configurations to support replication and future classroom studies.
Figures & tables
System
Multi-model routing
Budget enforcement
Instructor approvals
Prompt/audit transparency
FrugalGPT [ 8 ]
✓
✓
—
—
RouteLLM [ 9 ]
✓
(varies)
—
—
ThriftLLM [ 10 ]
✓
✓
—
—
This work (Routiium+EduRouter)
✓
✓
✓
✓
TABLE I: Positioning relative to related systems (illustrative dimensions).
Label
Definition
Governance behavior
L0
Validation or minimal prompt
No approval required; conceptual framing
L1
Guided troubleshooting hint
Overlay adds justification prompts
L2
Worked example fragment
Requires budget debit; throttled after configurable retry count
L3
Complete solution
TA approval required plus budget and frequency limits
P0
Ungoverned
No spend limits, overlays disabled, no approvals
P1
Governed
Per-turn spend limits, overlays enabled, L3 frequency caps
TABLE II: Hint levels and policy modes referenced throughout the paper.
Fig. 1: LABIIUM educational platform architecture with centralized teacher control, an explicit routing stack (EduRouter + Routiium), and distributed LAMB devices. The teacher console configures policies, approvals, and overlays; EduRouter computes cost- and policy-aware plans ( /route/plan ) while Routiium exposes an OpenAI-compatible proxy with overlays, logging, and streaming telemetry. Students reach their assigned LAMB via secure web tunnels, which in turn talk to instruments and DUTs while upstream assistance is routed through this governable routing and assistance plane.
Fig. 2: Protocol-level interaction between student, teacher console, Routiium, EduRouter, and LLM backends. Routiium receives chat requests, consults EduRouter’s /route/plan , dispatches to local vLLM or external OpenAI GPT-5 Mini, and streams the response back with routing headers.
Field
Content
Routing rationale
Reason for model selection (e.g., “canonical match: RC circuit troubleshooting” or “budget limit enforced”)
Question match
Matched library entry IDs and similarity scores
Active overlay
Which prompt modifications were applied
Content fingerprint
Hash for verifying overlay application
Request trace ID
Link to equipment telemetry
TABLE III: Metadata logged for each routing decision.
Fig. 3: Trace-driven simulator pipeline used for synthetic evaluation.
Policy
CAI
OAS
PSW
IIL
EI
P0 (Ungoverned)
0.90
0.69
1.45
5.20
0.59
P1 (Governed)
0.98
0.84
2.75
3.20
0.56
P2 (Integrity)
0.98
0.87
3.56
2.39
0.52
TABLE IV: Steerability metrics by policy (simulator, mean across seeds; IIL in turns).
Embedding
CHR
CRG
FCR
gte-large-en-v1.5
0.95
0.19
0.007
bge-large-en-v1.5
0.95
0.17
0.012
nomic-embed-text-v1.5
0.94
0.17
0.011
bge-small-en-v1.5
0.93
0.15
0.015
FastEmbed (edge)
0.72
0.05
0.010
Embedding off
0.00
0.00
0.000
TABLE V: Canonical metrics (simulator, averaged across jobs).
Policy
Freeze TTL
CSS
P0 (Ungoverned)
None
0.00
P1 (Governed)
5 min
0.49
P2 (Integrity)
30 min
0.60
TABLE VI: Canonical Stickiness Stability ( CSS ) by policy and freeze horizon.
Fig. 4: Embedding ablation in the simulator. Bars show canonical hit rate (CHR, left) and canonical routing gain ( CRG , right) averaged over cache TTLs and warm/cold starts for five embedding configurations—BAAI/bge-small-en-v1.5, BAAI/bge-large-en-v1.5, Alibaba-NLP/gte-large-en-v1.5, nomic-ai/nomic-embed-text-v1.5, and a FastEmbed deployment (ONNX wrapper around BAAI/bge-small-en-v1.5)—plus a no-embeddings baseline. Direct cloud-style integrations of the larger models achieve the strongest CHR and CRG , while the FastEmbed edge deployment trades some canonical fidelity for lower infrastructure cost and dependence on external providers.
Fig. 5: 100-query replay results. (a) Token cost by routing configuration. (b) End-to-end latency. (c) Time-to-first-token decomposed into routing and execution components. (d) Routing correctness by query difficulty.
Large language model routing selects models, tools, experts, or inference strategies to balance answer quality, cost, latency, and deployment constraints.
School of Artificial Intelligence, Nanjing University, China · 2National Key Laboratory for Novel Software Technology, Nanjing University, 210023, China · 3SinapisAI