Current beta acceptance checklist / Lista actual de aceptación de la beta

← NotatkyMarkdown · EN / ES ↓

Beta execution plan / Plan de ejecución

2026-09-05 · Draft for review / Borrador para revisión

English

Status: protected adult preview; external teen enrollment remains closed. Evidence checked September 5, 2026 (Pacific time). This continues BETA-READINESS.md and the existing A–G delivery order. Operating budget: at most $100/month total. First proposed family cohort: 5–10 invited families, learners 14–17, English and Spanish. This is a plan, not enrollment evidence or a legal compliance certificate.

What is available now

Ordered delivery checklist

Stage Acceptance evidence still required Current state
A. Account foundation Real login/logout/expiry on intended devices Configuration and email templates installed; synthetic account tests pass; owner email verified
B. Family admission Verified guardian relationship, learner assent, versioned agreements, revocation and safe-recipient handling Family schema installed; operational verification and family onboarding remain open
C. Library integration Real authenticated save, second-device restore, cross-user denial, conflict recovery and deletion Editor and owner policies implemented; migrations installed; adult eligibility/grant and production acceptance pending
D. Protected processing Authenticated PDF/PNG/voice jobs, isolated workers, resource limits, cancellation and EN/ES fixtures Local/portable foundations exist; hosted integration open
E. AI and safeguarding Reviewed vendor terms, enforced quotas, EN/ES safety evaluation, delivery failures and human escalation Hosted AI and parent delivery not connected; provider/operations review pending
F. Launch operations Recovery/deletion drill, support ownership, legal fields, vendor inventory, incident handling and intended domain HTTPS protected Railway preview live; notatky.com connection and remaining operational checks open
G. Family acceptance Full phone/tablet/desktop flow: upload/record → notes → additions → explanation → practice → restore Pending completion of B–F; use synthetic material before teen data

Next small chunks

Required inputs and unresolved limits

The operator must provide legal name, mailing address, working privacy/support contacts and launch states. Guardian verification method, safety reviewer, retention schedule and vendor data-use terms must be finalized against the actual deployment. The bilingual agreement pack remains a draft and must not collect acceptance while required fields are unresolved.

The adult pilot is a restricted test route, not proof of age or legal compliance. No automatic parental disclosure of every sensitive school question. No paid subscriptions or cancellation provider are connected; do not show a fake cancellation success. Full plagiarism scanning needs a separately evaluated provider and data-handling terms.

Each code chunk uses a separate branch/PR and relevant tests. Merge, deployment, database installation and real user acceptance are separate evidence stages. Roll back code using the previous verified release; revoke admissions to stop writes while preserving owner read/export/delete. Do not delete notes as an authorization rollback.