Kidoko Learning

Evidence

Every impact or capability claim on this site resolves here. A claim is only “evidence”-badged when it cites a real artifact; anything else shows what is missing.

How to read this page: evidence means a citable artifact exists today. evidence pending and proposed mean it does not — the entry says what would qualify it. There are no measured claims yet: no field pilot has run.

Backed today

Statements with a citable artifact — an engineering rehearsal, an adversarial review or a documented runbook in the repository. Where the artifact used synthetic data, the citation says so.

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 A lesson cannot reach learners until it clears independent educator and accessibility review; published versions are immutable and attempts stay pinned to the version attempted.

  • Timed lesson-production trial docs/ops/production-trial.md — one synthetic lesson through the real pipeline
  • Pilot course map and review state docs/content/pilot-courses.md

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 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

evidence No advertising to children, no sale of learner data, no public child profiles, no location tracking, no private adult-to-child messaging — these are product constraints, not just policy text.

evidence A learner marked local-only never syncs: their learning events stay on the device and are never sent to Kidoko servers.

evidence Pilot builds are signed with a recorded certificate fingerprint so a device can verify what it installs; the supported channel today is a programme-provisioned signed APK, not a public store listing.

  • Beta distribution runbook docs/ops/beta-distribution.md
  • Signing certificate record docs/release/store-submission/signing-certificate.md

evidence Outcome reporting derives every statistic — with its n, denominator, exclusions and method — from a frozen measurement protocol; the pipeline refuses bare numbers and causal claims.

  • Synthetic outcomes rehearsal report docs/ops/outcomes/rehearsal-outcomes-report.md — synthetic cohort — proves the pipeline, not learning results
  • Outcomes analysis plan docs/ops/outcomes/analysis-plan.md

Still pending evidence

Claims we intend to make once the qualified evidence exists. They are listed here — flagged — rather than implied anywhere else on the site.

evidence pending No field pilot has run, so there are no measured learning outcomes to publish. The first report will publish here with n, denominators and exclusions on every statistic.

  • What the real analysis will compute docs/ops/outcomes/analysis-plan.md — a plan, not results

What is missing: requires: field delivery — real baseline/endline administrations, double-scored judgments and operating-log entries.

evidence pending Programme cost figures — cost per enrolled, active and improved learner — will publish once real operating-log cost entries exist.

  • Cost model: capital / recurring / donated docs/ops/outcomes/analysis-plan.md — machinery verified; no field costs yet

What is missing: requires: field delivery — attended session-hours and real cost observations.

evidence pending A staffed public support mailbox is part of launch preparation; today support runs through the school facilitator and the programme team.

What is missing: requires: launch preparation — a monitored public mailbox.

Proposed coverage — not live

Plans, not facts. Proposed items describe what the programme intends, never what exists.

proposed Expansion beyond the first site is proposed to follow the site lifecycle — proposed, onboarding, ready, operational — with each step gated by delivery and learning evidence.

  • Site readiness model docs/ops/10-readiness-gate.md

What is missing: proposed coverage — the second-site replication trial has not run.

proposed Caregiver-supported home learning on family devices is planned after supervised school delivery proves out; it is not offered today.

What is missing: proposed — follows the supervised-deployment evidence gates.

How the registry works

Claims live in content/claims.json in the engineering repository, rendered through one component — a page cannot badge a statement as backed without the registry agreeing. The test suite asserts the convention: verified and measured claims must cite artifacts that exist; proposed and pending claims must name what is missing. Repo artifacts are cited by path — ask the programme team for a copy of any cited document.