@openwop/spec-artifacts 2.0.4 → 2.0.6

package/spec/v2/ext/chat/README.md

@@ -0,0 +1,20 @@
+# `chat` — extension
+
+| Field | Value |
+| --- | --- |
+| **witness:** | `claims-check` |
+| **technical:** | `experimental` |
+| **adoption:** | `single-witness` |
+| **peer-dependency id** | `chat` |
+| **advertised as** | `extensions.<org>.chat` (RFC 0169 §A.4) — never a root key |
+| **owning RFC** | RFC 0144 |
+
+> **Status: Draft · v2.0.0-rc (2026-09-03).** Extension document (RFC 0169 §B.3; RFC 0167 Axiom 1: a family that cannot be witnessed unaided lives here and is not a core obligation).
+
+## What it is
+
+RFC 0169 §B.3 (RFC 0144 extension class; prose-only §host.* section in v1; served under extensions.openwop-app.* by the one host that has it) The v1 prose that defines the surface is `spec/v1/host-capabilities.md` §host.chat (RFC 0144 extension class); it stands as the definition until this document carries its own normative text (P3-E and the Phase 4 host legs). A host that serves this surface advertises it under `extensions.<org>.chat` with the RFC 0169 record shape; a pack that requires it names `chat` in `peerDependencies` (RFC 0177 §B.1).
+
+## Witness
+
+`claims-check`: the suite can read the claim from discovery but has no behavioral probe; adoption is measured by the INTEROP-MATRIX bundle evidence.

package/spec/v2/ext/coordination/README.md

@@ -0,0 +1,20 @@
+# `coordination` — extension
+
+| Field | Value |
+| --- | --- |
+| **witness:** | `claims-check` |
+| **technical:** | `experimental` |
+| **adoption:** | `single-witness` |
+| **peer-dependency id** | `coordination` |
+| **advertised as** | `extensions.<org>.coordination` (RFC 0169 §A.4) — never a root key |
+| **owning RFC** | RFC 0144 |
+
+> **Status: Draft · v2.0.0-rc (2026-09-03).** Extension document (RFC 0169 §B.3; RFC 0167 Axiom 1: a family that cannot be witnessed unaided lives here and is not a core obligation).
+
+## What it is
+
+RFC 0169 §B.3 (RFC 0144 extension class; prose-only §host.* section in v1; served under extensions.openwop-app.* by the one host that has it) The v1 prose that defines the surface is `spec/v1/host-capabilities.md` §host.coordination (RFC 0144 extension class); it stands as the definition until this document carries its own normative text (P3-E and the Phase 4 host legs). A host that serves this surface advertises it under `extensions.<org>.coordination` with the RFC 0169 record shape; a pack that requires it names `coordination` in `peerDependencies` (RFC 0177 §B.1).
+
+## Witness
+
+`claims-check`: the suite can read the claim from discovery but has no behavioral probe; adoption is measured by the INTEROP-MATRIX bundle evidence.

package/spec/v2/ext/dataIntegration/README.md

@@ -0,0 +1,20 @@
+# `dataIntegration` — extension
+
+| Field | Value |
+| --- | --- |
+| **witness:** | `claims-check` |
+| **technical:** | `experimental` |
+| **adoption:** | `single-witness` |
+| **peer-dependency id** | `dataIntegration` |
+| **advertised as** | `extensions.<org>.dataIntegration` (RFC 0169 §A.4) — never a root key |
+| **owning RFC** | RFC 0144 |
+
+> **Status: Draft · v2.0.0-rc (2026-09-03).** Extension document (RFC 0169 §B.3; RFC 0167 Axiom 1: a family that cannot be witnessed unaided lives here and is not a core obligation).
+
+## What it is
+
+RFC 0169 §B.3 (RFC 0144 extension class; prose-only §host.* section in v1; served under extensions.openwop-app.* by the one host that has it) The v1 prose that defines the surface is `spec/v1/host-capabilities.md` §host.dataIntegration (RFC 0144 extension class); it stands as the definition until this document carries its own normative text (P3-E and the Phase 4 host legs). A host that serves this surface advertises it under `extensions.<org>.dataIntegration` with the RFC 0169 record shape; a pack that requires it names `dataIntegration` in `peerDependencies` (RFC 0177 §B.1).
+
+## Witness
+
+`claims-check`: the suite can read the claim from discovery but has no behavioral probe; adoption is measured by the INTEROP-MATRIX bundle evidence.

