Developer workflow · ENTITY v3.4.3
Create a New Profile
Rule: a profile constrains interpretation or deployment behavior; it does not manufacture authority, ownership, legal status or standards conformance.
- Define purpose. State exactly what deployment/context constraint the profile adds.
- Identify issuer/steward. Record the Entity authorized to publish the profile. Do not use the profile itself to manufacture authority.
- Choose an identifier and immutable version. The registry forms a stable profile reference from these values.
- Define schema commitment. Supply the schema SHA-256 and define required fields/allowed values/failure behavior.
- Choose profile kind. Use the implemented kinds: GLOBAL, JURISDICTION, INDUSTRY, DOMAIN, PRIVACY, TRUST or DISCLOSURE.
- Declare parents and object/evidence scope. Parent references must resolve in composed stacks; missing parents fail closed.
- Add standards mappings. Identify the external version and preserve
normative_equivalence_claimed: false. - Select conflict behavior. Use an implemented conflict policy such as
FAIL_CLOSEDorMOST_RESTRICTIVE. - Create valid and invalid fixtures. Test missing parents, altered hashes, invalid signatures and conflicting variants.
- Register and sign. Publish through the versioned registry with the issuer Entity signature.
- Test composition. Resolve the exact profile stack and hashes used by the consuming passport/deployment.
Do not
Do not encode unverified legal conclusions as protocol facts, retroactively alter an existing signed profile version, allow a provider/platform to gain authority merely because its profile is loaded, or claim an external standard is normatively equivalent without separate evidence.
Historical records
Profiles previously issued under v3.4.2-era campaigns remain historical signed records. Creating a current v3.4.3 profile does not rewrite or relabel those earlier objects.