A clear line between what exists today and what we are building next.
Splash Spectrum now has both a live public website and a deployed authenticated classroom pilot MVP. Product development and validation are still active, and this page prevents pilot capabilities and roadmap ideas from being mistaken for district-ready production features.
Public, pilot, development, and roadmap status.
The school-facing website, navigation, trust pages, pricing targets, pilot information, and interactive Glass Box demonstration are deployed.
The public website includes an interactive educational demonstration. The authenticated classroom pilot also records student inputs, teacher-approved source context, major system stages, claim categories, and evidence-quote support checks. It does not claim to expose private model chain-of-thought or provide complete production-grade provenance telemetry.
The authenticated classroom pilot supports teacher-created Story Studio assignments, required concepts, pasted teacher-approved source text, student creative choices, pre/post generation safety gates, source-support checks, verification, reflection, and teacher evidence. This remains a pilot workflow rather than a broadly deployed school product.
A separate authenticated pilot application now supports fixed teacher/student roles, classes, revocable join codes, teacher-visible rosters, assignment open/closed controls, Story Studio generation, the AI Glass Box learning loop, and saved student learning evidence. District-grade SSO, roster integrations, source-file uploads, enterprise administration, and broader production hardening are not yet complete.
Planned after Story Studio validation, with code sandboxing, safety review, and AI literacy around game logic.
Planned after the MVP, with age-appropriate lyrics/audio safeguards and transparency around creative choices.
Planned later because video generation introduces higher compute, identity, deepfake, moderation, and classroom-management complexity.
The pilot has authenticated accounts and teacher-controlled class join codes, but those are not a substitute for district SSO or roster integrations. Google/Microsoft school identity plus Clever/ClassLink-style workflows remain part of the school-ready roadmap.
Final privacy policy, terms, DPAs, security documentation, subprocessors, retention, and school-contract materials must match the shipped platform.
Schools should evaluate the product that actually exists.
Pilot conversations can now be scoped around the working authenticated classroom loop: teacher-created classes and assignments, pasted approved source material, student Story Studio creation, safety gates, Glass Box inspection, verification, reflection, and teacher evidence. File ingestion, institutional rostering, district administration, final production legal/security controls, and future studios should not be treated as available contractual features until they are implemented and validated.