Dependency profile
- Dependency owner
- Plural standards bodies and implementers
- Affected population
- Governments, companies, developers, agents and users
- Substitutability
- MODERATE
- Switching cost
- MEDIUM
- Replacement time
- Scenario-specific; must be measured and tested, not assumed.
- Concentration level
- MEDIUM
- Non-Domination Test
- PASS_REQUIREMENTS_DEFINED
Abuse and failure paths
Abuse: Standards capture, patent ambush, artificial incompatibility and declaring one implementation mandatory.
Failure: Fragmentation, ambiguous profiles, withdrawn standard or incompatible revision.
Required exit and alternatives
Exit: Open participation, disclosed interests, versioned profiles, migration windows and multiple implementations.
Portability: Portable schemas, test vectors and conformance results.
Interoperability: Public specifications, deterministic tests and backward-compatible profiles.
Independent alternative: Competing standards and translation gateways.
Emergency handback: Hold current profile, publish incompatibility, support migration and avoid forced downgrade.
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: Standards and public-governance 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.