// conformance
Three levels. One executable kit.
Conformance in OASP is something you prove, not something you assert. Pick the level that matches what you’re building, then run the kit against it — the same suite every other implementation runs.
// the levels
What each level requires
L1 Client
consumes OASP
✓ publish and send against a Conversation.
✓ stream Events as they append.
✓ follow a migration without dropping the thread.
✓ present one continuous Conversation to the user.
L2 Server
hosts the protocol
✓ host Conversations and Sessions.
✓ implement migrate and drain.
✓ enforce scope-pinned identity and containment.
✓ MUST emit AuditEvents for every consequential action.
L3 Adapter
bridges a runtime
✓ map a non-OASP runtime’s native sessions to OASP Sessions.
✓ translate native events into OASP Events.
✓ MUST emit AuditEvents across the bridge.
✓ expose migrate/drain where the runtime allows.
// requirement matrix
Capability by level
MUST required SHOULD recommended — not applicable
// conformance kit
Prove it by passing.
The conformance kit is an executable test suite you point at your implementation. It exercises every MUST for the level you claim and reports a signed result.
A passing run is what earns a listing on Implementations — conformance is demonstrated, not declared.
Get listed →