One standard.
Two independent layers.

A shared vocabulary defines what a protection means. A signed trust framework defines how it moves and who can be verified.

Explore all 133 rules →Assign a technical lead

Independent Rules and Trust layers overlap to form a shared envelope that seals a protection to one receiver.

Vocabulary133rule categories

Registry8populated capability groups

Regulatory map91laws

Coverage30+jurisdictions

The architecture

Each layer evolves without breaking the other.

Vocabulary can grow while routing hardens. The payload and transport version independently, keeping implementations stable as the standard matures.

01 / Vocabulary

OCSS Rules

One machine-readable registry of protection meanings, constraints, legal mappings, and expected surface behavior.

parental_consent_gatenot_for_minors_blockos_age_signal_ingestalgorithmic_audit

Open the rules registry →

02 / Routing + trust

OCSS Trust Framework

A signed outer envelope routes a sealed protection to a surface that verifies the emitter against a public Trust List.

ED25519JWEDIDRECEIPT

Inspect the trust contract →

The lifecycle

One protection, seven observable stages.

The same canonical flow appears everywhere—from executive overview to conformance evidence.

One protection changes continuously through selection, composition, sealing, signing, routing, enforcement, and receipt.

Central invariantCarriers route the envelope. They never read the protection.

Only the named destination can open the inner JWE. A signed, PII-free receipt proves what happened without creating a shadow identity graph.

Vocabulary ↔ law

Every category resolves to an obligation.

The crosswalk turns fragmented regulation into a shared implementation surface.

OCSS categoryRepresentative obligationSurfaceStatus

parental_consent_gateCOPPAPlatformMapped

not_for_minors_blockUK OSAApp storeMapped

os_age_signal_ingestCA AB 1043Device / OSMapped

algorithmic_auditKOSAPlatformReview

Implementation contract

Build once. Graduate without rebuilding.

Self-attested and accredited implementations use the same wire format, vocabulary, and endpoint. The difference is independently verified evidence.

SPECOCSS Draft 4Published · v0.4 JSONRules registryPublished · 133 rules

SCHEMAEnvelope schemaVersion 0.4 · Planned

TESTReference vectorsReproducible · Planned

Technical evaluation

Put Draft 4 in front of your platform team.

Start with the specification, then map one existing child-safety integration to the OCSS contract.

Open the evaluation package Talk to the working group

One standard.Two independent layers.