ENTITY v3.4.2 Language Distribution Readiness
Blackmore Technology Group maintains six controlled language baselines from the v3.4.2 Global Passport/conformance campaign. Each lane passed its recorded clean-room verification, dependency review and distribution/package smoke gate. Registry publication improves installability and discovery; it is not unrelated third-party validation.
Distribution matrix
Rust · crates.io
Package: entity-rust-cleanroom
Version: 3.4.2
State: package metadata qualified; trusted-publishing workflow prepared.
Remaining external gate: crates.io requires the first release of a new crate name to be published manually; trusted publishing can govern later releases.
TypeScript · npm
Package: entity-typescript-cleanroom
CLI: entity-verify
Version: 3.4.2
State: package contents qualified; trusted-publishing workflow prepared.
Remaining external gate: the package must first exist in npm before its trusted-publisher configuration can be completed.
C# / .NET · NuGet
Package: Blackmore.Entity.Passport.V34
Tool: entity-passport-v34
Version: 3.4.2
State: pack/install/execute smoke qualified; OIDC publishing workflow prepared.
Remaining external gate: configure the nuget.org trusted-publishing policy/account and repository variable required by the workflow.
Go · pkg.go.dev
Module: github.com/blackmore-technology-group/ENTITY-GO-CLEANROOM
Distribution tag: v3.4.2
State: canonical module identity and package smoke qualified.
Remaining external gate: create/verify the reviewed v3.4.2 tag and use normal Go proxy/pkg.go.dev discovery where applicable.
Swift · Swift Package Index
Products: EntitySwiftCleanroom, PassportV34
Distribution tag: v3.4.2
State: package description and release-build smoke qualified.
Remaining external gate: verify the reviewed v3.4.2 tag/package and submit the public Git URL to Swift Package Index where applicable.
Java · Maven Central
Coordinates: org.blackmoretechnologygroup.entity:entity-java-cleanroom:3.4.2
State: runnable shaded JAR qualified with the sealed v3.4.2 kit packaged and verified before classification.
Remaining external gate: Central Portal account, namespace verification and required artifact signing/publishing credentials.
What the package-smoke gates prove
The smoke gates are deliberately separate from protocol conformance. They test whether the distribution artifact itself can be packaged, resolved, built, installed or executed as expected for that ecosystem while the recorded clean-room campaign remains green. This prevents a package from being described as registry-ready merely because source tests pass.
What remains outside BTG control
Registry accounts, namespace ownership, first-publication rules, trusted-publisher policies and third-party package indexes impose external requirements. Those steps are recorded as gates rather than silently treated as complete. Until a registry or index actually exposes a package, describe it as qualified/publication-ready rather than published.
Relationship to v3.4.3
The v3.4.3 release carries forward compiled Rust clean-room/conformance qualification from v3.4.2 as inherited unchanged-scope evidence. That does not change these package versions to 3.4.3 and does not imply every language lane was re-executed against v3.4.3.
Independent evidence remains a separate lane
The six language baselines help outsiders reproduce behavior and lower implementation friction. Stronger evidence remains an unrelated engineer, institution or research group controlling its own implementation, methodology and conclusions. See Clean-Room Implementation and Independent Qualification.