For schools and operators
Kidoko is built for supervised community and school learning first — shared tablets, intermittent connectivity, and a facilitator who runs sessions.
What a deployment needs
- Devices — shared Android tablets (or phones) provisioned by the programme; learners do not need accounts.
- A facilitator — a named adult who runs sessions, takes attendance and reviews learner work, with a trained backup.
- Connectivity is optional — content packs are provisioned ahead of time; an optional local school hub keeps a whole LAN working and relays syncs when a link appears. Offline does not mean install-without-provisioning — setup needs a connection once.
- A safeguarding posture — named contacts, permissions on file, and the readiness items below signed before real learners enrol.
How a site becomes operational
Sites follow a lifecycle — proposed → onboarding → ready → operational. The platform enforces it: a site cannot enrol real learners until every critical readiness item — participant permissions, staff training, venue and materials — is signed by a named owner, and operating minima (leadership, facilitators, safeguarding pair, deployment mode, capacity) are in place. Retracting a critical item demotes the site back to onboarding.
evidence A site cannot enrol real learners until a readiness checklist — participant permissions, staff training, venue and materials — is signed by named owners; the platform refuses real-learner enrolment while a critical item is unsigned.
- Readiness gate runbook
docs/ops/10-readiness-gate.md - Device gate report
docs/ops/device-gate-report.md— adversarial probe battery on synthetic fixtures
evidence Downloaded lessons, practice and facilitator tools keep working without a live internet connection; progress queues on the device and syncs later through the cloud or a school hub.
- Disconnected-school dress rehearsal
docs/ops/evidence/dress-rehearsal.md— engineering rehearsal on synthetic data - Pilot operations rehearsal report
docs/ops/pilot-ops-rehearsal-report.md— engineering rehearsal on synthetic data
evidence Private surfaces — learner profiles, portfolios, administration and assessment banks — sit behind server-side authorization and are excluded from search indexing; an unauthenticated request gets an authorization challenge, not content.
- Independent security and access review
docs/ops/security-access-review.md— live adversarial battery against the real API
What a school gets
- Session plans and attendance tools that work on the LAN with no internet.
- Observation and evidence capture tied to the session plan.
- Content updates delivered as signed packs — over the air or sneakernet.
- Honest operational reporting: delivered sessions, device health, and flagged problems — not vanity metrics.