Design-partner beta and production roadmap
Phosra does not claim a production OCSS federation, current accreditation, current certification, or customer deployments on a shared network. This page separates the evaluation surfaces available now from the production capabilities still being designed.
OCSS Draft 4 is an independent pre-release draft intended for standards-track submission. It has no official IETF Datatracker record. Phosra remains the steward of record while the proposed transfer to independent governance is incomplete.
What is available now
| Surface | Current purpose |
|---|---|
| Local SDK and gatekeeper evaluation | Exercise policy evaluation in your own process. |
| Live, no-signup sandbox | Test documented flows with synthetic identities and data. |
| Public rule and compliance registries | Inspect the current vocabulary and legal mappings. |
| Sample signed artifacts | Inspect representative signatures and receipt shapes. |
Sandbox identities, providers, Trust List entries, signatures, and receipts are test fixtures. They are not evidence that a real provider, platform, accreditor, or customer has joined a production network.
Design-partner beta
The design-partner beta is for teams with a concrete child-safety workflow that can help define a responsible pilot. A design partnership can include:
- hands-on integration scoping and support;
- adapter and workflow co-design;
- joint pilot success criteria and a documented production path; and
- direct access to the product and standards team.
Apply through the design-partner beta or email [email protected]. Include the workflow you want to evaluate, the systems involved, and the evidence that would make a pilot useful.
Interim production network
There is no public interim production federation or customer traffic rail to configure today. Do not point an application at an undocumented host, treat a sandbox root as a production trust anchor, or interpret synthetic DIDs as accredited organizations.
Hosted decision routing between verified participants, broader production receipt-rail availability, additional adapters, and certification pathways are roadmap items. A design-partner pilot may help define those interfaces, but participation does not confer accreditation, certification, or permission to display a conformity mark.
Evaluation path
- 1Inspect the available surfaces
Run the sandbox, review the rule registry, and inspect the sample signed artifacts.
- 2Define one bounded workflow
Identify the policy input, local decision point, expected result, and evidence your team needs to review.
- 3Apply for the design-partner beta
Share that workflow and agree on pilot success criteria with the Phosra team.
- 4Document the production boundary
Record which parts can run locally today and which hosted routing, receipt, adapter, governance, or certification dependencies remain roadmap.
Accreditation and certification language
The OCSS draft describes roles, trust-list fields, conformance evidence, and possible accreditation lanes. Those protocol concepts do not establish a currently operating independent accreditor or a production certification program. Phosra does not self-certify, and a sandbox or design-partner result is not an accreditation decision.
Any future certification pathway would require published criteria, an identified independent decision-maker, auditable evidence, and explicit permission to use any mark. Until that exists, describe results precisely as local evaluation, sandbox testing, sample-artifact inspection, or a design-partner pilot.