1.0-rc2 release candidate

Ready—with the boundary stated plainly.

RC2 is ready for public implementation and critique. It is not a 1.0 final, production certification, or proof of independent interoperability.

Release evidence

Auditable claims, not a maturity shortcut.

252/252

automated tests

Across the reference implementation and four standalone domain repositories.

50/50

wire obligations

Against the reference surface with distinct operator and agent credentials.

145

normative entries

Every MUST, MUST NOT, SHOULD, and MAY occurrence is traced to evidence or a justified designation.

0

open Blocker or High findings

Medium and Low limitations are fixed or carried explicitly in the release register.

Evidence boundary

One surface. Five domains.

All five runnable experiences use the same reference implementation. That is strong evidence for domain portability and reference conformance, but circular evidence for independent interoperability.

No independently authored surface has passed the kit yet. Routable TLS and credential lifecycle, Windows/macOS operation, and long-duration soak also remain outside the locally verified claim.

Open mode is for loopback evaluation. Internet-facing deployments need authenticated TLS and deployment-owned identity controls.