BTG Engineering — Open Protocols, Evidence and Independent Reproduction
BTG Engineering is the public engineering gateway for Blackmore Technology Group Limited: open-source releases, architecture decisions, reproducible evidence, interoperability work, security review and contributor participation.
Important technical claims should be inspectable, reproducible and bounded to the evidence that actually supports them. The engineering program is designed so an unrelated developer can evaluate ENTITY without needing private BTG infrastructure.
ENTITY v3.3.0
The current protected public release is ENTITY v3.3.0 — Verifiable Reality, Evidence and Economic Causality. Its protected release commit is 9c79f987207592cb6791e1a8956f23351cdfb2d3.
Complete regression: 144/144 PASS
Targeted v3.3 suite: 16/16 PASS
Sealed v3.3 reality vectors: 20/20 PASS — 10 valid / 10 invalid
BTG-controlled native reproducibility baselines: Rust, TypeScript, C#, Go, Swift and Java
A cryptographically valid statement is not automatically a protocol-valid statement, and a protocol-valid statement is not automatically a true statement about the external world.
BTG-controlled qualification is engineering evidence. It is not presented as unrelated third-party validation. Independent implementation, live interoperability and independent external security review remain separate public milestones.
Developer and research portal
ENTITY Developer Portal — start with reproduction, architecture review, contribution, independent implementation, interoperability or security research.
Engineering Evidence — exact public qualification evidence and claim boundaries.
Open-Source Governance and Release Policy — stewardship, decision classes, evidence-gated releases and historical-integrity rules.
Architecture & ADRs and Technical Papers — durable architecture decisions and public engineering notes.
Interoperability Status — the live distinction between BTG-controlled reproducibility and external milestones still pending.
Independent Security Review Program — a public scope and evidence framework for external security researchers and review organizations.
Independent work wanted
The next credibility milestone is not another BTG-controlled implementation. It is useful work from people and organizations outside BTG control. A contributor does not need to implement the entire protocol.
Reproduce the v3.3 sealed reality kit on Linux or macOS.
Find a specification ambiguity, unsafe escalation or counterexample.
Benchmark the public verifier and publish the environment and result.
Build a narrow clean-room classifier for the 20 public v3.3 vectors.
Review evidence, attestation, recovery or provider-independence boundaries.
Perform a scoped independent security review against an exact protected release commit.
A reproducible failure is useful evidence. A partial result should be published as partial rather than upgraded into a stronger claim.
Engineering doctrine
Registration is not ownership.
Provenance is not external truth.
A valid signature is not objective external truth.
Hosting, custody and infrastructure possession do not become sovereign authority.
External evidence sources do not silently become general protocol authority.
Historical signed state is superseded explicitly rather than silently rewritten.
Internal qualification is not the same as independent external validation.
Blackmore Technology Group Limited stewards the official ENTITY repositories and release process. The protocol is intentionally designed so stewardship does not require a conforming implementation to depend on BTG hosting, BTG DNS, a BTG resolver, a mandatory BTG cloud service or paid permission to use the published protocol.
Comments