Reference network operator and continuity

We Are 14 Inc. is preparing the initial XCIM reference network during v0.x.

Planned operator scope

The operator is expected to coordinate the initial issuer registry, transparency publication, current-state distribution, Polygon anchoring, mirrors and status surface. None of these components is public or production-active today.

Public and private boundaries

Public data will be limited to issuer metadata, public keys, domain/application binding state, signed roots, proofs, anchors and protocol metadata. Recipient addresses, recipient records and predictable email hashes will not be published.

Keys and environments

Test and production environments will use separate identities and keys. The custody, rotation, suspension and recovery procedures must be published before the relevant component becomes active. Polygon Amoy is planned for test; mainnet is not active.

Continuity

Signed historical roots, anchors and mirrors are intended to remain independently reproducible. If the operator or an issuer stops operating, cached historical evidence remains checkable while current state eventually becomes indeterminate under each verifier’s freshness policy.

Participation

Independent issuers and verifiers will require public conformance criteria and test vectors before registration. Registry presence will publish facts; it will not grant universal trust.