package/spec/v2/ext/entities/README.md

@@ -0,0 +1,20 @@
+# `entities` — extension
+
+| Field | Value |
+| --- | --- |
+| **witness:** | `claims-check` |
+| **technical:** | `experimental` |
+| **adoption:** | `single-witness` |
+| **peer-dependency id** | `entities` |
+| **advertised as** | `extensions.<org>.entities` (RFC 0169 §A.4) — never a root key |
+| **owning RFC** | RFC 0144 |
+
+> **Status: Draft · v2.0.0-rc (2026-09-03).** Extension document (RFC 0169 §B.3; RFC 0167 Axiom 1: a family that cannot be witnessed unaided lives here and is not a core obligation).
+
+## What it is
+
+RFC 0169 §B.3 (RFC 0144 extension class; prose-only §host.* section in v1; served under extensions.openwop-app.* by the one host that has it) The v1 prose that defines the surface is `spec/v1/host-capabilities.md` §host.entities (RFC 0144 extension class); it stands as the definition until this document carries its own normative text (P3-E and the Phase 4 host legs). A host that serves this surface advertises it under `extensions.<org>.entities` with the RFC 0169 record shape; a pack that requires it names `entities` in `peerDependencies` (RFC 0177 §B.1).
+
+## Witness
+
+`claims-check`: the suite can read the claim from discovery but has no behavioral probe; adoption is measured by the INTEROP-MATRIX bundle evidence.

package/spec/v2/ext/grpc-transport/README.md

@@ -0,0 +1,13 @@
+# `grpc-transport` — extension (demoted)
+
+| Field | Value |
+| --- | --- |
+| **witness:** | `unwitnessable` |
+| **technical:** | `experimental` |
+| **adoption:** | `none` |
+| **advertised as** | not advertisable — no `grpc` block exists at the v2 root (RFC 0175 §A.1; RFC 0169 §A.1) |
+| **owning RFC** | RFC 0175 (demotion); RFC 0094 §H (v1 text) |
+
+> **Status: Draft · v2.0.0-rc (2026-09-03).** RFC 0175 §A.1: `grpc-transport.md` leaves `core/`; the suite ships no gRPC client and no host advertises the block, so the transport is `unwitnessable`. Its six v1 MUSTs are SHOULDs of this extension. `openwop.proto` beside this file is a NON-NORMATIVE sketch (the v1 proto, unchanged; `package openwop.v1`). The door back into core is named: a v2.x additive RFC that generates the proto from `spec/v2/declaration.json` and lands a suite client.
+
+The v1 definition stands at `spec/v1/grpc-transport.md` for v1.x hosts.

package/spec/v2/ext/kanban/README.md

