Last updated: 2026-06-09. A live record of OpenWOP-compatible hosts — their advertised compatibility profiles and the conformance evidence behind each claim. A row is a claim plus evidence: the claim is the host's advertised profile; the evidence is the conformance result published with the host (or under
conformance.md).
Hosts
| Host | Use case | Repo / Path | Compatibility profile claim | Scale claim | Production profile claim | Conformance link |
|---|---|---|---|---|---|---|
| In-memory (reference example) | Local development / fastest boot / no persistence | examples/hosts/in-memory/ | openwop-core · openwop-stream-sse · openwop-stream-poll | minimal | Not claimed | conformance.md |
| SQLite (reference example) | Single-machine durability / process-restart-safe | examples/hosts/sqlite/ | openwop-core · openwop-stream-sse · openwop-stream-poll · openwop-audit-log-integrity · openwop-interrupt-quorum · openwop-interrupt-auth-required · openwop-interrupt-external-event · openwop-interrupt-cascade-cancel · openwop-auth-api-key-rotation · openwop-discovery-auth-scoped | minimal | Not claimed | conformance.md |
| Python in-memory (reference example) | Cross-language portability — Python 3.11 stdlib-only port | examples/hosts/python/ | openwop-core · openwop-stream-sse · openwop-stream-poll | minimal | Not claimed | conformance.md |
| Postgres (reference example) | Multi-process durability + first production-profile host | examples/hosts/postgres/ | openwop-core · openwop-stream-poll · openwop-stream-sse · openwop-audit-log-integrity · openwop-interrupt-quorum · openwop-interrupt-auth-required · openwop-interrupt-external-event · openwop-interrupt-cascade-cancel · openwop-production · openwop-auth-oauth2-client-credentials · openwop-auth-oidc-user-bearer · openwop-auth-mtls · openwop-auth-api-key-rotation · openwop-discovery-auth-scoped (auth profiles conditional on env) | minimal | Claimed (since 2026-05-11) | conformance-full.md |
MyndHyve workflow-runtime (steward-affiliated sibling host — separate deployment, same maintainer org; not an independent-organization host, per the GOVERNANCE.md §"Acceptance evidence tiers" taxonomy this is tier-2 evidence) | Production agent-platform deployment whose live advertisements drove the RFC 0078–0094 Active → Accepted graduations | Closed source; live discovery: https://api.myndhyve.ai/.well-known/openwop | openwop-core · openwop-interrupts · openwop-stream-sse · plus the operational-annex claims openwop-core-standard (RFC 0088) and openwop-agent-platform full (RFC 0085) in its live profiles[] | Not published | Not claimed | Per-RFC graduation evidence in the Updated fields of RFCS/0078–0094 + the CHANGELOG.md 1.1.7/1.1.8 graduation entries (RFC 0093/0094: revision 00476-xuv, suite 1.22.0, 2026-06-11) (gated scenarios pass non-vacuously under OPENWOP_REQUIRE_BEHAVIOR=true; steward-curl-verified; the steward independently re-derived the profile predicates from the public discovery document) |
Agent Platform profile (RFC 0085 — openwop-agent-platform)
The aggregate platform profile defined in spec/v1/agent-platform-profile.md (RFC 0085, Accepted 2026-06-01). A host populates the status column when it reaches partial/full. MyndHyve — the steward-affiliated sibling host whose graduation evidence accepted the RFC — derives full; no example reference host claims it yet (honest).
| Host | openwop-agent-platform status | Notes |
|---|---|---|
MyndHyve workflow-runtime | full | Advertises the profile in its live profiles[]; the steward independently re-derived isAgentPlatformFull from the public discovery doc (all 16 §B terms) and the aggregate-evidence scenario passes non-vacuously at tier full — see RFC 0085's Updated field. Steward-affiliated sibling host (same maintainer org). |
| In-memory | none | Advertises feedback + several floor constituents, not the full floor set. |
| SQLite | none | — |
| Python | none | — |
| Postgres | none (candidate) | Already production-profile-satisfying and advertises memory / authorization / httpClient — the natural first partial/full candidate. |
Connection packs (RFC 0095 — capabilities.connections.packsSupported)
The portable provider-definition pack kind defined in spec/v1/connection-packs.md (RFC 0095, Accepted 2026-06-12). A host populates the status column when it advertises connections.packsSupported: true and implements the §Manifest clause 6 resolution contract; verification is the two capability-gated behavioral scenarios (connection-provider-resolution + connection-pack-write-reconsent) run non-vacuously against the published suite.
| Host | connections.packsSupported status | Notes |
|---|---|---|
| openwop-app reference | live + strict-verified | §B.6 loader-path resolution (openwop-app#178) + §10 test seams (#194) deployed rev 00160-kjq; connections.packsSupported advertised live (steward curl-verified on the direct run.app URL; seams correctly 404 in production). All five 1.23.0 scenarios pass NON-VACUOUSLY (OPENWOP_REQUIRE_BEHAVIOR=true) against a seam-enabled instance at the deployed code. |
MyndHyve workflow-runtime | live + strict-verified | §B.6 publish-path resolution (myndhyve#167/#168) + §10 seams (#169) serving on api.myndhyve.ai (revision workflow-runtime-00268-x9l); connections.packsSupported advertised live (steward curl-verified). All five 1.23.0 scenarios pass NON-VACUOUSLY (OPENWOP_REQUIRE_BEHAVIOR=true) over the live seams — the RFC 0095 Active → Accepted non-steward evidence. |
| In-memory | none | — |
| SQLite | none | — |
| Python | none | — |
| Postgres | none | — |
Localized content surface (RFC 0103 — capabilities.content.supported)
The capability-gated authored-content surface defined in spec/v1/localized-content.md (RFC 0103, Accepted 2026-06-17). A host populates the status column when it advertises content.supported: true (requires i18n.supported) and serves GET /v1/content/pages/{slug} with the §C resolveSection merge; the always-on legs of localized-content-delivery.test.ts verify the schemas + merge + capability coherence server-free, and the gated legs verify live delivery + tenant isolation.
| Host | content.supported status | Notes |
|---|---|---|
| openwop-app reference | live + non-vacuous | HOST-1 i18n.md annex (Accept-Language/Content-Language/capabilities.i18n) + HOST-2 content surface (content/resolve.ts resolveSection, /v1/content/*, SQLite/Postgres-backed, §F tenant-scoped); content { baseLocale:'en', supportedLocales:['es','pt-BR','fr'] } advertised on prod rev 00234-mg8 (app.openwop.dev, steward-curl-verified; main 999bfd0f, PR #412 / ADR 0064). Ran localized-content-delivery 18/18 NON-VACUOUSLY (incl. the live §A-coherence leg) — the second non-steward witness, closing the RFC 0103 content dual-witness bar. |
MyndHyve workflow-runtime | live + non-vacuous | Layer 1 (annex) + Layer 2 (content/resolveSection.ts + /v1/content/* over the Firestore CMS, credential-derived tenant per §F); content { baseLocale:'en', supportedLocales:['es','pt-BR','fr'] } advertised at doc root on prod rev 00273-6rf (api.myndhyve.ai, steward-curl-verified). Ran localized-content-delivery 18/18 NON-VACUOUSLY (incl. the live §A-coherence leg) + i18n-negotiation 4/4 — the Active → Accepted non-steward witness leg. |
| In-memory | none | — |
| SQLite | none | — |
| Python | none | — |
| Postgres | none | — |
Conformance pass rates
Measured against @openwop/openwop-conformance@1.22.0 (the published suite has since advanced to 1.25.0 — 1.23.0 added the +5 RFC 0095 connection-pack scenarios, 1.24.0 the RFC 0096/0097/0098 scenarios, and 1.25.0 the RFC 0099/0100 scenarios; all are capability-gated and soft-skip on these reference hosts (which advertise none of those surfaces), so applicable rates are unchanged, and the table below re-measures on the next suite cycle) — all five hosts measured 2026-06-11, then re-measured the same day after the gap-closure fixes landed (openwop-examples#7 + openwop-app#164): the morning run's findings — the RFC 0093 §A3 webhook-tenant-isolation registration-gate gap on SQLite/Postgres/Python, the Python RFC 0058 runTimeoutMs gap, and the workflow-engine's 12 long-carried pre-existing failures — were all root-cause fixed and verified. Current posture: zero deterministic failures on the workflow-engine, Postgres, SQLite, and Python hosts; the in-memory host's 45 failures remain its documented honest-non-claim set (advertised-fixture surfaces the minimal host doesn't implement). Modes: in-memory/python/postgres default (Postgres via pglite), SQLite strict with honest profile/fixture opt-outs, workflow-engine in-process serial. Suite total 1963. Measurement basis: full 82-fixture catalog (fixture resolution now env-overridable + sibling-probing and loud on fallback — the silent degraded loading of pre-1.22.0 readings is fixed). Pass rate is passed/total.
| Host | Passed | Failed | Skipped | Todo | Total | Pass rate (default) |
|---|---|---|---|---|---|---|
| Workflow-engine reference (in-process, post-#164) | 1872 | 0 | 91 | 0 | 1963 | 95.4% |
| Postgres reference | 1848 | 0 | 115 | 0 | 1963 | 94.1% |
| SQLite reference (strict) | 1826 | 0 | 137 | 0 | 1963 | 93.0% |
| In-memory reference | 1793 | 45 | 125 | 0 | 1963 | 91.3% |
| Python reference | 1786 | 0 | 177 | 0 | 1963 | 91.0% |
Composition partners — interop evidence
The conformance suite's MCP and A2A probes run against live reference implementations of the adjacent protocols. See A2A vs MCP vs OpenWOP for how the three layers compose.
| Partner | Reference impl | Sync round-trip | Async / durable (RFC 0100) |
|---|---|---|---|
| MCP | @modelcontextprotocol/sdk@1.29.0 (all three transports) | ✅ pass | — |
| A2A | @a2a-js/sdk@0.3.13 reference peer (echo skill, JSON-RPC) | ✅ 1/1 pass (a2a-task-roundtrip.test.ts) | ⏳ corpus landed (capabilities.a2a + A2ATaskState + durable-tasks/get/resubscribe/push subtests); reference-host durable-Task evidence at Active → Accepted |
Reading Rows
- Compatibility profile claim is derived from
/.well-known/openwopaccording tospec/v1/profiles.md. - Scale claim follows
spec/v1/scale-profiles.md. - Production profile claim follows
spec/v1/production-profile.mdand is recorded separately because durability, retention, backpressure, and observability are operational evidence, not discovery-payload predicates. - Conformance evidence should name the suite version, command used, target URL class, and pass/fail/skip counts. Do not include private deployment identifiers, secrets, or internal result paths.
Add A Host
1. Implement the openwop v1 wire contract. 2. Run @openwop/openwop-conformance against the host. 3. Publish a result file or Markdown summary in a public repository. 4. Add a row above with compatibility, scale, production-profile, and evidence claims.
See Also
conformance/README.md— how to run the suite.spec/v1/profiles.md— compatibility profile predicates.spec/v1/scale-profiles.md— scale tier definitions.spec/v1/production-profile.md— public-release operational profile.