BrainLoader CIE

A guided pipeline: ingestion → graph → unit → sequencer → compliance → export. Wizard state stays in this browser; curriculum data lives in Supabase via brainloader-cie.

Pipeline status

IngestionEmpty
Root hash—
Graph snapshot—
Unit—
Compliance—
Export—

How this connects to BrainLoader

  • Sequencer & units persist to your Supabase database (sequenced_sequences). The lesson runtime loads those lessons for students (replace lesson-1 with a real lesson_id from your sequence).
  • BrainBarn & roadmap use the same mastery_outcomes / NESA alignment as this pipeline — practice gaps on the teacher dashboard reinforce outcomes you sequence here.
  • Set CIE_API_URL on Vercel to your Railway brainloader-cie URL so ingestion, graph, and sequencer APIs resolve in production.

Switch areas anytime using the sticky workspace bar at the top (Teacher hub, Curriculum, Mastery, Student view).

Ingestion

Not started

Parse syllabus text into a structured tree and validate coverage.

No parse loaded yet. Paste a syllabus to begin.

Run ingestion

Graph

Pending

Build the persisted curriculum graph snapshot from the parsed tree.

Requires a successful ingestion tree.

Build graph

Unit

Pending

Select outcomes and content, then generate a teaching unit with quests and guardrails.

Select curriculum scope and run generation after graph build.

Generate unit

Sequencer

Needs unit

Living School sequencer cockpit — weekly timeline, adaptation, assessment-informed refocus.

Generate a unit first — the sequencer binds to your pipeline unit id.

Open cockpit

Compliance

Pending

Evaluate audit readiness, heatmap, and compliance warnings.

Run compliance after a unit is saved.

Evaluate

Export

Pending

Export the BrainLoader payload (JSON) for the active unit.

Create an export to download the BrainLoader JSON.

Create export