@@ -0,0 +1,20 @@
+# `kanban` — extension
+
+| Field | Value |
+| --- | --- |
+| **witness:** | `claims-check` |
+| **technical:** | `experimental` |
+| **adoption:** | `single-witness` |
+| **peer-dependency id** | `kanban` |
+| **advertised as** | `extensions.<org>.kanban` (RFC 0169 §A.4) — never a root key |
+| **owning RFC** | RFC 0144 |
+
+> **Status: Draft · v2.0.0-rc (2026-09-03).** Extension document (RFC 0169 §B.3; RFC 0167 Axiom 1: a family that cannot be witnessed unaided lives here and is not a core obligation).
+
+## What it is
+
+RFC 0169 §B.3 (RFC 0144 extension class; prose-only §host.* section in v1; served under extensions.openwop-app.* by the one host that has it) The v1 prose that defines the surface is `spec/v1/host-capabilities.md` §host.kanban (RFC 0144 extension class); it stands as the definition until this document carries its own normative text (P3-E and the Phase 4 host legs). A host that serves this surface advertises it under `extensions.<org>.kanban` with the RFC 0169 record shape; a pack that requires it names `kanban` in `peerDependencies` (RFC 0177 §B.1).
+
+## Witness
+
+`claims-check`: the suite can read the claim from discovery but has no behavioral probe; adoption is measured by the INTEROP-MATRIX bundle evidence.

package/spec/v2/ext/knowledge/README.md

@@ -0,0 +1,20 @@
+# `knowledge` — extension
+
+| Field | Value |
+| --- | --- |
+| **witness:** | `claims-check` |
+| **technical:** | `experimental` |
+| **adoption:** | `single-witness` |
+| **peer-dependency id** | `knowledge` |
+| **advertised as** | `extensions.<org>.knowledge` (RFC 0169 §A.4) — never a root key |
+| **owning RFC** | RFC 0144 |
+
+> **Status: Draft · v2.0.0-rc (2026-09-03).** Extension document (RFC 0169 §B.3; RFC 0167 Axiom 1: a family that cannot be witnessed unaided lives here and is not a core obligation).
+
+## What it is
+
+RFC 0169 §B.3 (RFC 0144 extension class; prose-only §host.* section in v1; served under extensions.openwop-app.* by the one host that has it) The v1 prose that defines the surface is `spec/v1/host-capabilities.md` §host.knowledge (RFC 0144 extension class); it stands as the definition until this document carries its own normative text (P3-E and the Phase 4 host legs). A host that serves this surface advertises it under `extensions.<org>.knowledge` with the RFC 0169 record shape; a pack that requires it names `knowledge` in `peerDependencies` (RFC 0177 §B.1).
+
+## Witness
+
+`claims-check`: the suite can read the claim from discovery but has no behavioral probe; adoption is measured by the INTEROP-MATRIX bundle evidence.

package/spec/v2/ext/launchStudio/README.md

@@ -0,0 +1,20 @@
+# `launchStudio` — extension
+
+| Field | Value |
+| --- | --- |
+| **witness:** | `claims-check` |
+| **technical:** | `experimental` |
+| **adoption:** | `single-witness` |
+| **peer-dependency id** | `launchStudio` |
+| **advertised as** | `extensions.<org>.launchStudio` (RFC 0169 §A.4) — never a root key |
+| **owning RFC** | RFC 0144 |
+
+> **Status: Draft · v2.0.0-rc (2026-09-03).** Extension document (RFC 0169 §B.3; RFC 0167 Axiom 1: a family that cannot be witnessed unaided lives here and is not a core obligation).
+
+## What it is
+
+RFC 0169 §B.3 (RFC 0144 extension class; prose-only §host.* section in v1; served under extensions.openwop-app.* by the one host that has it) The v1 prose that defines the surface is `spec/v1/host-capabilities.md` §host.launchStudio (RFC 0144 extension class); it stands as the definition until this document carries its own normative text (P3-E and the Phase 4 host legs). A host that serves this surface advertises it under `extensions.<org>.launchStudio` with the RFC 0169 record shape; a pack that requires it names `launchStudio` in `peerDependencies` (RFC 0177 §B.1).
+
+## Witness
+
+`claims-check`: the suite can read the claim from discovery but has no behavioral probe; adoption is measured by the INTEROP-MATRIX bundle evidence.

package/spec/v2/ext/messaging/README.md

