Phosra Spec / Capability
PCSS v1.0 — DraftPhosra Threshold
Verifiable parental consent and access boundaries.
What Threshold does
One parental authority gate for every consent flow in child-safety law.
Every child-safety law that asks for verifiable parental consent — COPPA’s foundational requirement, KOSA’s “access notification” duty, Utah’s App Store Accountability Act, Texas SCOPE — turns out to be the same primitive in different uniforms. So does every screen-time limit, every purchase approval, every contact-control gate. Each platform builds its own consent flow and its own approval queue.
Threshold is the canonical parental authority gate. A platform calls Threshold once with the request; Threshold returns Allow / Block / Pending Parent — backed by a verified parent attestation chain. The same primitive handles consent for account creation, time downtime windows, IAP approval, social-contact requests, school-mode toggles, and the Tech-Exit migration mode.
Parents stop being asked the same question twelve times across twelve apps. Regulators get a single audit-able consent record per child. Platforms inherit a verified-parent signal they can trust without standing up their own KYC stack.
How partners plug in
Threshold is a socket. Consent requests flow in. Verified decisions flow out.
These are the upstream consent providers and family-management surfaces Threshold federates — either shipping today, in conversation with a partner, or pending an upstream API.
Standards & laws
What Threshold does for each statute.
- COPPA / COPPA 2.0 — mediates verifiable parental consent before any data collection from a minor.
- KOSA — handles the parental-notification and time-restriction duties for covered platforms.
- NY SAFE for Kids — gates addictive-feed exposure pending parent attestation.
- CA AB 1709 (age-16 social media floor) — runs the parent-override consent flow.
- UT App Store Accountability Act + TX SB 2420 — performs the at-install consent check.
- EU GDPR-Kids (Art. 8) — verifies the parent’s age-of-consent override per member state.
Conformance
Adopter Tier 1 certification.
To ship Threshold-conformance for an Adopter Tier 1 certification, your implementation must pass the Threshold suite. Test count is [draft] coming Q3 2026. The suite covers parent-attestation chain verification, decision tracing across consent surfaces, audit-record emission, and federated-provider interop.
We are co-authoring the suite with our design partners. If you want a seat at the table while the bar is being set, reach out.
Rule list
The 14 rules Threshold ships
Every rule below is implemented by this capability. Pulled directly from the rule registry.
- Daily Time Limit — Enforces maximum daily screen time across platforms with configurable per-app or global limits.
- Scheduled Hours — Restricts platform access to specified time windows (e.g., after school, before bedtime).
- Time Per App Limit
- Time Downtime
- Phone Free School Hours
- Purchase Approval
- Purchase Spending Cap
- Social Contacts
- Social Multiplayer
- Stranger Outreach Friction
- Privacy Account Creation
- Parental Consent Gate
- Notification Curfew — Suppresses non-essential push notifications during configurable quiet hours (e.g., overnight).
- Dumbphone Migration Mode