Academy OS — Routing Studio

This is the hidden product: the logic that turns disconnected vendors into one school day.

Without a routing studio, Academy OS is just a dashboard wrapper. This interface shows how staff define lesson arcs, fallback paths, support-lane transitions, and the conditions that trigger intervention or acceleration.

Human-readable rule cards

What operators need to understand and change.

Main lane

If a student clears checkpoint A and B in Math Academy with confidence ≥ 0.8, route to next lesson in fractions sequence.

Support lane

If a student records 3 repeated misses on equivalent-fractions prerequisites, route to MobyMax support module for 12–15 minutes, then reattempt main lesson.

Escalation

If the same concept trigger appears across two consecutive days, add the learner to Tutoring Director review and pause automatic acceleration.

Extension

If pacing is 2+ lessons ahead and error rate stays low for 20 minutes, unlock enrichment problem set or challenge lane.

Machine-readable config mock

How a first MVP could store routing decisions before any ML layer exists.

{
  "cohort": "grade7_math",
  "sequence": [
    "fractions_foundations",
    "fraction_multiplication",
    "ratios_intro",
    "unit_rates"
  ],
  "rules": [
    {
      "if": "repeated_misses >= 3 && concept == 'equivalent_fractions'",
      "then": "route:mobymax_support_equivalent_fractions"
    },
    {
      "if": "idle_minutes >= 6 && recent_accuracy < 0.6",
      "then": "alert:guide_monitor"
    },
    {
      "if": "pace_delta > 2 && confidence > 0.85",
      "then": "route:extension_lane"
    }
  ]
}