This file is the canonical record of who has merge authority on github.com/openwop/openwop and what's expected of them. The maintainer set drives the decision rules in GOVERNANCE.md and the RFC process in RFCS/.
Recruitment of additional maintainers is out of band: this file documents the criteria and the process. It does not commit to a hiring schedule. The vendor-neutral-org migration tripwire in
ROADMAP.mdactivates when this file lists at least one maintainer not affiliated with the original steward.
Current maintainers
| Name | GitHub | Affiliation | Role | Active since |
|---|---|---|---|---|
| David Tufts | @davidscotttufts | OpenWOP | Lead maintainer | 2026-04 |
The lead maintainer is the tiebreaker for unresolved disagreement (per GOVERNANCE.md §"Decision making"). The lead-maintainer role is transitional and is replaced by a steering-committee vote once the path-to-working-group conditions in GOVERNANCE.md are met.
Maintainer expectations
A maintainer is expected to:
- Respond. Acknowledge issues and pull requests in their area within five business days. Acknowledgment may be a substantive reply or a "I'll get to this by ~date" — silence is the failure mode this rule exists to prevent.
- Gate quality. Merge only changes that pass the CI gates listed in
CONTRIBUTING.md§"The CI gate." A failing CI run is never a "fix-forward" rationale onmain. - Follow the spec change process. Per
GOVERNANCE.md§"Spec change process" — editorial / non-normative-addition / normative-addition / breaking each have their own decision rule and comment window. RFCs followRFCS/0001-rfc-process.md. - Disclose conflicts. Any commercial relationship, funding source, or employment that could bias a decision is disclosed in the PR or RFC thread. Recusal is the default for direct conflicts.
- Honor compatibility. Apply
COMPATIBILITY.mdstrictly. A major stays additive-only by default (§2, §2.4); safety/security breaks follow the §3 process; everything else waits for the next major. - Update governance docs in lockstep. Changes to maintainer status (additions, removals, role changes) update this file via PR. Changes to
GOVERNANCE.mddecision rules go through the RFC process. - Uphold registry policy. Maintainers acting as registry approvers apply the submission, trust-tier, and signing rules in
RFCS/0043-registry-and-extension-policy.md§B (indexed atdocs/governance/registry-policy.md) — including the registry-root-key rotation dual-control requirement (§B.4).
Promotion process
A contributor becomes a maintainer through these steps:
- Sustained contribution. Six months of substantive review or PR activity on the openwop corpus. "Substantive" means non-trivial spec / schema / SDK / conformance contributions, not just typo fixes.
- Nomination. An existing maintainer opens a PR adding the contributor to this file. The PR explains why the contributor meets the criteria.
- Lazy-consensus window. Seven calendar days during which any existing maintainer may object. Substantive objections move the proposal to a discussion in the PR thread; unresolved objections are settled by lead-maintainer tiebreaker per
GOVERNANCE.md. - Onboarding. The new maintainer is added to repository admin, CODEOWNERS for their declared area, the security advisory team (
SECURITY.md), and announced inCHANGELOG.mdunder### Governance.
A contributor may decline maintainer nomination at any time without explanation.
Stepping down
A maintainer may step down by opening a PR that:
- Moves their entry from "Current maintainers" to "Past maintainers" below.
- Lists their last active month.
- Optionally hands off ownership of any RFCs or open PRs in their queue.
Stepping down is acknowledged by lazy consensus (the PR merges with one approval). Past maintainers are not silently removed — the table preserves the history.
Removal for cause
A maintainer may be removed by lazy consensus of the remaining maintainers for:
- Sustained inactivity. No substantive activity for six months, with no advance notice.
- Code-of-conduct violation. Per
CODE_OF_CONDUCT.md. Removal is by majority of remaining maintainers; the lead maintainer recuses if the violation involves them. - Conflict-of-interest violation. Failure to disclose a conflict that materially affected a decision. Removal follows the code-of-conduct process.
A removed maintainer's entry moves to "Past maintainers" with a brief note on the removal reason. The note is factual; it doesn't repeat any private investigation detail.
Affiliation policy
Maintainers list their primary affiliation in the table. The affiliation field exists so:
- Cross-organization decision rules (per
GOVERNANCE.md§"Decision making" — required for breaking changes once multiple orgs are represented) can be evaluated. - External implementers can assess governance neutrality.
- The vendor-neutral-org migration tripwire in
ROADMAP.mdcan be checked mechanically.
A maintainer who changes affiliation updates this file in the same PR. Multiple affiliations may be listed if they're material to recusal decisions.
Past maintainers
_None yet._
Recruitment log
The vendor-neutral-org migration tripwire in ROADMAP.md activates when this file lists ≥1 maintainer not affiliated with OpenWOP. Recruitment is out-of-band: this section tracks attempts (and their outcomes) so the project's recruitment posture is auditable, but it doesn't commit to a hiring schedule.
External host implementations
Recruitment targets per docs/recruitment/external-host.md. The drafts are ready and sendable, with zero unfilled placeholders and every quoted figure pointing at a dated, re-derivable measurement. Outreach has not been sent. Sending it is the tripwire for RFC 0035 and RFC 0038 both; neither is blocked on the world having declined, only on nobody having asked.
| Target | Outreach sent | First reply | Status | Notes |
|---|---|---|---|---|
| LangChain / LangGraph adapter | — | — | Drafted | Tier 1; cites README's six-borrowed-idioms section. See docs/recruitment/external-host.md §"Tier 1". |
| Restate | — | — | Drafted | Tier 2; durable-execution-runtime fit. |
| DBOS | — | — | Drafted | Tier 3; Postgres-native transactional workflows. |
| Inngest | — | — | Drafted | Tier 4; TS-native event-driven runtime. |
When a target replies positively + commits to a draft adapter PR within 30 days, move their row's status to in-progress. When their host appears on INTEROP-MATRIX.md, status → live.
External pack authors
Recruitment targets per docs/recruitment/external-pack-author.md (drafts ready; outreach not sent). Initial Tier-1 shortlist below; the recruitment doc's criteria gate adding more.
| Target | Outreach sent | First reply | Status | Notes |
|---|---|---|---|---|
Linear (Issues / Cycles API → vendor.linear.workflows) | — | — | Pending outreach | Tier 1: dev-tools vendor with workflow-shaped public API. Best fit: Linear's GraphQL issueCreate + cycleCreate mutations as openwop nodes. |
Sourcegraph (Code Search / Cody → vendor.sourcegraph.code-search) | — | — | Pending outreach | Tier 1: code-intelligence vendor; an existing MCP server can be wrapped as an openwop pack for the workflow surface. |
Vercel (Build / Edge Functions → vendor.vercel.deploy) | — | — | Pending outreach | Tier 1: deploy-on-workflow-event is a common HITL pattern. |
Resend (transactional email → vendor.resend.send) | — | — | Pending outreach | Tier 1: smallest possible pack scope (1 node, 1 envelope); good first-pack proof point. |
Stripe (payment workflows → vendor.stripe.charge / vendor.stripe.refund) | — | — | Pending outreach | Tier 1: payment-with-HITL-approval is the canonical openwop use case from interrupt.md §"approval". |
When a target replies, fill in Outreach sent + First reply, advance Status through in-discussion → pack-drafted → published. When their pack lands on packs.openwop.dev, status → live.
Follow-up cadence: Day +5 / +12 / +28 nudges per
docs/recruitment/follow-up-cadence.md. After Day +28 with no reply, the lead is cold — re-contact only on a real trigger (new release, new endorsement, new evidence) at Day +90.
Governance migration trigger
When the first non-steward maintainer is added to the "Current maintainers" table above:
- Add the recruitment log row that produced them.
- Open the vendor-neutral-org migration RFC per
RFCS/0001-rfc-process.md.
Bootstrap-phase RFC waivers
⚠️ The grant below authorises less than has been done under it (audit:
docs/WAIVER-AUDIT-2026-08-20.md).- It permits additive RFCs, Draft → Active. At least five RFCs — 0147, 0148, 0149, 0150, 0156 — are non-additive and were promoted to
Accepted.- RFC 0147 forbids waiving the comment window for RFCs touching identity, authorization, idempotency, replay or certification (§A.6), and was itself waived while affecting four of them.
- Reconciling the text with the practice is on the maintainer's desk; nothing has been reversed on this basis.
Completeness is gated.
scripts/check-waiver-ledger.mjs(step 6 ofopenwop:check) fails if an RFC the tree shows as waived has no row here.
Per GOVERNANCE.md §"Sole-steward operation," additive RFCs MAY be promoted Draft → Active by steward decision when the comment window would only serve as a delay against zero external reviewers. This section records every RFC that has used the waiver, so future maintainers can audit the velocity of bootstrap-phase decisions. The waiver is retired automatically when the first non-steward maintainer joins.
| RFC | Title | Draft date | Active date | Comment-window duration | Waiver rationale |
|---|---|---|---|---|---|
| 0009 | Production-Profile Conformance | 2026-05-11 | 2026-05-11 | < 1 day | Additive; INTEROP-MATRIX Postgres row already claimed production-profile.md without mechanical evidence — closing the gap was higher-value than the 7-day delay |
| 0010 | Auth-Profile Conformance | 2026-05-11 | 2026-05-12 | < 1 day | Additive; consolidates four production-auth profile claims from auth-profiles.md (FINAL v1) into mechanical conformance — same posture as RFC 0009 |
| 0011 | Auth-Scoped Discovery Advertisement | 2026-05-12 | 2026-05-12 | < 1 day | Additive; closes ROADMAP Track 2 "next add auth-scoped discovery variants when a host advertises them" by formalizing capabilities.discovery.authScoped as a capability flag and adding the three conformance subtests called out in capabilities-change-detection.md §"Conformance expectations" |
| 0012 | Memory Compaction Profile | 2026-05-13 | 2026-05-15 | < 2 days | Additive; closes the SR-1 carry-forward gap for host-managed memory compaction and shipped with Postgres reference behavior plus conformance scenarios before external reviewers existed |
| 0022 | core.dispatch + core.subWorkflow runtime variable mapping | 2026-05-18 | 2026-05-18 | < 1 day | Additive; closes the symmetric input-mapping gap on both workflow-invocation primitives, identified via the MyndHyve Launch Studio production rebuild. Ships with schema deltas (dispatch-config.schema.json + capabilities.schema.json), spec prose update (node-packs.md §"core.subWorkflow contract"), and four conformance scenarios capability-gated on agents.dispatchMapping + subWorkflow.inputMapping. Promoted to Accepted same-day (2026-05-18) after the Postgres reference host implemented both §A + §B end-to-end and all four primary conformance scenarios (HVMAP-1a/1b/1c/2) graduated from it.todo() to live behavioral tests against the host (the mockDispatchPlan supervisor-mock extension at §"Unresolved questions" #6 landed alongside to unblock the dispatch trio). |
| 0042 | Experimental capability tier | 2026-05-22 | 2026-05-29 | 7 days elapsed (window waived, not run) | Additive tier/experimentalUntil vocabulary; steward acceptance after the §A/§B/§D wire surface reconciled into capabilities.md. |
| 0050 | SAML / SCIM enterprise identity profiles | 2026-05-24 | 2026-06-01 | 8 days elapsed (window waived, not run) | Additive auth profiles; the full auth-profiles.md SAML/SCIM/LDAP wire surface had already landed on main before the flip. |
| 0065 | Workflow node primary-output annotation | 2026-05-25 | 2026-05-29 | < 4 days | Additive single optional advisory field (outputRole); wire surface landed atomically with the flip. |
| 0066 | x-openwop-form vendor extension | 2026-05-25 | 2026-05-29 | < 4 days | Additive UX-hint vocabulary on pack configSchema; normative surface landed atomically with the flip. |
| 0067 | Provider-catalog conventions | 2026-05-26 | 2026-05-29 | < 3 days | Additive aiProviders.authModes + provider-name vocabulary; surface already on main, no steward prerequisite owed. |
| 0068 | Memory consolidation + standing commitments | 2026-05-26 | 2026-05-29 | < 3 days | Additive capabilities + content-free events; the gated scenarios shipped in @openwop/openwop-conformance@1.14.0 as the steward prerequisite. |
| 0071 | Artifact-type packs + chat card packs (Phase 1) | 2026-05-26 | 2026-05-26 | < 1 day | Additive pack kinds; architect pass resolved all six original design questions and the Phase-1 wire surface landed atomically. |
| 0072 | Agent inventory + dispatch normative surface | 2026-05-26 | 2026-05-29 | < 3 days | Additive read surface; full §A wire surface landed atomically on main (same-day Draft → Active → Accepted). |
| 0076 | Pack runtime requirements + host safe-fetch | 2026-05-28 | 2026-05-29 | < 1 day | Additive; flipped after a MyndHyve (second-host) wire-shape review resolved Q1–Q4; §A surface + conformance landed with the flip. |
| 0077 | Agent run lifecycle + live manifest dispatch | 2026-05-29 | 2026-05-29 | < 1 day | Additive; all five Unresolved questions resolved via MyndHyve T4 co-design (architect-validated) before the flip. |
| 0078 | Portable tool catalog + tool session contract | 2026-05-29 | 2026-05-30 | < 1 day | Additive; gated scenarios authored + published in @openwop/openwop-conformance@1.14.0; MyndHyve wire-shape review preceded the flip. |
| 0079 | Credential provenance + egress policy | 2026-05-29 | 2026-05-30 | < 1 day | Additive; same batch + same review posture as RFC 0078 (egress-audience-binding keystone published in 1.14.0). |
| 0080 | Agent memory capability reconciliation | 2026-05-29 | 2026-05-30 | < 1 day | Additive reconciliation of the memory capability model; all 4 Unresolved questions resolved as proposed after MyndHyve wire-shape review. |
| 0083 | Durable trigger + channel bridge profile | 2026-05-29 | 2026-05-30 | < 1 day | Additive composition of RFC 0052/0053/0017/0040; flipped after MyndHyve wire-shape review. |
| 0084 | Budget, quota, and cost policy | 2026-05-29 | 2026-05-30 | < 1 day | Additive; the gated budget-enforcement scenario published in @openwop/openwop-conformance@1.16.0 as the steward prerequisite. |
| 0085 | openwop-agent-platform meta-profile | 2026-05-29 | 2026-05-30 | < 1 day | Additive operational annex; the capstone, flipped LAST in the agent-platform arc after MyndHyve wire-shape review (all hard predicate terms ≥ Active). |
| 0090 | Agent verifier turn + convergence criteria | 2026-06-07 | 2026-06-07 | < 1 day | Additive (agent.verified event + verifier capability + executionModel.version 6); steward wire-shape review; verifier-no-content-leak invariant + always-on shape test landed with the flip. |
| 0091 | Multimodal perception input | 2026-06-07 | 2026-06-07 | < 1 day | Additive (ContentPart[] widening gated on aiProviders.input.modalities[]); steward wire-shape review during the bootstrap phase. |
| 0092 | Agent-level capability requirements | 2026-06-07 | 2026-06-07 | < 1 day | Additive (AgentManifest.requiresCapabilities[] reusing the RFC 0072 degraded[] projection); steward wire-shape review during the bootstrap phase. |
| 0093 | Protocol hardening (webhook delivery egress, interrupt-token lifecycle, retryable-response caching, approval-gate timeout/override) | 2026-06-11 | 2026-06-11 | < 1 day | Security/correctness pins from the 2026-06-11 corpus review; bootstrap-phase waiver. |
| 0094 | Wire-shape reconciliation (schema/prose defect repairs + schema-closure policy) | 2026-06-11 | 2026-06-11 | < 1 day | Defect repairs of self-contradictory published artifacts from the 2026-06-11 corpus review; bootstrap-phase waiver. |
| 0163 | SCIM ⟷ SAML subject-linking hardening (declarable link-key class + same-IdP trust-root MUST) | 2026-09-01 | 2026-09-01 | < 1 day | Additive; binds only hosts already opting into RFC 0159 subjectLinking:true, of which none exist in production discovery (INTEROP-MATRIX; MyndHyve live doc has no auth block; openwop-app advertises the profiles only behind seams), so a window would delay against zero external reviewers. Three pre-lock amendments were made by an architect pass rather than by a comment window: enum collapsed to classes, schema conditional added, trust-root representation pinned — each recorded in the RFC's Updated field and Alternatives 6–7. Same rule RFC 0159 and RFC 0050 used. |
| 0164 | Mandatory SCIM ⟷ SAML subject linking for combined hosts (RFC 0159 UQ1 / RFC 0163 UQ1 resolved) | 2026-09-02 | 2026-09-02 | < 1 day | Additive by an empirical argument recorded in the RFC: the §4 default-on row's harm set (hosts that advertise both profiles without the flag) is empty — INTEROP-MATRIX lists none, MyndHyve's live discovery has no auth block, openwop-app advertises the profiles only behind seams and already derives the flag. Same lineage and same rule as the RFC 0159 and 0163 waivers; the RFC 0147 §A.6 identity clause is named in the RFC header rather than hidden. Counterfactual recorded: safety-fix + 90 days had any combined host existed. |
| 0165 | v2 preparation — additive wire shapes (protocolVersions[], the Subject record, header dual emission) | 2026-09-02 | 2026-09-02 | < 1 day | Additive per COMPATIBILITY §2.1 — every field optional, no MUST relaxed; window waived under GOVERNANCE §"Sole-steward operation" (one maintainer, both hosts steward-owned). RFC 0147 §A.6 (identity RFCs complete the full window) is overridden and named in the RFC header — the 0159/0163/0164 precedent, stated rather than performed. Evidence gate not waived: Active → Accepted requires both host legs. |
| 0166 | Register dispositions, terminal states, witness classes (process) | 2026-09-02 | 2026-09-02 | < 1 day | Process/additive (governance amendment carried by an RFC because it adds an RFC 0001 status state); window waived under GOVERNANCE §"Sole-steward operation". Evidence gate: Active → Accepted requires the three corpus gates green AND the mechanical witness classification to have started being reviewed (ratchets moved). |
| 0167 | OpenWOP v2 — the program RFC (umbrella for children 0168–0178) | 2026-09-03 | 2026-09-03 | < 1 day | breaking (the v2 major) — the RFC 0001 §4 30-day window waived under GOVERNANCE §"Sole-steward operation" (one maintainer, one organization, both matrix hosts steward-owned, no external adopter to wait for); the §5 cross-org note carried in the header; RFC 0147 §A.6 overridden and named (this RFC touches identity, authorization, isolation, idempotency, replay, external effects and certification — all seven). Evidence gate not waived: Accepted only at the v2.0 cut on the §G.2 predicates; every child needs a witnessed bundle. Adversarial /architect pass recorded in place of external review. |
| 0168 | v2 evidence and conformance (RFC 0167 child C.1) | 2026-09-03 | 2026-09-03 | < 1 day | breaking (v2) under the RFC 0167 program; window waived under GOVERNANCE §"Sole-steward operation"; RFC 0147 §A.6 override inherited from and named in the parent (the bundle is the artifact every security claim rests on). Evidence gate not waived: Accepted at Phase 3 on suite 2.0.0's seven self-tests and openwop-app's verifying v2-rc bundle. |
| 0169 | v2 discovery and capabilities (RFC 0167 child C.2) | 2026-09-03 | 2026-09-03 | < 1 day | breaking (v2) under the RFC 0167 program; window waived under GOVERNANCE §"Sole-steward operation"; RFC 0147 §A.6 override inherited from and named in the parent. Evidence gate not waived: Accepted at Phase 3 on the five v2 scenarios. Adversarial /architect pass recorded in the RFC. |
| 0172 | v2 versioning and release (RFC 0167 child C.5) | 2026-09-03 | 2026-09-03 | < 1 day | breaking (v2) under the RFC 0167 program; window waived under GOVERNANCE §"Sole-steward operation"; RFC 0147 §A.6 override inherited from and named in the parent. Evidence gate not waived: Accepted at Phase 3 on the dual-stack scenario from both majors on openwop-app. Adversarial /architect pass recorded in the RFC. |
| 0174 | v2 governance (RFC 0167 child C.7) | 2026-09-03 | 2026-09-03 | < 1 day | breaking (v2) under the RFC 0167 program; window waived under GOVERNANCE §"Sole-steward operation"; RFC 0147 §A.6 override inherited from and named in the parent; this RFC amends the decision rule, and the two-approval requirement in GOVERNANCE §"Amendments" is waived and recorded here under the same paragraph (approval-count waived) — the first RFC tested by its own check-waiver-authority.mjs. Evidence gate not waived: Accepted at Phase 3 on the corpus gates. |
| 0178 | v2 assurance registers and deprecation machinery (RFC 0167 child C.11) | 2026-09-03 | 2026-09-03 | < 1 day | breaking (v2) under the RFC 0167 program; window waived under GOVERNANCE §"Sole-steward operation"; RFC 0147 §A.6 override inherited from and named in the parent. Evidence gate not waived: Accepted at Phase 3 on the annotation generator and removal-date gate. |
| 0179 | Root preferredVersion (v1.x additive half of RFC 0172 §A.1) | 2026-09-03 | 2026-09-03 | < 1 day | additive; 7-day window waived under GOVERNANCE §"Sole-steward operation"; no RFC 0147 §A.6 surface. Evidence gate not waived: Accepted when openwop-app advertises it and suite 2.0.0's dual-stack-negotiation reads it. |
| 0180 | Vendor-org registration procedure for spec/v2/declaration.json extensions | 2026-09-06 | 2026-09-06 | < 1 day | additive (COMPATIBILITY.md §2.1); window waived under GOVERNANCE §"Sole-steward operation". Process-only: no schema, field, MUST, or error-code change — declaration.schema.json already pinned the entry shape and key pattern. Evidence gate not waived, and deliberately not faked: §Conformance records A.1 as negative-existence (a host reading a private registry that happens to agree is indistinguishable on the wire) rather than minting a scenario that would pass vacuously; A.5 is already witnessed by the two legs of v2-unmapped-type-refused. Filed because the registry shipped at 2.0.0 admitting one reserved org with no procedure for a second — found from outside by a live host whose 31 types were correctly, and permanently, refused. |
| 0181 | Vendor path namespace — /host/<org>/… for host-proprietary operations under major 2 | 2026-09-10 | 2026-09-10 | < 1 day | additive (COMPATIBILITY.md §2.1); window waived under GOVERNANCE §"Sole-steward operation". v2 prose (versioning.md §5 decision, §1.4 scoping) plus declaration rows (two org registrations under RFC 0180 A.2, two reserved segments); no field, MUST relaxation, error-code or v1 change; no RFC 0147 §A.6 surface. Evidence gate not waived: Accepted when a tier-1 host serves /host/<org>/… for its registered org and advertises the mount under extensions.<org>; the suite deliberately never measures a vendor path and §Conformance says so. Filed the day two production hosts measured the gap versioning.md §5 had recorded as undecided (1,062 and 11 proprietary roots; one façade already answering under /host/ by accident). |
| 0182 | listRuns — a portable, tenant-scoped, paginated run list under major 2 (GET /runs, family runList) | 2026-09-11 | 2026-09-11 | < 1 day | additive (COMPATIBILITY.md §2.1); window waived under GOVERNANCE §"Sole-steward operation". One new OPTIONAL operation gated on a new core family; response reuses RunSnapshot; no existing field, MUST, error-code or v1 change; no RFC 0147 §A.6 surface (tenant scoping is enforced by identity §5's existing bound-id rule, not a new authorization primitive). Evidence gate not waived: Accepted when the reference host (tier-1) or a tier-2 host advertises runList and passes v2-run-list; the scenario ships in the same release (suite 2.1.0). Filed after RFC 0181 §Unresolved-1 was corrected: the operation was never in v1, and the interop gap (every UI grows its own list) is real. |
| 0183 | interruptResolved cannot record four of the five resume actions | 2026-09-16 | 2026-09-16 | < 1 day | additive (COMPATIBILITY.md §2.1); window waived under GOVERNANCE §"Sole-steward operation". Three OPTIONAL properties on a closed def and decision's enum closed; §A.1 raised from SHOULD to a kind-conditional MUST at Active because the shipped suite (2.2.0) already asserted it and COMPATIBILITY.md §2.3 forbids a suite stricter than the spec on wire shape — the reporting host (openwop-app) implements it. Not an RFC 0147 §A.6 surface (event payload fidelity; no identity, authorization, isolation, idempotency, replay or effect rule changes). Evidence gate not waived: Accepted on the reference host passing the refine and edit-accept legs. |
| 0184 | A tenant-bound id cannot survive a front door as %2F (~-escaped path projection) | 2026-09-16 | 2026-09-16 | < 1 day | additive (COMPATIBILITY.md §2.1); window waived under GOVERNANCE §"Sole-steward operation". RFC 0147 §A.6 overridden and named in the RFC header (identity surface): a second accepted spelling beside %2F, five grammars widened, nothing accepted today refused; the defect was live on a tier-1 host's front door and suite 2.2.0 already enforced v2-bound-id-path-projection, so Draft contradicted a shipped MUST. Counterfactual recorded: safety-fix + full window had any accepted spelling narrowed. Evidence gate not waived: Accepted on the reference host passing the scenario unaided. |
| 0186 | Three payload seats the hosts measured and the corpus lacked (conversation.exchanged union, reason on two defs, ApprovalData.onTimeout) | 2026-09-17 | 2026-09-17 | < 1 day | additive (COMPATIBILITY.md §2.1); window waived under GOVERNANCE §"Sole-steward operation". Every seat is a strict widening whose value domain was measured from a production host's emit sites or type (not a sample) and answered on the /crosstalk v2 bus; the witness v2-payload-seats-0186.test.ts ships in the same PR and is sabotage-proved three ways. |
| 0187 | Four bindings the hosts found: webhookId carries the subscriptionId kind; a v2-only type passes through on the v1 wire; eligibility binds every writer; the legacy writer marks the row | 2026-09-18 | 2026-09-18 | < 1 day | additive (COMPATIBILITY.md §2.1); window waived under GOVERNANCE §"Sole-steward operation". Every seat is a strict widening whose value domain was measured from a production host's emit sites or type (not a sample) and answered on the /crosstalk v2 bus; the witness v2-payload-seats-0186.test.ts ships in the same PR and is sabotage-proved three ways. |
| 0188 | GET /webhooks/{webhookId}/dead-letters: the read that makes webhooks.md §Durability observable, gated on a new webhooks.deadLetter facet; the seat that makes the deliveryId kind witnessable; the run-sink/delivery-sink split; and the webhooks family's first owningRfc. | additive (7-day) | 2026-09-18 | steward | No identity or auth surface is narrowed — one new optional read, gated on a facet no host advertises yet, and its response schema is closed so a host cannot widen it. The obligation it makes observable is one the corpus already asserted and nothing could check. |
| 0189 | normativeText as a checkable declaration field: legal home classes, a content predicate, a ratchet that stops punishing honest declarations, and a deadline that can actually fire. | editorial + gate | 2026-09-18 | steward | No wire surface, schema shape, error meaning or MUST strength changes — this RFC governs a gate over a source artifact, and every rule it adds was sabotage-proved at filing. |
| 0190 | The kernel budget's denominator follows the home gate's acceptance (spec/v2/core/** recursive, plus ext documents a core family declares), and its cap grows only as families are actually homed. Supersedes RFC 0174 §E.2/§E.2a. | editorial + gate | 2026-09-18 | steward | No wire surface, schema shape, endpoint contract, error meaning or MUST strength changes — this governs a gate over source artifacts. RFC 0147 §A.6 does not apply. Filed because §E.2a's rejection of a raise (2026-09-17) rested on a denominator of 16 RFCs, one day before RFC 0189 made 61 families' homes dated work against 164 remaining words. |
| 0191 | The reciprocal normative-home marker: a declared spec/v2/** home must itself claim the family. Filed after four syntactic predicates were measured and all four either broke honest declarations or kept the loophole. | editorial + gate | 2026-09-18 | steward | No wire surface, schema shape, endpoint contract, error meaning or MUST strength changes — a gate predicate plus a one-line marker in nine core documents. RFC 0147 §A.6 does not apply. |
| 0192 | A facet is advertised by the presence of its key. States the v2 facet advertisement semantic (the family rule existed; the facet row did not), rewrites 26 descriptions that still conditioned a MUST on the retired supported flag, and fails the generator on the 27th. | additive | 2026-09-19 | steward | No identity, authorization, isolation, idempotency, replay, external-effect or certification surface changes — RFC 0147 §A.6 does not apply. A description is an annotation, not an assertion, so no host document changes validity. |
| 0193 | A capability record is an object, so a v1 array needs a seat. Names the three envelope families whose payload the v2 generator dropped in silence, pins an absent catalog to fail CLOSED, and makes the generator refuse rather than drop. | additive | 2026-09-19 | steward | RFC 0147 §A.6 IS engaged (prompt-injection surface) and is discharged, not waived: the change is strictly restrictive — before, a major-2 host had no list and any reading admitting unlisted kinds was unconstrained; after, the absent-catalog case is pinned to refuse. There is no configuration of seats under which a kind admitted after this RFC would have been refused before it. Every published v2 discovery document, including the vacuous one that motivated the RFC, stays valid. |
| 0194 | a run's terminal event is emitted once and ends its forward execution | 2026-09-21 | 2026-09-21 | < 1 day (window waived, not run) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting replay, external effects or certification; this RFC is in that class. The steward decided on 2026-09-21 to waive it anyway ("Move all RFCs to active and waive the wait period"). Recorded here so the override is auditable, not so it reads as routine. |
| 0195 | a certification bundle's declarations are signed, and an unobserved requirement is blocked | 2026-09-21 | 2026-09-21 | < 1 day (window waived, not run) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting replay, external effects or certification; this RFC is in that class. The steward decided on 2026-09-21 to waive it anyway ("Move all RFCs to active and waive the wait period"). Recorded here so the override is auditable, not so it reads as routine. |
| 0196 | callbackUrl is refused or delivered under the egress guard, and an embedded IPv4 address is judged as IPv4 | 2026-09-21 | 2026-09-21 | < 1 day (window waived, not run) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting replay, external effects or certification; this RFC is in that class. The steward decided on 2026-09-21 to waive it anyway ("Move all RFCs to active and waive the wait period"). Recorded here so the override is auditable, not so it reads as routine. |
| 0197 | v2 surfaces are retired, never reshaped | 2026-09-22 | 2026-09-22 | < 1 day (window waived, not run) | breaking. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting certification (what a committed bundle may carry; what a capability status may claim); this RFC is in that class. The steward decided on 2026-09-22 to waive it anyway (the MCP/A2A remediation program instruction, precedent RFC 0194). It is also breaking-class (30-day window) and amends the decision rule (the GOVERNANCE.md breaking-change row), so the GOVERNANCE §"Amendments" two-approval requirement is waived while one maintainer exists (RFC 0174 §B.3). Acceptance is provisional and the RFC 0156 §B review is owed. Recorded here so the override is auditable, not so it reads as routine. |
| 0198 | the MCP server mount maps long runs to MCP Tasks, and a disconnect cancels only the run it owns | 2026-09-22 | 2026-09-22 | < 1 day (window waived, not run) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting replay, external effects and isolation (tasks/update resolves interrupts; a disconnect cancels a run; task ids resolve through tasks/*); this RFC is in that class. The steward decided on 2026-09-22 to waive it anyway (the MCP/A2A remediation program instruction, precedent RFC 0194). Acceptance is provisional and the RFC 0156 §B review is owed. Recorded here so the override is auditable, not so it reads as routine. |
| 0199 | the host as an OAuth client, and the credential interrupt | 2026-09-22 | 2026-09-22 | < 1 day (window waived, not run) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting identity and authorization (who may complete a grant; what a run may ask a user for); this RFC is in that class. The steward decided on 2026-09-22 to waive it anyway (the MCP/A2A remediation program instruction, precedent RFC 0194). Acceptance is provisional and the RFC 0156 §B review is owed. Recorded here so the override is auditable, not so it reads as routine. |
| 0200 | the host as an OAuth protected resource | 2026-09-22 | 2026-09-22 | < 1 day (window waived, not run) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting identity and authorization (which tokens a host accepts; what refusals disclose; what credential may leave it); this RFC is in that class. The steward decided on 2026-09-22 to waive it anyway (the MCP/A2A remediation program instruction, precedent RFC 0194). Acceptance is provisional and the RFC 0156 §B review is owed. Recorded here so the override is auditable, not so it reads as routine. |
| 0201 | Standard Webhooks as an opt-in companion signature scheme, with a signed delivery id, multi-signature rotation and endpoint verification | 2026-09-22 | 2026-09-22 | < 1 day (window waived, not run) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting external effects and idempotency (endpoint verification; a signed, retry-stable delivery id); this RFC is in that class. The steward decided on 2026-09-22 to waive it anyway (the MCP/A2A remediation program instruction, precedent RFC 0194). Acceptance is provisional and the RFC 0156 §B review is owed. Recorded here so the override is auditable, not so it reads as routine. |
| 0202 | each inventoried agent is published as an A2A Agent Card | 2026-09-22 | 2026-09-22 | < 1 day (window waived, not run) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting isolation and authorization (tenant-scoped inventory published through a second protocol surface); this RFC is in that class. The steward decided on 2026-09-22 to waive it anyway (the MCP/A2A remediation program instruction, precedent RFC 0194). Acceptance is provisional and the RFC 0156 §B review is owed. Recorded here so the override is auditable, not so it reads as routine. |
| 0203 | a remote node-pack runtime may name its MCP server by its registry record | 2026-09-22 | 2026-09-22 | < 1 day (window waived, not run) | additive. Routine bootstrap waiver under GOVERNANCE §"Sole-steward operation". Carries an MCP Registry record by value inside the signed manifest: no outbound fetch, no new egress target, no credential path, no identity the host must trust. RFC 0147 §A.6 does not apply. |
| 0204 | the v2 host MCP client returns MCP results | 2026-09-22 | 2026-09-22 | < 1 day (window waived, not run) | additive. Routine bootstrap waiver under GOVERNANCE §"Sole-steward operation". Changes the shape a pack receives from an MCP call and the metadata a catalog publishes; adds no outbound call and touches no identity, tenancy, replay or certification surface. The one safety rule (an unclassified MCP tool is write) only narrows. RFC 0147 §A.6 does not apply. |
| 0205 | run artifacts and conversation content speak A2A Parts | 2026-09-22 | 2026-09-22 | < 1 day (window waived, not run) | additive. Routine bootstrap waiver under GOVERNANCE §"Sole-steward operation". Two optional representations and one widened string grammar; its one isolation sentence restates for the native read the url rule RFC 0152 already imposes over A2A. RFC 0147 §A.6 does not apply. |
| 0206 | locale keys accept the BCP 47 tags the host negotiates | 2026-09-22 | 2026-09-22 | < 1 day (window waived, not run) | additive. Routine bootstrap waiver under GOVERNANCE §"Sole-steward operation". Widens one string grammar (a strict superset), adds a fallback step only a newly legal key can reach, and two canonical-case SHOULDs. RFC 0147 §A.6 does not apply. |
| 0207 | trace context across MCP and A2A, and debug-bundle spans that join the trace | 2026-09-22 | 2026-09-22 | < 1 day (window waived, not run) | additive. Routine bootstrap waiver under GOVERNANCE §"Sole-steward operation". Observability: a carrier for correlation data the corpus already says is never authorization evidence; the HTTP header stays conforming (decisions log D4). RFC 0147 §A.6 does not apply. |
| 0208 | v2 homes the A2A and MCP operation mappings | 2026-09-22 | 2026-09-22 | < 1 day (window waived, not run) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting isolation (no enumeration of unreadable tasks; ListTasks scoping; hints never select a tenant); this RFC is in that class. The steward decided on 2026-09-22 to waive it anyway (the MCP/A2A remediation program instruction, precedent RFC 0194). Acceptance is provisional and the RFC 0156 §B review is owed. Recorded here so the override is auditable, not so it reads as routine. |
| 0209 | v2 A2UI surfaces are A2UI v0.9 | 2026-09-22 | 2026-09-22 | < 1 day (window waived, not run) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting authorization and replay (A2UI action confinement; a surface is the fold of several recorded envelopes); this RFC is in that class. The steward decided on 2026-09-22 to waive it anyway (the MCP/A2A remediation program instruction, precedent RFC 0194). Acceptance is provisional and the RFC 0156 §B review is owed. Recorded here so the override is auditable, not so it reads as routine. |
| 0210 | a lane's revocation rule is measured, and a host that only honours exp says so | 2026-09-22 | 2026-09-23 | 1 day (window waived, not run — filed with the window explicitly NOT waived; the waiver came after) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting identity and authorization (which credentials a host accepts, for how long, and what it refuses them with); this RFC is squarely in that class and its own header said so, recording that no waiver was requested and none granted. The steward decided on 2026-09-23 to waive it anyway. Two things distinguish it from a routine row: the RFC carries its own override rather than being folded under RFC 0200's (stacking a second identity-vocabulary widening on one override is the compounding §A.6 exists to prevent), and the withheld half — the enum member, the error code, the lifetime MUST, the invariant and the enforcing scenario — lands in the same change as the member it bounds, so the corpus never offers exp-only with nothing measuring it. Acceptance is provisional and the RFC 0156 §B review is owed. Active, not Accepted: no host advertises exp-only yet and the four §B rows have no executed-pass. Recorded here so the override is auditable, not so it reads as routine. |
| 0212 | canonical JSON is RFC 8785 JCS, and a certification preimage does not depend on the machine that computed it | 2026-09-23 | 2026-09-23 | < 1 day (window waived, not run) | Class-3 correction. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting certification and replay; this RFC defines the bytes a bundle signature and witnessSha256 cover and the bytes the RFC 0150 replay digest hashes, so it is squarely in that class. The steward decided on 2026-09-23 to waive the window (the MCP/A2A remediation program instruction; precedent RFC 0194). It carries its own override, not one folded under an earlier RFC's. The evidence gate is not waived: Accepted still needs the vectors reproduced by one host-side verifier and the registry signer's refusals. Acceptance is provisional and the RFC 0156 §B review is owed. Recorded here so the override is auditable, not so it reads as routine. |
| 0214 | an A2A push credential is a destination credential, and a push is an egress like any webhook | 2026-09-23 | 2026-09-23 | < 1 day (window waived, not run) | Class 3 correction + additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting authorization, external effects and replay (which credential may leave the host and to where; which outbound POSTs a host makes; whether a replay fork makes them); this RFC is in that class. The steward decided on 2026-09-23 to waive it anyway (the MCP/A2A overlap remediation program, TODO.md decision D5; precedent RFC 0194). Scope is the correction only; the push implementation is deferred (decision D2), and every host-behavior row is gated on a2a.pushNotifications, which no committed host advertises. Acceptance is provisional and the RFC 0156 §B review is owed. Recorded here so the override is auditable, not so it reads as routine. |
| 0211 | an A2A error's details are an ErrorInfo, and an A2A interface never answers in the OpenWOP envelope | 2026-09-23 | 2026-09-23 | < 1 day (window waived, not run) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting isolation; this RFC is in that class on one axis (§D: what an A2A error may disclose about a task the caller cannot read). The steward decided on 2026-09-23 to waive it anyway (the MCP/A2A overlap remediation program, TODO.md; precedent RFC 0194). It carries its own override rather than being folded under RFC 0208's. Acceptance is provisional and the RFC 0156 §B review is owed. The evidence gate is not waived: Accepted needs a deployed tier-1/tier-2 bundle. Recorded here so the override is auditable, not so it reads as routine. |
| 0213 | three outcomes the v2 core never stated — a resume cursor past the log, the loser of a same-key race, and a resolve after the run ended | 2026-09-23 | 2026-09-23 | < 1 day (window waived, not run) | §A/§C Class-3, §B additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting replay (event-log resumption), idempotency (the concurrency rule) and authorization (the resolve outcome on an approval surface); this RFC is in all three. The steward decided on 2026-09-23 to waive it (the MCP/A2A remediation program instruction, precedent RFC 0194). Evidence gate not waived: each section moves to Accepted on its own witness. Acceptance is provisional and the RFC 0156 §B review is owed. Recorded here so the override is auditable, not so it reads as routine. |
| 0215 | a webhook delivery does not wait on another subscription's receiver, and an unregistered subscription gets no further attempts | 2026-09-24 | 2026-09-25 | 1 day (window waived, not run) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting isolation (§A: one tenant's dead receivers delaying another tenant's deliveries) and external effects (§B: signed deliveries to a destination its owner withdrew); this RFC is in both. The RFC's own Draft had committed to the full window (to 2026-10-01). The steward decided on 2026-09-25 to waive it anyway ("waive the comment window and move 0215 to Active", precedent RFC 0194); an architecture review decided the open questions in its place. Evidence gate not waived. Acceptance is provisional and the RFC 0156 §B review is owed. Recorded here so the override is auditable, not so it reads as routine. |
| 0216 | a colocated companion bundle is marked, and witnesses only the rows that need the suite's own issuer | 2026-09-26 | 2026-09-26 | < 1 day (window waived, not run — filed Draft with the full window to 2026-10-03; the waiver came the same day) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting certification; this RFC changes which committed bundle rows check-accepted-predicate counts as acceptance evidence, so it is in that class. The steward directed the waiver on 2026-09-26. It carries its own override, not one folded under an earlier RFC's. The evidence gate is not waived. Acceptance is provisional and the RFC 0156 §B review is owed. Recorded here so the override is auditable, not so it reads as routine. |
| 0221 | a webhook secret the host generates is returned once | 2026-09-27 | 2026-09-27 | < 1 day (window waived, not run) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting external effects; a webhook subscription's signing secret is part of that surface, as it was for RFC 0201 and RFC 0215. The steward's standing directive (window waived, Accepted provisional) covers it. It carries its own override. The evidence gate is not waived, and the RFC 0156 §B review is owed. |
| 0223 | a rejected approval gate fails closed, and the failure is routable | 2026-09-28 | 2026-09-28 | < 1 day (window waived, not run) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting authorization and replay; an approval gate's outcome is an authorization decision (as it was for RFC 0213 §C), and the rule's last clause governs replay. The steward approved skipping the window for #1692. The evidence gate is not waived, and the RFC 0156 §B review is owed. |
| 0222 | v2 registry operations — lifecycle by publication, key rotation, and the checks a registry refuses on | 2026-09-28 | 2026-09-28 | < 1 day (window waived, not run) | additive. Routine bootstrap waiver under GOVERNANCE §"Sole-steward operation". Restates for v2 the earlier major's deprecate, yank, key-rotation and submission rules, filtered to what the static registry tree does; no schema shape, code or endpoint changes. RFC 0147 §A.6 does not apply: registry lifecycle is not replay, an external effect or certification, and the key rules neither widen nor narrow who may sign a namespace. Evidence gate not waived. |
| 0220 | an extension family graduates on evidence a script can read | 2026-09-27 | 2026-09-28 | ~1 day (filed Draft with the full window to 2026-10-04; waived 2026-09-28, not run) | additive + Class 3 correction. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §D changes which bundles count as ext-maturity evidence (tier-2+ only), a certification class. The steward directed the waiver on 2026-09-28, and it also covers the 7-day window on each Draft → Stable promotion PR under spec/v2/ext/README.md until RFC 0220 is Accepted (the steward chose "waive both"; applied to #1707 and to the dataIntegration promotion). Extended 2026-09-28 by steward direction ("do not wait the 7 days"): every further Draft → Stable ext promotion under spec/v2/ext/README.md lands without the 7-day window once its certified tier-2 evidence is committed. The evidence predicate is not waived: check-ext-status-coherence must report the family GRADUABLE, and the live discovery is re-checked at the flip. It carries its own override. The evidence gate is not waived: each promoted family rests on a certified tier-2 bundle (#1690). The RFC 0156 §B review is owed. |
| 0225 | a webhook host may advertise how long a delivery can keep retrying | 2026-09-28 | 2026-09-28 | 0 days elapsed (window waived, not run — filed Draft with the full window to 2026-10-05; the waiver came the same day) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting certification, external effects and replay; this RFC is in all three: §D changes a certification row's verdict (0173.webhook-durable-delivery.dead-letter convicts past an advertised bound instead of recording blocked), §B bounds when an outbound webhook delivery is dead-lettered, and §C edits webhooks.md §Replay (word-neutral, the rule stays in replay.md). Steward direction 2026-09-28: the maintainer chose the override explicitly after the §A.6 finding was put to them. The evidence gate is not waived, and the RFC 0156 §B review is owed. |
| 0230 | inbound webhook ingest contract — Standard Webhooks signing, webhook-id identity, response shape | 2026-09-30 | 2026-09-30 | < 1 day (window waived, not run — filed Draft with the full window; the waiver came the same day) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting identity/authentication, idempotency, external effects and certification; this RFC is in four: §C makes the signature (not an OpenWOP credential) authenticate ingestUrl, §C keys dedup on webhook-id, an accepted ingest starts a run, and §Conformance defines how openwop.floor.trigger-bridge-delivery is witnessed without seams. Steward direction 2026-09-30: the maintainer chose the override explicitly after the §A.6 finding and the three open security questions were put to them (decided in the RFC's §Decisions). The evidence gate is not waived, and the RFC 0156 §B review is owed. |
| 0226 | three run-failure codes the hosts share, registered | 2026-09-28 | 2026-09-28 | 0 days elapsed (window waived, not run — filed Draft with the full window to 2026-10-05; the waiver came the same day) | additive. Steward direction 2026-09-28: maintainer waived the comment window. Routine bootstrap waiver under GOVERNANCE §"Sole-steward operation". Three errors.json rows (node_config_invalid, sandbox_invocation_error, mcp_error) and a widened capability_not_provided meaning; no shape, status or existing code changes. RFC 0147 §A.6 does not apply: error-code vocabulary is not identity, authorization, idempotency, replay or certification; sandbox_invocation_error changes no isolation guarantee and mcp_error no external-effect semantics. Evidence gate not waived. |
| 0227 | a generated restatement of a registry is not kernel prose | 2026-09-28 | 2026-09-29 | 1 day elapsed (window waived, not run — filed Draft with the full window to 2026-10-05) | editorial + gate (amends RFC 0190 §A). Steward direction 2026-09-29: the maintainer waived the comment window explicitly ("address these, even waive the 7 day period"). Routine bootstrap waiver under GOVERNANCE §"Sole-steward operation". The kernel budget excludes a spec/v2/generated/ document a registered generator writes whole and checks byte-for-byte; the errors.md status table moves there (37,713 → 37,351 of 37,800), and 0171.error-registry-prose-parity is re-pointed. RFC 0147 §A.6 does not apply: the RFC governs a gate over source artifacts; no certification bundle, witness or replay digest covers the budget or the parity row, and no identity, authorization, isolation, idempotency, replay or external-effect surface changes. No MUST is added, moved or relaxed. Evidence gate not waived. |
| 0229 | a production host can witness secret resolution without an oracle | 2026-09-29 | 2026-09-30 | 1 day elapsed (window waived, not run — filed Draft with the full window to 2026-10-06 and the text saying it would run in full; the waiver came the next day) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting certification and secret material; this RFC is in both: §E adds a second path to the openwop-secrets certification floor and the first requirement ids of the v2 secrets family, and §A–§B govern how a host resolves, redacts and digests a run-supplied secret. Steward direction 2026-09-30: the maintainer chose the override explicitly after being told §A.6 bars a bootstrap waiver here. It carries its own override. The evidence gate is not waived: Accepted needs all four §F rows executed-pass on a certified production bundle. Acceptance is provisional and the RFC 0156 §B review is owed. Recorded here so the override is auditable, not so it reads as routine. |
| 0232 | a trigger subscription's dead-lettered deliveries are readable — triggerBridge.deadLetter, listTriggerDeadLetters, run-less transitions recorded | 2026-10-03 | 2026-10-03 | < 1 day (window waived, not run — filed Draft with the full window to 2026-10-10; the waiver came the same day) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting authorization/isolation and certification; this RFC is in both: §B adds a tenant-bound read under webhooks:manage, and §E decides how openwop.floor.trigger-bridge-delivery's leg 4 is scored on a host without seams (two ids, the state-change id inapplicable). Steward direction 2026-10-03: the maintainer decided the five questions and waived the window, then chose the override explicitly after being told §A.6 bars a bootstrap waiver here. The evidence gate is not waived: Accepted needs the §E rows executed-pass on a certified production bundle with no seams served. Acceptance will be provisional and the RFC 0156 §B review is owed. |
| 0233 | a host's connection providers and refused registrations are readable — connections.providerRead, listConnectionProviders, resolveConnectionProvider | 2026-10-03 | 2026-10-03 | < 1 day (comment window waived, not run — filed Draft with the full window to 2026-10-10; the waiver came the same day) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting authorization and certification; this RFC is in both: §B/§C add host-global reads under manifest:read, and §F decides how v2-provider-conflict is scored on a seam-free host. Steward direction 2026-10-03: the maintainer directed this RFC to Accepted without the window and its design questions to /architect review (rulings in §Decisions). The evidence gate is not waived: Accepted needs the §F rows executed-pass on a certified production bundle with no seams served. Acceptance will be provisional and the RFC 0156 §B review is owed. |
| 0234 | an accepted RFC may set v1 end-of-support earlier than the computed date — leg (c), applied: 2026-10-04 | 2026-10-04 | 2026-10-04 | 0 days (comment window waived, not run — Draft → Accepted in the filing PR) | governance (end of the v1 obligation; no wire change). STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting compatibility and certification; ending the v1 overlap early is both. Steward direction 2026-10-04: the maintainer chose "RFC, window waived, today" in the steward session after being told it changes a normative safeguard for third-party v1 consumers and is hard to reverse. Evidence: every counted host certified at v2 and reporting no third-party old-major traffic over 7 days (RFC 0234 §Motivation). The retention floors (to 2027-09-05) are unchanged; the RFC 0156 §B review is owed. |
| 0235 | If-None-Match is evaluated as HTTP defines it — runs.md §Caching and encoding, capabilities.md §1.1, the OpenAPI If-None-Match and discovery ETag descriptions | 2026-10-04 | 2026-10-04 | 0 days (comment window waived, not run — filed Draft with the full window to 2026-10-11; the waiver came the same day) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting authorization and certification; this RFC is in both: §A requires a conditional to be evaluated only where the answer would be 2xx, which protects the non-disclosure 404, and §D adds four requirement ids every major-2 bundle records. Steward direction 2026-10-04: the maintainer directed "skip the comment window and move it to Active" and to take it to Accepted with the other sessions. The evidence gate is not waived: Accepted needs the four openwop.requirement.0235.* ids executed-pass on a certified major-2 bundle with no seams served. The RFC 0156 §B review is owed. |
| 0238 | a host's front-end plugin boundary is observable — uiPlugins.served, getUiPluginFrame, dispatchUiPluginRequest, fixture ui-plugin-pack-narrow | 2026-10-06 | 2026-10-06 | 0 days (comment window waived, not run — filed Draft with the full window to 2026-10-13; the waiver came the same day) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting authorization and certification; this RFC is in both: §C adds a dispatch operation authorized per method as the caller, and §F re-witnesses four protocol-tier SECURITY invariants that every major-2 bundle records. Steward direction 2026-10-06: the maintainer directed "bypass the 7 day period and proceed to active". The evidence gate is not waived: Accepted needs the four openwop.requirement.0238.* ids executed-pass on a certified bundle from a host advertising uiPlugins.served with the fixture installed. The RFC 0156 §B review is owed. |
| 0239 | a council's roster has an input seat and its refusals have codes — core.conversationGate participants, conversation_speaker_not_participant, conversation_roster_exceeded | 2026-10-06 | 2026-10-06 | 0 days (comment window waived, not run — filed Draft with the full window to 2026-10-13; the waiver came the same day) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting authorization and certification; this RFC is in both: §B decides who may speak in a conversation, and §F adds three requirement ids every major-2 bundle records. Steward direction 2026-10-06: the maintainer directed "move RFC 0239 to active and waive the comment window". The evidence gate is not waived: Accepted needs the §F rows on a certified bundle. The RFC 0156 §B review is owed. |
| 0241 | a host event can be triggered on demand for test — POST /host/events/test, the reserved host-test.* types | 2026-10-07 | 2026-10-07 | 0 days (comment window waived, not run — filed Draft with the full window to 2026-10-14; the waiver came the same day) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting authorization and certification; this RFC is in both: §B adds an operation under webhooks:manage whose product reaches a tenant's subscribers, and §D changes how the openwop.requirement.0236.* rows and invariant host-event-tenant-isolation are witnessed on every major-2 bundle. Steward direction 2026-10-07: the maintainer chose "Waive, go Active". The evidence gate is not waived: Accepted needs a certified seams-off bundle. The RFC 0156 §B review is owed. |
| 0242 | a negotiation record says what was asked for, and an inbound negotiation has a home — optional requested on negotiation.decided; the reserved durable host-event type | 2026-10-10 | 2026-10-10 | 0 days (comment window waived, not run — filed Draft with the full window to 2026-10-17; the waiver came the same day) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting authorization and certification; this RFC is in certification: §D adds 0242.* rows to every major-2 bundle on a host serving A2A or MCP, and changes the tests behind invariants a2a-version-no-silent-downgrade and mcp-version-no-silent-downgrade. Steward direction 2026-10-10: the maintainer said "waive it". The evidence gate is not waived: Accepted needs a certified bundle. The RFC 0156 §B review is owed. |
| 0243 | parallel fan-out has a v2 seat, and a link key needs both linking lanes — optional agents.fanOut; auth.subjectLinkKey MUST NOT without both lanes | 2026-10-12 | 2026-10-12 | 0 days (comment window waived, not run — Draft → Active in the filing PR) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting identity and certification; this RFC is in both: §B restricts how a host advertises its SAML/SCIM subject-link contract, and adds 0243.* rows to every major-2 bundle. Steward direction 2026-10-12: the maintainer said "Waive the comment window". The evidence gate is not waived: Accepted needs a certified bundle (gap G1). The RFC 0156 §B review is owed. |
| 0244 | eval suites grade the tool path, run repeated trials, and fail closed on a fixture miss — optional expected.trajectory, trials, fixtures.onMiss, four agents.evalSuite members | 2026-10-14 | 2026-10-14 | 0 days (comment window waived, not run — Draft → Active in the filing PR) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting certification; this RFC adds 0244.* rows to every major-2 bundle. Steward direction 2026-10-14: the maintainer asked to move RFC 0244 to Active by waiving the 7-day window. The evidence gate is not waived: Accepted (provisional) 2026-10-14 on MyndHyve's certified 2.46.9 cut (tier-2, independent second host). The RFC 0156 §B review is owed. |
| 0245 | eval fixtures replay a recorded tool error as an error — optional toolResponses[].isError, one agents.evalSuite member (fixtureErrors) | 2026-10-15 | 2026-10-15 | 0 days (comment window waived, not run — Draft → Active in the filing PR) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting replay or certification; this RFC governs replay of a recorded tool boundary and adds 0245.* rows to major-2 bundles. Steward direction 2026-10-15: the maintainer asked to move RFC 0245 to Active and waive the 7-day window. The evidence gate is not waived: Accepted needs a host advertising fixtureErrors and passing 0245.fixture-error-replayed. The RFC 0156 §B review is owed. |
| 0246 | a trajectory-failed trial cannot carry a task or a suite to a pass — the mean task rule and suite passed read a gating score; optional gatedScore / gatedAggregateScore | 2026-10-15 | 2026-10-16 | 1 day (the COMPATIBILITY.md §3 90-day window, comment window waived, not run) | safety-fix. STEWARD OVERRIDE — outside this grant, which permits only additive RFCs. It overrides two rules: the §3 90-day window (no embargo is claimed; the defect was public in openwop#2003 from filing) and RFC 0147 §A.6 (certification: 0246.* rows on every major-2 bundle). Steward direction 2026-10-16: "We need to find a way to waive this 90 day period", then "Yes to both, record the override and finish #2003". Rationale: the window gives implementers time to migrate, and the only implementers of agents.evalSuite.trajectory are steward hosts. openwop-app already gates; MyndHyve (73befc109) does not, and the override is conditional on its fix shipping first or with the RFC (gap G3). Advisory GHSA-ffx7-pm5h-v6pq. The evidence gate is not waived: Accepted needs a certified bundle passing 0246.mean-gated and 0246.suite-gated. The RFC 0156 §B review is owed. |
| 0247 | bounded stream lifetime — optional resumable query parameter on streamRunEvents / streamHostEvents, one limits facet (maxStreamAgeSec) | 2026-10-15 | 2026-10-15 | 0 days (comment window waived, not run — Draft → Active in the filing PR) | additive (COMPATIBILITY.md §4, an optional capability off by default; the hold-open MUST is unchanged for a consumer that does not opt in). Steward direction 2026-10-15: the maintainer instructed "Proceed with all phases", which included filing this RFC Active. Routine bootstrap waiver under GOVERNANCE §"Sole-steward operation". RFC 0147 §A.6 does not apply: stream lifetime is not identity, authorization, isolation, idempotency, replay, external effects or certification, and no conformance rows are added. Accepted needs a host bounding opted-in streams while passing the existing resume legs, and the v2 SDKs opting in. |
| 0248 | ctx.callAI reports its provider attempts and takes a per-call retry policy — optional result attempts, optional request retry, one aiProviders.callAccounting facet member | 2026-10-19 | 2026-10-22 | 3 days (comment window waived, not run; no comments were filed on openwop#2024) | additive (COMPATIBILITY.md §4: two optional fields and an optional capability; a host that does not advertise it is unchanged). STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting replay; §A.5 requires attempts to replay identically. Steward direction 2026-10-22: the maintainer instructed "Waive the comment window on RFC 0248 and proceed to active". The evidence gate is not waived: Accepted needs a deployed host advertising aiProviders.callAccounting and passing the callai-attempt-accounting legs. The RFC 0156 §B review is deferred by the 2026-10-17 steward exemption. |
| 0249 | v2 proposal operations and a verifiable install read-back — seven /proposals operations, three scopes, agents.proposals.clientDrafts / readback, activation.installedArtifact | 2026-10-24 | 2026-10-24 | 0 days (comment window waived, not run; filed as Draft in openwop#2030) | additive (COMPATIBILITY.md §4: new operations, optional fields and scopes, three new error codes; a host that does not advertise agents.proposals is unchanged). STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting certification; this RFC adds 0249. rows to major-2 bundles and moves two protocol-tier invariants to witnessable-gated. Steward direction 2026-10-24: the maintainer instructed "waive the 7 day window for 0249". The evidence gate is not waived: Accepted needs a certified host passing the 0249. host legs. The RFC 0156 §B review is deferred by the 2026-10-17 steward exemption. |
| 0250 | opt-in host-event replay and explicit resync — hostEvents.replay {minRetentionSeconds}, replay=required, 409 host_event_resync_required | 2026-10-24 | 2026-10-24 | 0 days (comment window waived, not run; filed as Draft in openwop#2035) | additive (COMPATIBILITY.md §4: an optional facet member, an opt-in query, one error code; requests without the parameter are unchanged). STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting certification; this RFC adds 0250. rows to major-2 bundles. Steward direction 2026-10-24: the maintainer chose "Waive it" for RFC 0250. The evidence gate is not waived: Accepted needs a certified host passing the 0250. host legs. The RFC 0156 §B review is deferred by the 2026-10-17 steward exemption. |
| 0251 | an eval run names its modes and regression baseline — createRun evalModes / baselineRunId, agents.evalSuite.baselineSelection | 2026-10-26 | 2026-10-26 | 0 days (comment window waived, not run; filed Active) | additive (COMPATIBILITY.md §4: two optional createRun properties and an optional facet member; requests without them are unchanged). STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting certification; this RFC adds 0251. rows to major-2 bundles. Steward direction 2026-10-25: the maintainer chose "Waive it" for RFC 0251. The evidence gate is not waived: Accepted needs a certified host passing the 0251. host legs. The RFC 0156 §B review is deferred by the 2026-10-17 steward exemption. |
| 0252 | an eval task takes its fixtures from a recorded run — createRun fixtureRuns, agents.evalSuite.recordedFixtures, eval.started.fixtureRuns | 2026-10-26 | 2026-10-26 | 0 days (comment window waived, not run; filed Draft in openwop#2046 with the window to 2026-11-02) | additive (COMPATIBILITY.md §4: one optional createRun property, an optional facet member and an optional event property; requests without them are unchanged). STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting tenant isolation and replay; §C scopes a source run to the caller's tenant and §D/§E replay recorded tool outcomes. Steward direction 2026-10-26: the maintainer instructed "Waive the comment window for RFC 0252 and work with other sessions to move it to accepted". The evidence gate is not waived: Accepted needs a certified host passing the 0252.* host legs. The RFC 0156 §B review is deferred by the 2026-10-17 steward exemption. |
| 0253 | read back an installed workflow-chain or agent pack — getInstalledPack, the pack-kind readback rules | 2026-10-29 | 2026-10-31 | 0 days of the 7 (comment window waived, not run; filed Draft in openwop#2058 with the window to 2026-11-05) | additive (COMPATIBILITY.md §4: one new operation and description changes; the new MUSTs bind only a host listing a pack kind in agents.proposals.readback). STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting tenant isolation; §A scopes the read to the caller's tenant. Steward direction 2026-10-31: offered a waiver of the window to 2026-11-05, the maintainer answered "proceed". UQ 1–6 were decided after an /architect review the maintainer approved (openwop#2071). The evidence gate is not waived: Accepted needs a certified host passing a pack kind's 0253.* host legs. The RFC 0156 §B review is deferred by the 2026-10-17 steward exemption. |
| 0255 | delete the AI Envelope from v2; the steward-deletion corrections class | 2026-10-30 | 2026-10-30 | 0 days (comment window waived, not run; filed and moved Active in the same PR) | breaking, landing in a 2.x minor through the class this RFC adds. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. It affects security invariants and certification. Steward direction 2026-10-30: "Waive the 7 day comment window"; a breaking RFC's window is 30 days, and the instruction is recorded as running none. GOVERNANCE.md "Evidence gates are never waived" applies: Accepted needs a certified bundle. |
| 0256 | the tool-turn contract: channels, admission order, trust restricts approvers, recovery and replay, provider-executed tools | 2026-10-30 | 2026-10-30 | 0 days (comment window waived, not run; filed and moved Active in the same PR) | additive, with §C a Class 3 correction candidate. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. It changes approval and prompt-injection rules. Steward direction 2026-10-30: "Waive the 7 day comment window". The evidence gate is not waived. |
| 0254 | the agent deployment transition contract at v2 — deployment_state_conflict, optional transitionRunId, transitionAgentDeployment 202/409, the agents.deployment transition rules | 2026-10-29 | 2026-10-29 | 0 days (comment window waived, not run; filed and moved Active in the same PR) | additive (COMPATIBILITY.md §2.4: one registered code, one optional record property, two responses on an operation no host serves, rules for transitions v2 left unspecified). STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting certification; the rulings tighten v2-deployment-lifecycle and the protocol-tier invariant deployment-promotion-fail-closed. Steward direction 2026-10-29: the maintainer instructed "proceed, and waive the comment window". The evidence gate is not waived: Accepted needs a certified host passing the 0082.* legs (openwop-app#5393). The RFC 0156 §B review is deferred by the 2026-10-17 steward exemption. |
| 0257 | run status when every terminal node is skipped — run.completed.skippedTerminals, childSkippedTerminals, the EdgeCondition.left resolution pin | 2026-11-02 | 2026-11-02 | 0 days (comment window waived, not run; filed and moved Active in openwop#2076) | additive (COMPATIBILITY.md §4: a rule for a previously undefined state, one optional run.completed property, a pin on a previously unpinned path). STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting replay; §A.4 binds a replay fork's disposition. Steward direction 2026-11-02: the maintainer instructed openwop-app-14 "skip the 7 day comment window and move to active", and confirmed it in the openwop-be session ("Yes, waive it"), approving the decisions on UQ 1–8, R1 and R6. The evidence gate is not waived: Accepted needs openwop-app passing the 0257.* legs on a certified cut. The RFC 0156 §B review is deferred by the 2026-10-17 steward exemption. |
| 0236 | Host events — events without a run-log position: events.md §Host events, webhooks.md §Delivery, conversation.md §channelPresence, the hostEvents family | 2026-10-05 | 2026-10-05 | 0 days (comment window waived, not run — filed Draft the same day) | additive with a safety-fix clause. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting isolation; §D binds every hostEvents message to its tenant and adds invariant host-event-tenant-isolation. Steward direction 2026-10-05: the maintainer directed "proceed with moving the RFC to accepted". The evidence gate is not waived: Accepted needs the openwop.requirement.0236.* ids on a certified major-2 bundle. The RFC 0156 §B review is owed. |
| 0237 | Declared nondeterminism names its sources; false is not a v2 state: replay.md §Declared nondeterminism, events.md §Envelope contracts, nondeterminismPolicy.sources | 2026-10-06 | 2026-10-06 | 0 days (comment window waived, not run — filed Draft the same day with the window to 2026-10-13) | additive. STEWARD OVERRIDE of RFC 0147 §A.6 — outside this grant. §A.6 forbids bootstrap waiver language from shortening the window for RFCs affecting certification; §B adds a requirement id a major-2 bundle records. Steward direction 2026-10-06: the maintainer answered "yes to both" to waiving the window and moving 0237 to Active. The evidence gate is not waived: Accepted needs the two openwop.requirement.0237.* ids on a certified major-2 bundle. The RFC 0156 §B review is owed. |
| 0170 | v2 identity (RFC 0167 child C.3) | 2026-09-03 | 2026-09-03 | < 1 day | breaking (v2) under the RFC 0167 program; window waived under GOVERNANCE §"Sole-steward operation"; RFC 0147 §A.6 override inherited from and named in the parent (identity and authorization are this child's whole surface). Evidence gate not waived: Accepted at Phase 3 on the nine v2 scenarios with the seam-gated legs recorded as such. |
| 0171 | v2 wire envelope (RFC 0167 child C.4) | 2026-09-03 | 2026-09-03 | < 1 day | breaking (v2) under the RFC 0167 program; window waived under GOVERNANCE §"Sole-steward operation"; RFC 0147 §A.6 override inherited from and named in the parent (replay and external effects through the event log and the error registry). Evidence gate not waived: Accepted at Phase 3 on the ten v2 scenarios; the fork-a-v1-run leg on both matrix hosts. |
| 0173 | v2 security defaults (RFC 0167 child C.6) | 2026-09-03 | 2026-09-03 | < 1 day | breaking (v2) under the RFC 0167 program; window waived under GOVERNANCE §"Sole-steward operation"; RFC 0147 §A.6 override inherited from and named in the parent (authorization, isolation, replay, external effects). Evidence gate not waived: Accepted at Phase 3 on the nine v2 scenarios with the effect-seam manifest as the replay witness. |
| 0175 | v2 transports and embedded protocols (RFC 0167 child C.8) | 2026-09-03 | 2026-09-03 | < 1 day | breaking (v2) under the RFC 0167 program; window waived under GOVERNANCE §"Sole-steward operation"; RFC 0147 §A.6 override inherited from and named in the parent (identity and authorization at the peer boundary). Evidence gate not waived: Accepted at Phase 3 on the eight v2 scenarios and the interop threat model's existence. |
| 0176 | v2 persisted data and coexistence (RFC 0167 child C.9) | 2026-09-03 | 2026-09-03 | < 1 day | breaking (v2) under the RFC 0167 program; window waived under GOVERNANCE §"Sole-steward operation"; RFC 0147 §A.6 override inherited from and named in the parent (replay and fork read persisted identity and effect records). Evidence gate not waived: Accepted at Phase 3 on the seven v2 scenarios with the three consumers pinned. |
| 0177 | v2 registry, packs, and the extension tail (RFC 0167 child C.10) | 2026-09-03 | 2026-09-03 | < 1 day | breaking (v2) under the RFC 0167 program; window waived under GOVERNANCE §"Sole-steward operation"; RFC 0147 §A.6 override inherited from and named in the parent (pack trust path and signing). Evidence gate not waived: Accepted at Phase 3 on the seven v2 scenarios and a green registry-check.sh over registry/v2/. |
| 0217 | after a subscription is unregistered, its dead-letter read answers as though it never existed (amends RFC 0188 §A; RFC 0215 gap G5) | additive (7-day) | 2026-09-26 | steward | No identity or auth surface is narrowed: the only new answer is the 404 not_found identity.md §5 already gives an unknown id, on a read gated on a facet. Filed rather than edited into RFC 0188 because 0188 is Accepted and may carry only witnessed requirements. |
| 0218 | an audit checkpoint signs its Merkle root, and the root is pinned (auth-profiles.md §"Audit-log integrity" 3; the checkpoint export) | Class 3 correction + additive (7-day) | 2026-09-27 | steward | RFC 0147 §A.6 does not apply: the bytes pinned are an audit-log checkpoint's, which no certification bundle, witness digest or replay digest covers. The construction pinned is the one both reference hosts and the out-of-band verifier already use; no deployed host moves. §C (the anomaly shape, 2026-09-28) was added in place while Active under the same waiver: additive optional members plus a Class 3 pin of chainValid, with the two reference hosts, the only implementers, corrected in the same cycle. |
| 0219 | a client announces the protocol version it implements in OpenWOP-Client-Version (versioning.md §1.5; extends RFC 0172 §A.5) | additive (7-day) | 2026-09-27 | steward | RFC 0147 §A.6 does not apply: the header neither authenticates nor selects a contract, and no replay, external-effect or certification preimage covers it. The only host behaviour it narrows (a malformed value read as 0.0 and refused) was undefined; the new malformed leg waits on the two affected hosts being measured before the PR merges. |
| 0224 | audit-log integrity gets a v2 home (new core family auditLogIntegrity; security-defaults.md §Audit-log integrity) | additive (7-day) | 2026-09-28 | steward | RFC 0147 §A.6 does not apply: an audit-log checkpoint is covered by no certification bundle, witness digest or replay digest, and the RFC advertises an existing optional profile rather than changing replay or external effects. RFC 0147 §A's optional-capability freeze is spent (2026-08-20). The evidence gate is not waived: Accepted waits for a certified public v2 bundle. |
| 0228 | the error codes v1 named for host services, decided for v2 (errors.md §Host-service refusals and §Unadvertised operations; nine errors.json rows) | additive (7-day) | 2026-09-28 | steward | RFC 0147 §A.6 does not apply: the RFC names codes for refusals whose rules already exist. The SSRF guard, tenant isolation and the deploy: scope check keep their text, a recorded failure code replays as recorded, and no bundle, witness or replay preimage covers an error code. Filed Draft with the full window to 2026-10-05; the maintainer waived it the same day. The pack-facing consolidation (secret_ → credential_ plus details.reason) is disclosed in §Compatibility (risk R1), and the one host-visible status move (an unadvertised /prompts answers 404, not 501) is gap G6. The evidence gate is not waived. |
| 0231 | a host says which budget exhaustion behaviours it serves (optional budget.onExhaustion facet; runs.md §Refusals, budget-policy.md §D) | additive (7-day) | 2026-10-02 | steward | RFC 0147 §A.6 does not apply: the RFC adds a capability facet and a create-time refusal with an existing code. It changes no identity, authorization, isolation, idempotency, replay, external-effect or certification decision, and budget is on no profile floor. Filed Draft with the full window to 2026-10-09; the maintainer waived it the same day. An absent facet keeps today's meaning (gap G1), so no existing advertisement changes. The evidence gate is not waived. |
When the count gets uncomfortable (e.g., > 5 waivers within a 30-day window, or > 15 total before the first non-steward maintainer joins), that's a signal to slow down and stage at least one RFC through a real 7-day window even without external reviewers — exercising the process is itself a credibility surface.
Tripwire status: crossed (since 2026-06-11). The ledger is past the > 15-total threshold with no non-steward maintainer, and the 2026-05-25 – 2026-05-30 cluster alone exceeded the 5-in-30-days signal. Per the policy, the slow-down response should be evaluated, and at least one upcoming RFC should be staged through a real 7-day comment window even without external reviewers. The tripwire is deliberately retained, not raised.
Waivers not annotated at the time (added 2026-08-20)
These twenty-one RFCs used the waiver but were never entered above. The rationale column is absent rather than reconstructed — nobody recorded why at the time, and a plausible after-the-fact reconstruction would be worse than an honest gap: it would read as a decision that was made. What is below is derived from each RFC's own header.
| RFC | Title | Created | First promotion | Status |
|---|---|---|---|---|
| 0043 | Registry and extension-policy | 2026-05-22 | 2026-07-07 | Accepted |
| 0101 | Multi-party group conversation (shared transcript, speaker attribution) | 2026-06-14 | 2026-06-22 | Accepted |
| 0103 | Localized Content Surface — durable, authored, structured localized content (p | 2026-06-17 | 2026-06-17 | Accepted |
| 0105 | Speech synthesis adapter (ctx.callSpeechSynthesizer) — text-to-speech as a f | 2026-06-20 | 2026-06-21 | Accepted |
| 0106 | — | — | — | ? |
| 0108 | Self-hosted / OpenAI-compatible provider class (aiProviders.selfHosted[]) | 2026-06-23 | 2026-06-24 | Accepted |
| 0109 | Conversation-turn model provenance (agent.model) | 2026-06-24 | 2026-06-24 | Accepted |
| 0110 | — | — | — | ? |
| 0121 | — | — | — | ? |
| 0124 | — | — | — | ? |
| 0147 | Protocol Integrity and Standards-Readiness Program | 2026-08-11 | 2026-08-16 | Accepted |
| 0148 | Non-Vacuous Conformance and Certification Evidence | 2026-08-11 | 2026-08-16 | Accepted |
| 0149 | Machine-Contract and Version Reconciliation | 2026-08-11 | 2026-08-16 | Accepted |
| 0150 | Effect Identity, Replay, and Split-Brain Safety | 2026-08-11 | 2026-08-12 | Accepted |
| 0151 | Compensation and Partial-Failure Profile | 2026-08-11 | 2026-08-17 | Accepted |
| 0152 | A2A 1.0 Versioned Composition | 2026-08-11 | 2026-08-16 | Accepted |
| 0153 | MCP 2026-07-28 Versioned Composition | 2026-08-11 | 2026-08-16 | Accepted |
| 0154 | Workload Identity, Delegation, Telemetry, and Provenance Assurance | 2026-08-11 | 2026-08-16 | Accepted |
| 0155 | Core Profile and Extension Discipline | 2026-08-11 | 2026-08-16 | Accepted |
| 0156 | Governance, Independent Assurance, and Claims Policy | 2026-08-11 | 2026-08-12 | Accepted |
| 0157 | Chain fragments carry compensation (RFC 0013 revision × RFC 0151 §B) | 2026-08-16 | 2026-08-16 | Accepted |
Anyone with first-hand knowledge of one of these decisions should move its row into the curated table above with the real rationale.
Spec version bump runbook
The repo holds spec/v2/ (the current major) and spec/v1/ (frozen since v1 end of support on 2026-10-04), rendered at /spec/v2/ and /spec/v1/. The major is the URL-stability boundary: a minor edits the major's directory in place, and a new directory appears only for a new major.
Minor or patch release (the common case)
The release manager:
- Lands the additive prose, schema and RFC changes in
spec/v2/andschemas/v2/. API changes go into the source documentsapi/openapi.yamlandapi/asyncapi.yaml(orscripts/derive-v2-api-prose.yaml), andapi/v2/is regenerated from them byscripts/derive-v2-api.py(CONTRIBUTING.md§"OpenAPI and AsyncAPI"). - Bumps
spec/v2/release.jsonand the package version sites, and adds a## [2.N.P]section toCHANGELOG.md(PUBLISHING.md§"Version sites"). - Tags and publishes per
PUBLISHING.md.
The public site is published from a separate repo. openwop/openwop-site renders this corpus pinned to an exact openwop commit. Its pin-bump workflow opens a PR as main moves, and merging that PR redeploys the site. No site build or deploy step runs in this repo.
The next major
A new major is rare and touches every OpenWOP repository. The RFC that opens it sets the plan (COMPATIBILITY.md §5). The work, in order:
In this repository:
- Create
spec/vN/beside the current major, andschemas/vN/with every$idunderhttps://openwop.dev/spec/vN/. The previous major's directories stay in place and become read-only. - Produce the new API documents, the seams document and the operation-path manifest. Decide, and write down, which document is the source and which are derived (for v2,
scripts/derive-v2-api.pyderivesapi/v2/from the v1 documents). - Enforce the deprecation register: every entry due at
N.0is absent from the new tree, and the check fails otherwise. - Publish the new suite major and
@openwop/spec-artifactsperPUBLISHING.md, with the scenarios that run against both majors during the overlap. - Add the
## [N.0.0]CHANGELOG section: the one release where breaking changes are permitted.
In the sibling repositories:
openwop-site: render everyspec/v*/directory, point/spec/latest/at the new major, and keep the old major's pages.openwop-sdks: publish the SDK majors (npm, PyPI, and a Go module path with the/vNsuffix). The old majors stay installable for the retention floor (spec/v2/core/overview.md§"Old-major retention floors").openwop-registry: publish the registry for the new major (re-signed manifests, or a signed compatibility overlay) and the peer-dependency alias table.openwop-examplesandopenwop-cli: bring the reference hosts to the new floor with fresh certification bundles, and record the CLI's disposition.
Hosts (INTEROP-MATRIX.md):
- Each host advertises both majors in
protocolVersions[]during the overlap, publishes a non-vacuous certification bundle for the new major, and gets a matrix row. The old major's end-of-support date then followsCOMPATIBILITY.md§5.
Anti-pattern. Don't create a minor-version directory such as spec/v2.3/. Minors are in-place edits of the major's directory.
See also
GOVERNANCE.md— decision rules, role definitions, path to working group.RFCS/0001-rfc-process.md— formal RFC mechanism that maintainer approvals operate on.COMPATIBILITY.md— what counts as additive vs. breaking; what maintainers gate.CODE_OF_CONDUCT.md— behavioral expectations enforced under "Removal for cause."ROADMAP.md— the vendor-neutral-org migration tripwire that depends on this file.docs/recruitment/external-host.md— per-target host-recruitment outreach drafts.docs/recruitment/external-pack-author.md— external pack-author recruitment.