Developer workflow
Create a New Profile
- Define purpose. State exactly what deployment/context constraint the profile adds.
- Identify authority. Record who is authorized to publish/steward the profile. Do not use the profile itself to manufacture authority.
- Choose an identifier/version. Treat versions as immutable interpretation targets.
- Define schema/constraints. Specify required fields, allowed values and failure behavior.
- Add mappings. Where mapping to an external standard, identify the external version and state that mapping is correspondence—not normative equivalence.
- Create fixtures. Include valid and invalid examples.
- Test composition. Verify the profile composes with other profiles without scope escalation or contradictory silent defaults.
- Register/review. Add to the versioned registry through normal review/governance.
Do not
Do not encode unverified legal conclusions as protocol facts, retroactively alter an existing profile version, or add a profile that silently transfers user authority to a platform/provider.