Developer reference
Implementation Packages
An implementation package is a deployable configuration of the one ENTITY Global Passport for a domain. Packages contain mapping/configuration material; they do not fork core sovereignty semantics.
Package contents
Public packages can include schemas, mappings, templates, conformance fixtures, SDK material, deployment examples and a package verifier.
Deployment sequence
select package → configure organization facts → connect systems/data → ingest → verify passport → run conformance → deploy
CONFIGURE-ME rule
Example placeholder facts must be replaced with organization-specific values such as organization, jurisdiction, authority source and the domain-specific policy/namespace. A package with unresolved placeholders is not a production deployment.
Integrity
Sealed historical package payloads retain their package hashes. Documentation can evolve around them without pretending a changed package still has the old hash.