Students, teachers, parents — and the AI agents they bring — build real apps and reports against one platform, by reading plain-language docs and calling one API. Two front doors, one database.
For teachers, students, parents & their AI agents.
For district integrators & compliance reviewers.
Who everyone is and where they belong — students, parents, guides, staff; schools, districts, levels; and the memberships that connect them over time.
What there is to learn — the knowledge graph of skills and how they relate, plus the academic standards it references. The same map for every student.
Articles, videos, audio, images, interactives, questions, and tests — each tagged to what it teaches. Everything a student actually interacts with, and nothing else.
The first-party reference player resolves Curriculum renderer refs, fetches Content and QTI launch material, writes Events, and shows Results readback.
The activity stream — a student launches an app, asks for a hint, submits an answer, sits a test. A record that something happened.
How each student is doing — outcomes, test scores (including MAP), the working grade, the report card, and each student's mastery as it grows and decays.
Derived report facts — minutes, XP rollups, streaks, accuracy, completion, school-day calculations, grade-level status, and RIT/grade reads.
Which third-party application is calling Alpha — its publisher, lifecycle, tenant grants, scopes, clients, sandbox boundary, and request attribution.
Drop the global skill pack and your credentials into Claude, Codex, or Perplexity. It routes the agent to the right Platform3 surface and module pack — no copied tables, no hidden growth math, no private data wrangling.
Install the global skill pack + your platform credentials into your AI agent, point it at the docs above, and ask it to build — a quiz app, a leaderboard, a learning report. If it needs to compute something the platform should have done, that's a gap we fix on the platform, not in your app.
Generation-loop provenance and progress enter through Platform's governed producer contract; generated student-facing artifacts materialize through Content and QTI.