Profile Registry
The Global Profile Registry provides versioned, signed, composable context/constraint definitions. Profiles can describe global, jurisdictional, industry, domain, privacy, trust or disclosure requirements without becoming a new authority system.
profile_is_not_authority and standards_mapping_is_not_normative_equivalence. Profiles constrain interpretation/workflow; they do not mint sovereign authority.Registry responsibilities
- Stable profile identifier and explicit version.
- Schema SHA-256.
- Issuer identity and signature.
- Parent-profile references.
- Applicable object/evidence types.
- Policy and conflict behavior.
- Standards mappings without normative-equivalence claims.
- Historical signed variants where semantic rebinding is explicitly allowed.
Profile stack
resolve_stack() requires an explicit profile set, requires a GLOBAL profile, verifies parent references and returns exact profile hashes. Missing required parents or mismatched ref/hash pairs fail closed.
Historical interpretation
A passport references the profile version/hash used at issuance. Updating the registry must not silently reinterpret old signed passports. Supersede, migrate or explicitly import a signed semantic-equivalent variant under the implemented rules.
Conflict policy
The registry recognizes explicit conflict policies such as FAIL_CLOSED and MOST_RESTRICTIVE. Do not invent permissive defaults when profiles disagree.
Version boundary
This page documents the current v3.4.3 registry. Historical v3.4.2 profile evidence remains under its original labels; the current runtime label is not back-propagated into previously signed profile records.