Dependency profile
- Dependency owner
- Independently deployed Eviulon and Patefacere publication authorities
- Affected population
- Humans, agents, identity users and public reviewers
- Substitutability
- CONSTRAINED
- Switching cost
- HIGH
- Replacement time
- Scenario-specific; must be measured and tested, not assumed.
- Concentration level
- HIGH
- Non-Domination Test
- PASS_REQUIREMENTS_DEFINED
Abuse and failure paths
Abuse: One site becomes authoritative for the other, stale state presented as success, hidden private-data transfer or rendering dependency.
Failure: Partition, replay, schema conflict, compromised manifest, wrong origin or unavailable counterpart.
Required exit and alternatives
Exit: Separate deployments, explicit states, monotonic sequence, last-known-good, local rendering and correction notices.
Portability: Portable public manifests and append-only observations; no citizen or credential bodies.
Interoperability: Versioned open JSON schemas, migration guidance and deterministic conformance corpus.
Independent alternative: Each site remains independently useful and may operate with connector UNAVAILABLE.
Emergency handback: Reject candidate, preserve accepted state, publish UNAVAILABLE/CONFLICT and reconcile only after evidence passes.
Disconfirming evidence
- Failed exit drill
- Unavailable independent alternative
- Retaliation for attempted exit
- Material portability gap
- Undisclosed common-mode dependency
Truth boundary
Static risk-governance record. It does not prove an operational service, market share, capacity, dependency, alternative, or successful exit drill.
Authority and record status
Responsible authority: Eviulon and Patefacere independent publication authorities.
Static concentration-governance record; no operational alternative or exit drill is proven.
Revision date: . Public corrections may be initiated through the diplomatic contact route.