Skip to content

ENTITY v3.4.0 — Global Passport, Continuous Provenance & Industry Packages - #41

Merged
blackmore-technology-group merged 29 commits into
mainfrom
entity-v3.4.0-development
Sep 24, 2026
Merged

blackmore-technology-group merged 29 commits into
mainfrom
entity-v3.4.0-development

Conversation

@blackmore-technology-group

Copy link
Copy Markdown
Owner

Release candidate for ENTITY v3.4.0.

Qualification evidence:

  • 177/177 complete regression PASS
  • 33/33 v3.4 targeted Global Passport / implementation-package tests PASS
  • 24/24 sealed Global Passport vectors PASS (12 valid / 12 invalid)
  • Canonical result SHA-256: ac7504cce70576008cff069607619660a4b9bf0cad43b3f3de81078f1e80d9ba
  • Rust, TypeScript, Go, C#, Java and Swift BTG-controlled implementations PASS the same canonical campaign

Architecture:

  • Preserves ENTITY → AUTHORITY → RIGHT → EVENT → VALUE
  • Adds one Global Passport with composable industry profiles, continuous provenance, a versioned registry and executable implementation packages
  • Industry packages configure the one Global Passport; they do not create six incompatible passport protocols
  • External standards are mapped, not redefined
  • Custody does not create authority; protocol/evidence verification does not establish objective external truth or regulatory compliance

Publication model:

  • ENTITY core publishes the universal Global Passport protocol and canonical package registry
  • Dedicated domain repositories are designated for Healthcare, Finance, Manufacturing, AI, Robotics and public/unclassified Defence packages

Claim boundary:
The six native implementations are BTG-controlled controlled-interoperability evidence, not unrelated third-party independence. Independent third-party interoperability, external security/cryptographic review and deployment-specific legal/regulatory determinations remain external work.

Copy link
Copy Markdown
Owner Author

Final v3.4.0 branch-native release verification completed on 2026-09-24.

PR head: 2d7529fbadb4dd04840d62b751294bf9a7f70ed5

Sealed release evidence

  • Release snapshot SHA-256: 3ff0e51ca2daabf50bc517e9c6e3438e8c150f1560cca6c99621621e3c855a90
  • Release manifest file SHA-256: a47fe94750ca0e2ff3b466ece5d39d9ad161f4c447227fe6dc03094d7099b0a5
  • Canonical package registry SHA-256: d59e93c0569b0c21bbb214da1afb567ad02324f581e1a2bfb2460a9c38ca7295
  • Global Passport canonical result SHA-256: ac7504cce70576008cff069607619660a4b9bf0cad43b3f3de81078f1e80d9ba

Fresh-download verification from the actual PR branch

  • Global Passport campaign: 24/24 PASS (12 valid / 12 invalid)
  • Executable domain packages: 6/6 PASS
  • Release manifest verification: PASS
  • Repository safety: 3/3 PASS
  • Complete regression evidence remains 177/177 PASS
  • Six BTG-controlled native implementations remain PASS: Rust, TypeScript, Go, C#, Java, Swift

GitHub checks on this head

  • dependency-review: success
  • ENTITY public conformance smoke: success
  • Net PR diff: 28 intended release files; no scratch/operational artifacts remain.

Publication model
ENTITY core carries the one Global Passport protocol and canonical registry. Healthcare, Finance, Manufacturing, AI, Robotics and public/unclassified Defence are executable domain packages intended for dedicated repositories; they do not create separate passport protocols.

Claim boundary remains unchanged: BTG-controlled interoperability is meaningful controlled evidence, not unrelated third-party independence. Independent interoperability, external security/cryptographic review, deployment-specific legal/regulatory determinations, and real external market adoption remain external work.

@blackmore-technology-group
blackmore-technology-group merged commit 2db5bff into main Sep 24, 2026
5 checks passed
@blackmore-technology-group
blackmore-technology-group deleted the entity-v3.4.0-development branch September 24, 2026 23:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant