Goal
Evaluate one public ENTITY domain package as a new developer against the current ENTITY v3.4.3 release/documentation context and report whether the package is understandable and reproducible without prior project knowledge.
Current core release: https://github.com/blackmore-technology-group/ENTITY/releases/tag/v3.4.3
Domain documentation: https://blackmore-technology-group.github.io/ENTITY-DOCS/domains/
Version boundary: ENTITY runtime v3.4.3 is current. BTDU remains component 3.4.2 unchanged. Historical package seals or v3.4.2 evidence remain historical and are not rewritten by this onboarding test.
The six public domain packages remain bounded deployment packages for the same ENTITY/Global Passport architecture; they are not six separate sovereignty systems.
Choose one of:
- Healthcare
- Finance
- Manufacturing
- AI
- Robotics
- Defence/Public-Unclassified
This is an onboarding/deployment-path test, not a request to deploy production data or prove regulatory compliance.
What to do
- Start from a clean clone of the selected public package repository.
- Read its README and
deployment.example.json.
- Read the matching current domain page in ENTITY-DOCS.
- Replace
CONFIGURE-ME placeholders with clearly fictional/non-production values.
- Run:
python tools/verify_package.py
- Follow the documented path far enough to understand how organization facts, mappings, the Global Passport and current ENTITY v3.4.3 fit together.
- Report anything unclear, missing, stale, unnecessarily difficult, or inconsistent with the current core documentation.
Useful output
A short onboarding report, documentation PR, reproducible setup failure, missing example or confusing field is useful.
Boundaries
- Use fictional/non-production configuration only.
- Do not commit credentials, private keys, live data, protected health information, financial records, classified/restricted information or operational secrets.
- Package verification does not establish regulatory compliance, objective external truth, legal title, safety certification or accounting fair value.
- Provider custody does not create ENTITY authority.
- Historical package/release integrity remains historical evidence; this task evaluates the current v3.4.3 adoption path.
A failed or confusing onboarding path is useful evidence if it is reproducible.
Goal
Evaluate one public ENTITY domain package as a new developer against the current ENTITY v3.4.3 release/documentation context and report whether the package is understandable and reproducible without prior project knowledge.
Current core release: https://github.com/blackmore-technology-group/ENTITY/releases/tag/v3.4.3
Domain documentation: https://blackmore-technology-group.github.io/ENTITY-DOCS/domains/
Version boundary: ENTITY runtime v3.4.3 is current. BTDU remains component 3.4.2 unchanged. Historical package seals or v3.4.2 evidence remain historical and are not rewritten by this onboarding test.
The six public domain packages remain bounded deployment packages for the same ENTITY/Global Passport architecture; they are not six separate sovereignty systems.
Choose one of:
This is an onboarding/deployment-path test, not a request to deploy production data or prove regulatory compliance.
What to do
deployment.example.json.CONFIGURE-MEplaceholders with clearly fictional/non-production values.Useful output
A short onboarding report, documentation PR, reproducible setup failure, missing example or confusing field is useful.
Boundaries
A failed or confusing onboarding path is useful evidence if it is reproducible.