Loading The VR School
Loading The VR School
The VR School now models the school as source code: enrollment, support, course planning, dashboards, EduCoin™, credentials, payments, safety, district partnerships, and creator operations all have workflows, task contracts, event schemas, evidence, and launch gates.
not ready for 5m burst
The platform is inspiring and live, but the listed blockers must be resolved before claiming global-scale launch readiness.
Workflows
19
TaskDefs
70
Contracts
71
Blockers
6
The first LittleHorse-ready workflow is source code, not a slide. It has task definitions for lead classification, SofAI follow-up, operator notification, and append-only School-as-Code event recording.
classify-lead
LittleHorse TaskDef boundary
send-sofai-followup
LittleHorse TaskDef boundary
notify-operator
LittleHorse TaskDef boundary
record-school-as-code-event
LittleHorse TaskDef boundary
19 workflows across 14 domains.
70 TaskDefs and 71 event contracts.
The app is manifest-ready, but LITTLEHORSE_API_HOST and LITTLEHORSE_NAMESPACE are not configured.
Install Docker or provision LittleHorse Server, then run scripts/start-littlehorse-local.mjs locally or configure production LITTLEHORSE_* env vars.
DATABASE_URL/FLY_DATABASE_URL is missing. Persistent leads, EduCoin™, credentials, and dashboard state cannot be trusted at scale.
Create managed Postgres, set DATABASE_URL in Vercel production, redeploy, then POST /api/educoin/database-readiness with the banking token.
RESEND_API_KEY plus CONTACT_NOTIFY_TO or ADMISSIONS_NOTIFY_EMAIL are required for automatic replies and operator alerts.
Set RESEND_API_KEY, CONTACT_FROM_EMAIL, and CONTACT_NOTIFY_TO in Vercel production.
Protected bootstrap/admin APIs need EDUCOIN_BANK_ADMIN_TOKEN when no admin session is available.
Generate a high-entropy token and configure EDUCOIN_BANK_ADMIN_TOKEN in production.
EduCoin™, payment rails, banking, credential issuance, privacy, and youth incentives require legal/compliance approval before regulated claims.
Complete legal review, user terms, privacy/data agreements, partner contracts, compliance policies, and incident response ownership.
The app can publish static pages and APIs, but a 5M-user burst requires CDN/load testing, queue limits, database pooling, email rate limits, WAF/rate limits, and incident staffing.
Run k6 load tests, configure Vercel/DB/email limits, enable observability, and prepare an operator war room before a major public launch.