@@ -0,0 +1,20 @@
+# `messaging` — extension
+
+| Field | Value |
+| --- | --- |
+| **witness:** | `claims-check` |
+| **technical:** | `experimental` |
+| **adoption:** | `single-witness` |
+| **peer-dependency id** | `messaging` |
+| **advertised as** | `extensions.<org>.messaging` (RFC 0169 §A.4) — never a root key |
+| **owning RFC** | RFC 0144 |
+
+> **Status: Draft · v2.0.0-rc (2026-09-03).** Extension document (RFC 0169 §B.3; RFC 0167 Axiom 1: a family that cannot be witnessed unaided lives here and is not a core obligation).
+
+## What it is
+
+RFC 0169 §B.3 (RFC 0144 extension class; prose-only §host.* section in v1; served under extensions.openwop-app.* by the one host that has it) The v1 prose that defines the surface is `spec/v1/host-capabilities.md` §host.messaging (RFC 0144 extension class); it stands as the definition until this document carries its own normative text (P3-E and the Phase 4 host legs). A host that serves this surface advertises it under `extensions.<org>.messaging` with the RFC 0169 record shape; a pack that requires it names `messaging` in `peerDependencies` (RFC 0177 §B.1).
+
+## Witness
+
+`claims-check`: the suite can read the claim from discovery but has no behavioral probe; adoption is measured by the INTEROP-MATRIX bundle evidence.

package/spec/v2/ext/portability/README.md

@@ -0,0 +1,11 @@
+# `portability` — extension (goals, export, import)
+
+| Field | Value |
+| --- | --- |
+| **witness:** | `claims-check` |
+| **technical:** | `experimental` |
+| **adoption:** | `none` |
+| **advertised as** | `extensions.<org>.portability` |
+| **owning RFC** | RFC 0168 (decided in C.1 per RFC 0174 §E.2), RFC 0086/0087 (v1 text) |
+
+> **Status: Draft · v2.0.0-rc (2026-09-03).** `/v1/goals`, `/v1/export`, `/v1/import` were absent from the v1 OpenAPI while `spec/v1/portability.md` and the goals prose described them (RFC 0174 §E.2 noted the decision belongs to C.1). Decided (Phase 3 plan §11): they do not enter `api/v2/openapi.yaml`; the export/import bundle (`schemas/v2/export-bundle.schema.json`, `bundleVersion` "2") and the goals surface are this extension, advertised under `extensions.<org>.portability`, with `spec/v1/portability.md` as the definition until a v2.x additive RFC lands their operations with a witness.

package/spec/v2/ext/provider-idempotency/README.md

@@ -0,0 +1,11 @@
+# `provider-idempotency` — extension (registry)
+
+| Field | Value |
+| --- | --- |
+| **witness:** | `witnessable-gated` |
+| **technical:** | `experimental` |
+| **adoption:** | `none` |
+| **advertised as** | not a discovery family — a data registry (`registry.json`) the Layer-2 obligation reads |
+| **owning RFC** | RFC 0173 §C.2, RFC 0150 G3 |
+
+> **Status: Draft · v2.0.0-rc (2026-09-03).** `registry.json` records which providers have a natural business-identity key (RFC 0173 §C.2: business-identity keying is the core obligation; the activity recipe is the documented fallback). Rows are measured by the Phase 4 host legs. The witness is `GET /runs/{runId}/effects` (`effect-ledger-projection.schema.json` `keying`).

package/spec/v2/ext/restTransport/README.md

