🎓 pack: edtech-pack

Ship K-12 software without the FTC COPPA fine.

Q: What human gates does edtech-pack introduce?

gate:coppa-consent (product + legal), gate:ferpa-disclosure (school district admin), gate:508-conformance (a11y lead). These layer on top of the standard plan/ship gates.

Q: What if my project doesn't match these signals exactly?

You can manually add the pack name to PROJECT.md or run /migrate to re-run detection with updated rules.

Building an LMS overlay, AI tutor, gradebook, or anything touching student PII? GreatCTO auto-attaches edtech-pack with COPPA verifiable parental consent, FERPA directory-information opt-out, GDPR-K (Article 8) digital age-of-consent matrix, Section 508 + WCAG 2.2 AA, plus state-law student-data protection (SOPIPA-CA, NY Ed Law 2-D).

$ npx great-cto init All packs ↗

Auto-attach signals

Detected by CLI when:

kindergarten · school · student · lms · canvas · blackboard · google-classroom · clever · classlink · coppa · ferpa

The pack rides on top of your base archetype (web-service, ai-system, fintech, …) — it doesn't replace it. Auto-injects reviewer agents into the pipeline + opens human gates listed below.

Reviewer agents activated

1 specialist added to the pipeline.

01 · edtech-reviewer

COPPA § 312 verifiable parental consent · FERPA disclosure rules · GDPR-K age-of-consent by EU member state · SOPIPA-CA · NY Ed Law 2-D · CSAM hash check on uploads

Human gates introduced

3 new gate types on top of `gate:plan` + `gate:ship`.

Gate	Owner	Trigger
`gate:coppa-consent`	product + legal	before collecting any under-13 data
`gate:ferpa-disclosure`	school district admin	before sharing educational records with vendors
`gate:508-conformance`	a11y lead	before public release of student-facing UI

Required artefacts before senior-dev claims tasks

7 concrete deliverables.

✓ COPPA verifiable parental consent workflow (email-plus-credit-card / signed form / video-conf verification)
✓ FERPA directory-information opt-out interface
✓ GDPR-K Article 8 age-of-consent matrix by EU member state (13/14/15/16 varies)
✓ Section 508 ICT + WCAG 2.2 AA test report on all student-facing screens
✓ Student-data deletion workflow (SOPIPA / NY 2-D)
✓ Vendor data-protection addendum (DPA) for school district contracts
✓ Annual privacy notice + parental-access portal

EVAL suite required

5 golden-set scenarios shipped as templates.

Each EVAL has ≥5 test cases, pass threshold, regression interpretation, cross-refs to TM + gates. Run via your existing test framework.

EVAL-edtech-under13-detection.md
EVAL-edtech-parental-consent-flow.md
EVAL-edtech-ferpa-directory-opt-out.md
EVAL-edtech-wcag-aa-conformance.md
EVAL-edtech-csam-hash-check.md

Regulatory surface covered

9 standards / regulations addressed.

COPPA (15 USC § 6501) FERPA (20 USC § 1232g) GDPR Article 8 SOPIPA (CA) NY Ed Law § 2-D PPRA Section 508 ICT Refresh WCAG 2.2 AA CIPA

FAQ

Common questions about edtech-pack.

When does edtech-pack auto-attach?

When the CLI detects these signals in your repo: kindergarten · school · student · lms · canvas · blackboard · google-classroom · clever · classlink · coppa · ferpa. Override anytime by editing packs: in PROJECT.md.

What human gates does edtech-pack introduce?

gate:coppa-consent (product + legal), gate:ferpa-disclosure (school district admin), gate:508-conformance (a11y lead). These layer on top of the standard plan/ship gates.

What if my project doesn't match these signals exactly?

You can manually add the pack name to PROJECT.md or run /migrate to re-run detection with updated rules.

30 seconds

Drop GreatCTO into any repo — edtech-pack attaches automatically.

$ npx great-cto init

no signup·runs locally·pay your own API