v0.21.2 - Operator Onboarding Status

v0.21.2 - Operator Onboarding Status

Added

• An "Onboarding and Initial Backers (proof pending)" section in the founding community operator documentation, recording that additional operators and backers are being onboarded and are preparing their own endpoints, treaties, and proof bundles.

Changed

• Made the verification gate explicit: a participant is named in the operator cohort only when public proof artifacts (a reachable sovereign endpoint, a signed treaty_id, and a redacted proof bundle) are committed under examples/.
• Bumped package metadata to 0.21.2.

Notes

• No organization, identity provider, or partner is named as an implementer or operator until its proof artifacts exist. This keeps the registry aligned with the external-operator proof workflow rather than asserting unverified adoption.

Verified

• Sphinx docs (warnings-as-errors), full pre-push hooks (mypy, compileall, sphinx, pytest), and package build passed.