Phosra — The Child Safety Intelligence Layer

AI SANDBOX

The Child Safety Intelligence Layer

Phosra reads the child-safety statutes coming out of 30+ jurisdictions, the controls each platform actually ships, and the policies each family enables — and enforces the right action across whichever surface can carry it. The interoperability layer for child safety.

Talk to a Partner Engineer See the Brief

91: Statutes watched continuously
104: Rule categories cross-jurisdiction
9: Enforcement surfaces orchestrated
1: Reasoning layer above them all

The Loop

Continuous Child-Safety Compliance — the job Phosra invents.

Compliance has always been a quarterly project. Phosra makes it a continuous one. The loop runs whether you’re watching or not.

01Ingest

Read everything, continuously.

Statutes from 30+ jurisdictions, weekly. Platform capability shifts. CSM Privacy-Program tier changes. Regulator alerts. Phosra workers run on your behalf whether you're watching or not.

02Reason

Route every rule to the best surface.

The Composite Enforcement Engine evaluates which native provider can natively carry each rule, and where Phosra's own services need to fill the gap. One rule grammar, 96 categories, every jurisdiction.

03Act

Enforce across every surface.

DNS, MDM, OS-level family controls, and Phosra's nine capabilities — orchestrated as one. The same rule that targets a Roblox account also reaches the family router and the device.

04Remember

Every decision, with full provenance.

Each enforcement is recorded with the law, the rule, the platform, the policy version. Query it. Export it. Hand it to a regulator. The history is yours — and it compounds.

Why · Phosra

Why Phosra is the reasoning layer, not another input.

The loop runs whether you're watching or not.

Phosra ingests new laws, platform capability shifts, and CSM tier changes continuously. The Brief tells you what changed for your fleet — by the time you open the dashboard, the reasoning has already run.

Interoperable by design — one rule, every surface.

96 rule categories, structured once. The Composite Engine routes each rule to whichever native provider can carry it, and uses Phosra's own services where they can't. DNS, MDM, OS controls, social platforms, MCP-connected agents — all one wire.

Provenance you'd lose if you left.

Every enforcement is recorded with the law, the rule, the platform, the policy version. That history is yours — and it compounds. Inputs are competitors' problem. Provenance is your moat.

“Operators of online platforms shall implement reasonable measures to protect minors from harm — measured, audited, and made transparent.”

KOSA · S.1409 · §3(a)
Enacted Mar 2026

The Stack

Nine capabilities. Every child-safety rule maps to one.

96 categories · 87 statutes

The interoperability layer

Inputs, not competitors.

Phosra is the interoperability layer for child safety. It orchestrates above every other system — native parental controls, OS-level age signals, DNS providers, MDM consoles, parental-controls vendors — and routes the right rule to whichever surface can carry it. The categories below describe the input shapes Phosra is designed to consume.

Parental-control apps

Phosra orchestrates above existing parental-controls vendors — they remain the user-facing surface; Phosra is the reasoning layer.

Bark, Qustodio, others — connected as Source integrations

Device & OS

Phosra reads Apple/Google/Samsung/Microsoft age signals (e.g., CA AB 1043) and routes rule categories like os_age_signal_ingest to them natively.

Tracking Apple, Google, Samsung, Microsoft public roadmaps

Platforms

Phosra reads each platform's controls surface and routes social_media_age_gate, content_filtering, and 100+ other rules to native APIs where available; Phosra services fill the rest.

229 platforms in the registry · 6 live integrations · public roadmap

Standards & civil society

Rule authorities, conformance auditors, youth advocates — Phosra publishes the protocol; these counterparts feed it the signal.

Public review process

No logos shown until adopters sign. Phosra publishes the protocol, not endorsements. See adoption status · Read the spec

The Brief

What changed in child-safety for your fleet today.

The Brief is the in-dashboard surface where Phosra’s continuous reading of laws, platforms, and CSM tiers reaches your team — prioritized by impact on the minors you actually protect.

Law2026-05-12

NY S9051 took effect.

AI companionship prohibition. Phosra has staged 2 policy changes for review across your affected fleet.

Affected

3,412 minors

Platform2026-05-08

Roblox shipped age-gate v2.

Now nativable for social_media_age_gate. Phosra can drop its fallback enforcement on this surface for 312 devices.

Affected

312 devices

CSM tier2026-05-10

Discord: Pass → Warning.

Your csm_privacy_tier_gate rule will start failing for protected accounts on this platform unless re-tiered.

Affected

1,108 accounts

See the Brief in your dashboard Read the public weekly digest Talk to a Partner Engineer

Sample items shown for illustration. Live Brief items are computed per-org against the minors and devices on your fleet — or read the public industry-wide digest at /weekly.

The registry the engine reads

91 statutes.
104 cross-jurisdiction categories.
The structured signal Phosra reasons over.

Every statute Phosra watches resolves to a machine-checkable rule category. Every rule category resolves to an enforcement surface. The registry below is the input side of the loop — not the product, but the structured signal the product reasons over.

Statutes mapped

Countries covered

104

Rule categories

OCSS capabilities

See conformance Browse the registry

Three steps to integration.

From zero to conformant in days, not quarters.

OCSS Spec Binding

Version

v1.0

Jurisdictions3 selected

US-CAEUUKBRAU

42 rules bound

3 jurisdictions · v1.0 pinned

Six lines.

One protocol. One SDK. Three calls.

import { phosra } from "@phosra/sdk";

const age     = await phosra.age.identify(req);
const audit   = await phosra.tier.evaluate({ age, jurisdiction: "US-CA" });
const receipt = await phosra.receipt.sign(audit);

✓ audit.allow   = false
✓ audit.cited   = ["KOSA-§4(b)(2)", "CA-AADC-§22675"]
✓ receipt.id    = "rcpt_018d4cb13f…"

Phosra is also an MCP server. Agents, advisors, and partner systems read and write the same rule layer.

See the full reference

For developers

One API. Every rule. Every jurisdiction.

Conform once and stay conformant. The CLI, SDK, and registry stay in lockstep with the Charter. Receipts ship signed, regulator-ready.

Read the docs →View on GitHub

REGISTRY96 categories · live

JURISDICTIONS27 (US-fed, US-states, EU, UK, AU, BR, IN…)

AVERAGE LATENCY11ms p50 · 38ms p99

RECEIPT FORMATEIP-712-style signed envelope

import { phosra } from "@phosra/sdk";

// Age returns the canonical age signal for a user
const age = await phosra.age.identify(req);

// Tier returns the rule set that applies, given age + jurisdiction
const audit = await phosra.tier.evaluate({
    age,
    jurisdiction: "US-CA",
    capability:   "recommender",
});

// Receipt signs the decision so a regulator can replay it later
const receipt = await phosra.receipt.sign(audit);

✓ audit.allow      = false
✓ audit.cited      = ["KOSA-§4(b)(2)", "CA-AADC-§22675"]
✓ receipt.id         = "rcpt_018d4cb13f…"

On-ramps

Start with parental-control apps.

Four roles share one protocol. Parental-control apps are the natural first integration — they consume the Age and Tier signals every other surface produces. The other three doors open as the network matures.

Parental-controls apps

START HERE