Academy OS — Routing Studio
Curriculum sequencing, progression rules, and support-lane logic
Critical backend interface

This is the hidden product: the logic that turns separate tools into one academic block.

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, retry, or advancement.

Human-readable rule cards

What adults need to understand and adjust.

Main lane

If the student completes the reading warm-up and grammar review on pace, route into the next scheduled math lesson in the daily core sequence.

Support lane

If the student records repeated misses or stalls on multi-step multiplication, route to a shorter support sequence before returning to the main lesson.

Escalation

If the same struggle pattern appears across consecutive blocks, add the learner to teacher review and pause automatic advancement in that subject.

Extension

If the student finishes the core path early with strong accuracy and stable pace, unlock broader learning or enrichment work.

Machine-readable config mock

How a first MVP could store routing decisions before any advanced ML layer exists.
{
  "cohort": "grade4_core_block",
  "subjects": ["math", "reading", "grammar"],
  "sequence": [
    "lexia_reading_warmup",
    "noredink_grammar_review",
    "ixl_multiplication_main"
  ],
  "rules": [
    {
      "if": "reading_complete && grammar_complete",
      "then": "route:ixl_multiplication_main"
    },
    {
      "if": "repeated_misses >= 3 && subject == 'math'",
      "then": "route:math_support_lane"
    },
    {
      "if": "pace_drop == true && idle_minutes >= 5",
      "then": "alert:teacher_monitor"
    },
    {
      "if": "core_complete && confidence > 0.85",
      "then": "route:broader_learning_extension"
    }
  ]
}