Platform Conformance

The platform conformance surface is the public contract used to validate shared Durable Workflow behavior across the server, worker protocol, CLI, official SDKs, and operator surfaces. It gives implementers a stable place to find the suite manifest, the runtime scenario catalogs, and the pass / fail vocabulary used by conformance harnesses.

This route is a discovery page for the public conformance surface. It does not change the default documentation line: /docs/ continues to resolve to the stable 1.x documentation. The full prerelease conformance authority is the Platform Conformance Suite page in the explicit 2.0 prerelease docs.

Executed Run Ledger​

The ledger's snapshot_refreshed_at records when its current artifact tuple and derived freshness projection were generated or refreshed. retained_evidence_captured_at records when the bounded evidence source was captured. Artifact-tuple refreshes advance only the snapshot timestamp; they do not rewrite retained runs, their finished_at values, artifact attachments, or per-run evidence documents.

Public Manifests​

Stable Fixture Authorities​

The suite manifest binds each authority below to its versioned artifact_id, deterministic HTTPS resolver_url, and expected sha256. Consumers should reject fetched bytes that do not match the suite binding.

The active worker-protocol fixture follows the lifecycle-neutral catalog authority. The prior beta-worded bytes are retained only by the manifest's separate durable-workflow.v2.worker-protocol-api@catalog-16-beta-history identity and are not an active fixture source.

Planned Waterline observer and MCP discovery categories remain provisional and non-normative until a later suite version explicitly promotes them.

How Harnesses Use This Surface​

Conformance harnesses should fetch the suite manifest first, then load each runtime scenario manifest named by the fixture catalog for the implementation targets they claim. Runtime results should record concrete published artifact versions, the suite version, scenario ids, observed outputs, and one status per required scenario: pass, fail, unsupported, not_covered, or runner_blocked.

Passing conformance for a stable runtime category requires every required scenario in that category to pass. A smoke subset, missing scenario, unresolved artifact version, unsupported claimed surface, or environment-blocked cell is not full conformance for that category.

Release Status​

Stable 1.x remains the default public documentation line. The explicit 2.0 prerelease docs and platform conformance manifests describe the prerelease compatibility surface for implementations that claim those server, protocol, SDK, CLI, or operator contracts.