Implementation Packages
An implementation package is a deployable configuration/profile stack over the same ENTITY runtime. Packages add domain schemas, mappings, fixtures and deployment guidance; they do not fork or replace core ENTITY authority semantics.
Package contents
Public packages can include schemas, mappings, templates, conformance fixtures, SDK material, deployment examples, required evidence definitions and a package verifier.
Deployment sequence
CONFIGURE-ME rule
Example placeholder facts must be replaced with organization-specific values such as organization, jurisdiction, authority source, issuer/controller Entity and domain-specific policy/namespace. A package with unresolved placeholders is not a production deployment.
Authority boundary
A package can constrain a deployment and require evidence; it does not become sovereign authority over the objects it describes. External standards referenced by a package retain their own semantics and conformance requirements.
Integrity and supersession
Sealed historical package payloads retain their package hashes and version context. Documentation can evolve around them without pretending a changed package still has the old hash. Publish a new version when package bytes or semantics change.
Version boundary
Use v3.4.3 for current runtime/package work. Historical v3.4.2 package evidence remains reproducible against its original tagged state and should not be relabeled as a v3.4.3 execution.