ENTITY v3.4.2 Research & Citation
ENTITY publishes machine-readable citation and software metadata so researchers, architects, reviewers and procurement teams can identify the exact software release they evaluated rather than citing a moving repository branch.
Current citable software release
| Field | Value |
|---|---|
| Software | ENTITY: Sovereign Digital Authority, Provenance, Data Rights, Recovery and BTDU |
| Version | 3.4.2 |
| Release date | 2026-09-26 |
| Author | Shawn Blackmore, Blackmore Technology Group Limited |
| License | Apache-2.0 |
| Protected release commit | 6dfa3d6cc738d9369cf092d2782676bf4f2a46e4 |
| Release tree | f90bf74e29899f82d0a4ee321604346241bba4de |
Machine-readable metadata
CITATION.cff
GitHub-compatible Citation File Format metadata identifies the v3.4.2 software release, author, date, license and research keywords.
CodeMeta
codemeta.json publishes structured software metadata for research-software catalogs and machine ingestion.
Zenodo-ready metadata
.zenodo.json is prepared for software archiving and DOI publication. No Zenodo DOI is claimed on this page unless and until one is actually issued.
Suggested citation before a DOI is issued
Until a DOI-backed archive record exists, cite the exact tagged software release rather than main:
Evidence and reproducibility boundary
The released software records BTG-controlled regression, repository-safety, dependency-review, public-conformance and protected-state recovery evidence. Those results are engineering evidence for the identified release; they are not presented as unrelated third-party validation.
Independent evidence is intentionally separated into public reproduction, interoperability, security-audit, hardware, multi-host, certified-device and assessor pathways. A negative independent result is evidence and should not be rewritten into a pass.
External verification
Bounded tasks let an unrelated engineer reproduce a campaign, test onboarding, inspect BTDU boundaries, or independently implement one classifier.
External qualification
Hardware custody, physical multi-host, certified-device, independent audit and assessor gates each maintain their own evidence chain.
Archival status
A Software Heritage archival request has been submitted for the public repository. This page does not claim a completed public archive identifier until a resolvable Software Heritage record is available. Zenodo metadata is prepared, but no DOI is claimed until Zenodo actually issues one.
For reviewers
When publishing analysis of ENTITY, identify the exact release/tag/commit, the material actually reviewed, test environment, methodology, exclusions and whether the work was independent of BTG. That keeps conclusions bounded to reproducible evidence rather than a generic project name.