Draft 4 is open for reviewEvaluate with your platform team
OCSSOpen Child Safety
Sign in

The coordination layer for child safety

One protection standard. Every surface.

OCSS gives apps, platforms, operating systems, and networks one verifiable way to exchange and enforce child-safety protections.

Explore rules

OCSS working group

Start a conversation.

Tell us who you are and we’ll follow up directly—no mailing list or automated sequence.

Your details go directly to the OCSS working-group lead.

Open specification · Royalty-free · Vendor-neutral governance

SAFETY APPPROTECTEDreceiver-boundBLIND ROUTE · SEALED CONTENTENFORCESIGNED RECEIPTOSNETWORKBROWSERPLATFORM
A receiver-bound protection moves through a blind route, is verified at the enforcement surface, and returns a signed receipt.
Current statusDraft 4open review
Typed vocabulary133search the registry →
Regulatory map91laws · 30+ regions
Governance1:1one org · one vote

The platform case

Stop paying the integration tax.

Child-safety apps and enforcement surfaces are wired together one contract at a time. OCSS replaces the mesh with one shared protocol.

TodayN × M

Every pair negotiates its own integration.

4 APPS4 SURFACESA1A2A3A4S1S2S3S416 AGREEMENTS
Four apps connected to four surfaces through sixteen bilateral agreements.

Duplicated contracts · inconsistent semantics · fragmented evidence

With OCSSN + M

Every participant implements once.

4 APPS4 SURFACESOCSSA1A2A3A4S1S2S3S48 IMPLEMENTATIONS
Four apps and four surfaces join through eight implementations of one shared contract.

One vocabulary · one trust contract · independent enforcement

One canonical flow

From a protection to verifiable enforcement.

The carrier moves the signal. The surface verifies and enforces it. No intermediary reads the child’s data.

ONE OBJECT · SEVEN MATERIAL STATES01 · Select02 · Compose03 · Seal04 · Sign05 · Route06 · EnforceSIGNED RECEIPT07 · Record
One protection changes continuously through selection, composition, sealing, signing, routing, enforcement, and receipt.
The central invariantRouting outside. Protection sealed inside.

Only the designated enforcement surface can open the typed protection. The signed receipt remains independently replayable without exposing a child.

Designed for platform adoption

Lower the risk before the first integration.

The standard’s governance and conformance model are part of the product—not an appendix to it.

OPEN

Royalty-free implementation

No license toll, proprietary gateway, or bilateral commercial agreement required.

View evidence
TEST

Binary conformance

Every obligation maps to observable behavior and a reproducible test vector.

View evidence
BLIND

Privacy in the architecture

Carriers route the envelope without opening or retaining a child’s protection data.

View evidence
GOV

No founder veto

One organization, one vote, with reserved civil-society participation.

View evidence
Charter not yet ratified9 committee seats3 reserved for civil societyQ3 2026 target

Adoption without theater

Progress you can inspect.

OCSS does not borrow credibility from unsigned logos. Until organizations formally participate, activity is measured through open artifacts, working groups, and reproducible evidence.

Open the live status page
Production accreditations0Published zero
Founding seats open12Open
Conformance harness7Assertions
SpecificationD4Draft
Last updated

Choose the right entry point

Bring the right team into the room.

OCSS separates executive evaluation, technical implementation, and standards participation so each group can move at the right depth.

Evaluation package

Every claim should resolve to an artifact.

PDF Executive adoption brief6 min readSPEC OCSS Draft 4VersionedJSON Rules registry133 categoriesTEST Conformance harnessOpen source

The next useful step

Evaluate OCSS with your platform team.

Bring an executive sponsor and a technical lead. We’ll map the standard to your surfaces, trust requirements, and adoption path.

Start a standards conversationReview Draft 4