@@ -0,0 +1,20 @@
+# `restTransport` — extension
+
+| Field | Value |
+| --- | --- |
+| **witness:** | `claims-check` |
+| **technical:** | `experimental` |
+| **adoption:** | `none` |
+| **peer-dependency id** | `restTransport` |
+| **advertised as** | `extensions.<org>.restTransport` (RFC 0169 §A.4) — never a root key |
+| **owning RFC** | RFC 0115 |
+
+> **Status: Draft · v2.0.0-rc (2026-09-03).** Extension document (RFC 0169 §B.3; RFC 0167 Axiom 1: a family that cannot be witnessed unaided lives here and is not a core obligation).
+
+## What it is
+
+RFC 0169 §C.5 (claims-check; ext/ unless a behavioral witness lands) The v1 prose that defines the surface is `spec/v1/capabilities.md` (root key `restTransport`, RFC 0113); it stands as the definition until this document carries its own normative text (P3-E and the Phase 4 host legs). A host that serves this surface advertises it under `extensions.<org>.restTransport` with the RFC 0169 record shape; a pack that requires it names `restTransport` in `peerDependencies` (RFC 0177 §B.1).
+
+## Witness
+
+`claims-check`: the suite can read the claim from discovery but has no behavioral probe; adoption is measured by the INTEROP-MATRIX bundle evidence.

package/spec/v2/ext/sandbox-runtime-notes/README.md

@@ -0,0 +1,11 @@
+# `sandbox-runtime-notes` — extension (non-normative)
+
+| Field | Value |
+| --- | --- |
+| **witness:** | `unwitnessable` |
+| **technical:** | `experimental` |
+| **adoption:** | `none` |
+| **advertised as** | not advertisable (notes, not a surface) |
+| **owning RFC** | RFC 0173 §D (RFC 0035 superseded by the `packs` obligation at the cut) |
+
+> **Status: Draft · v2.0.0-rc (2026-09-03).** RFC 0035's `node:vm` demonstrator and its runtime notes are kept here as implementation history. In v2 isolation binds with pack execution (`security-defaults.md`): `sandbox.isolationModel` names `wasm | process | container | vm`; `node:vm` is not a value (RFC 0035 §20, `:130`: escapable by design). A host MAY register and validate packs without executing them. RFC 0035 flips `Superseded` at the RC.

package/spec/v2/ext/webResearch/README.md

@@ -0,0 +1,20 @@
+# `webResearch` — extension
+
+| Field | Value |
+| --- | --- |
+| **witness:** | `claims-check` |
+| **technical:** | `experimental` |
+| **adoption:** | `single-witness` |
+| **peer-dependency id** | `webResearch` |
+| **advertised as** | `extensions.<org>.webResearch` (RFC 0169 §A.4) — never a root key |
+| **owning RFC** | RFC 0144 |
+
+> **Status: Draft · v2.0.0-rc (2026-09-03).** Extension document (RFC 0169 §B.3; RFC 0167 Axiom 1: a family that cannot be witnessed unaided lives here and is not a core obligation).
+
+## What it is
+
+RFC 0169 §B.3 (RFC 0144 extension class; prose-only §host.* section in v1; served under extensions.openwop-app.* by the one host that has it) The v1 prose that defines the surface is `spec/v1/host-capabilities.md` §host.webResearch (RFC 0144 extension class); it stands as the definition until this document carries its own normative text (P3-E and the Phase 4 host legs). A host that serves this surface advertises it under `extensions.<org>.webResearch` with the RFC 0169 record shape; a pack that requires it names `webResearch` in `peerDependencies` (RFC 0177 §B.1).
+
+## Witness
+
+`claims-check`: the suite can read the claim from discovery but has no behavioral probe; adoption is measured by the INTEROP-MATRIX bundle evidence.

package/spec/v2/release.json

@@ -1,6 +1,6 @@
 {
   "$comment": "RFC 0172 \u00a7D.1 \u2014 the one release identity the v2 artifacts derive from. `version` is the next corpus tag `v<version>` (the publish workflow's coordinated-release tag pattern `v*`; RFC 0172's `openwop/v2.<minor>.<patch>` spelling is amended to this at its flip). api/v2/*.yaml info.version, the suite's 2.x version and @openwop/spec-artifacts read it. Bumped by the release PR that cuts the tag, never by hand elsewhere.",
-  "version": "2.0.4",
-  "corpusTag": "v2.0.4",
+  "version": "2.0.6",
+  "corpusTag": "v2.0.6",
   "updated": "2026-09-05"
 }