v2 defines three profiles. A host holds a profile when its discovery document advertises every family the profile names and the profile's floor scenarios pass. Anything else a host supports is advertised as its own capability, not as another profile.
openwop-discovery-core
The host publishes a valid v2 discovery document and negotiates the protocol version; it makes no claim about running workflows.
- Families required: none
- Discovery keys required:
protocolVersions,preferredVersion
The 3 floor scenarios
v2-capabilities-root-closedv2-preferred-version-defaultv2-version-header-honored
openwop-core-standard
The host runs workflows to the executable floor: interrupts, replay, webhooks, idempotency and the event log. This is what an unqualified "OpenWOP conformant" claim means.
- Families required:
interrupt,replay,webhooks,idempotency,eventLog
The 14 floor scenarios
v2-interrupt-token-schemev2-effect-seam-manifestv2-webhook-durable-deliveryv2-idempotency-key-grammarv2-era-keyv2-era-stamp-universalv2-event-type-closedv2-poll-cursor-v2v2-run-cancelv2-run-bulk-cancelv2-run-pause-resumev2-run-options-limitsv2-sse-last-event-idv2-sse-last-event-id-cursor
openwop-conformance-seams-v2
The host mounts the conformance test seams under /conformance/seams/ so the suite can drive seam-based scenarios; it is a testing surface, not a production feature.
- Families required: none
- Discovery keys required:
conformance.seamsProfile
The 4 floor scenarios
v2-fork-a-v1-runv2-effect-identity-business-keyv2-v1-signed-webhook-acceptedv2-effect-seam-no-refire
_Generated from spec/v2/profiles.json at build time._