[Review] Obtain two independent M0 protocol and safety reviews

[veil-chow-fyaic]

Goal

Satisfy the M0 exit criterion requiring two independent design reviews before declaring the foundation implementable without undocumented assumptions.

Reviewer brief

Review the protocol from two perspectives:

1. distributed-systems correctness: idempotency, ordering, expiry, replay, freshness, lifecycle, and audit;
2. agent/harness safety: context sovereignty, provenance, consent, structured gates, wake/interrupt budgets, and cross-harness degradation.

Evidence required

• Reviewer affiliation or relevant perspective is disclosed.
• Findings identify exact documents or schema paths.
• Each finding is accepted, resolved, deferred with rationale, or rejected with rationale.
• At least one review comes from outside the maintainer organization.
• Final review artifacts are linked from the M0 milestone.

[veil-chow-fyaic]

Internal review round — 2026-08-20

Three independent read-only Codex sub-agent review lanes examined main@c38873026222175433fb86f2fcac1a655ffcc932:

• distributed-systems and protocol correctness: request changes;
• authorization, provenance, privacy, and consent safety: request changes;
• cross-harness implementability and Kimi feasibility: request changes.

The reports are being added under docs/09-reviews in the current implementation PR. They found no P0 issue, but identified M0 blockers covering crash/idempotency semantics, authenticated principals and grants, revocation-at-admission, cross-state CAS, mailbox/registration bindings, partial interruption, external verification, summary disclosure, and capability coherence.

These internal passes do not satisfy this issue’s organizationally independent external-review criterion. Kimi Code was also attempted as a different-model review/test path: ACP v1 handshake against local Kimi Code 0.36.1 passed, but the live model call returned HTTP 403 because the account billing-cycle quota is exhausted. This issue remains open.