OpenWOP — v2 spec corpus — Core

core/overview OpenWOP v2 Core — Overview spec/v2/core/ is what a host implements to pass the 2.0.0 floor: reading order, the six axioms, and rules other documents reference. Stable
core/capabilities Discovery and Capabilities A host advertises what it supports in one discovery document: one record type per family on a closed root, generated from one declaration… Stable
core/versioning Versioning and Release How a v2 host selects a major, what each version axis means, and what a release is. Stable
core/runs Runs Creating, reading, streaming, cancelling, pausing, forking and diffing a run. Every host projects the same snapshot from the same event log… Stable
core/events Events A run is its append-only event log. Every snapshot, stream, poll, fork and diff is a projection of it. Stable
core/errors Errors Every error a v2 host returns is a row in one registry. A client routes on error, never on message. A code that is not registered is not a… Stable
core/headers Headers Every non-standard header is named OpenWOP-<Name>, and every header is declared in OpenAPI. These tables are generated from that… Stable
core/idempotency Idempotency A retried request MUST NOT create a second run, and a retried node MUST NOT issue a second external effect. A host MUST implement Layer 1… Stable
core/identity Identity Who owns a run, how each lane binds and revokes, and the grammar of links, ids and tokens. Idempotency keys are in idempotency.md. Stable
core/oauth OAuth The host obtains, stores and refreshes the third-party tokens a connector node needs; a pack names a provider and scopes and never touches… Stable
core/interrupt Interrupt interrupt is how a run waits on something outside itself; every kind shares one payload shape, event pair, resolve contract and token… Stable
core/replay Replay and Fork POST /runs/{runId}:fork re-executes a past run state: a replay reproduces recorded history under current code; a branch explores an… Stable
core/persistence Persistence and Coexistence How a v2 host reads what a v1 host wrote, handles a run in flight at the cut, and maps each persisted store. Stable
core/webhooks Webhooks A client registers a URL and an event filter once; the host POSTs matching events, signed, as they happen, and durably. Stable
core/security-defaults Security Defaults In v2 a security behavior is not an opt-in flag. Each surface maps to the behavior it binds, its invariant and its witness. Stable
core/packs Packs Pack manifests, the registry tree, peer-dependency identifiers, and signing. Per-kind rules live in connection-packs.md,… Stable
core/node-pack-runtimes Node-pack runtimes The language a node pack runs in, and how a remote pack names its MCP server, by URL or an inline MCP Registry record. The shape is… Stable
core/host-services Host services Node packs call advertised host.* services through ctx. Each section states the contract a host accepts by advertising that family. Stable
core/tool-catalog Tool catalog A host's tool catalog lists the tools a caller may invoke, with a projection onto MCP ToolAnnotations. The shapes are… Stable
core/connection-packs Connection Packs A connection pack is a signed provider definition — the endpoints, scope catalog, and reach a connector's auth.provider string resolves… Stable
core/form-content-packs Form Content Packs A form-content pack ships declarative form templates a host renders in its own chrome. The manifest is… Stable
core/workflow-chain-packs Workflow Chain Packs A workflow-chain pack ships a reusable fragment a host expands into a concrete definition, and may compose other chains as co-registered… Stable
core/conversation Conversation surfaces No client route opens a conversation. These are the obligations of a host advertising these families. Stable
core/interop Interop A host advertises A2A and MCP, negotiates a version, and records every negotiation. Capability shapes are in capabilities.md; the peer… Stable
core/conformance Conformance How a requirement is asserted and witnessed, how seams mount, what the suite ships, and what a bundle proves. Profiles are in overview.md;… Stable