1 · BTG-controlled qualification
Tests executed against code/campaigns controlled by BTG. Engineering evidence—not unrelated validation.
ENTITY keeps BTG-controlled qualification, outside reproduction, real-world economic lineage, independently authored implementation, independent security review and institutional use as separate evidence classes. The platform implements a full market/economic fabric; each public case advances only when evidence supports that state.
Tests executed against code/campaigns controlled by BTG. Engineering evidence—not unrelated validation.
An unrelated person independently runs a published BTG baseline and reports environment, results and hashes.
An unrelated upstream project reviews/tests/accepts BTG work, providing externally controlled evidence of technical adoption.
An unrelated implementer builds from public protocol/conformance material using a repository and architecture they control.
Outside reviewers control methodology and report boundaries, incompatibilities or findings.
Organizations exercise the system against real operational, market or integration requirements with independently controlled evidence.
The public ledger now records two external software contributions through exact lineage, review/CI, upstream merge and ENTITY acceptance state. Both are PRO_BONO, with realized cash of USD 0 and payment_settled=false.
Upstream merged on September 28, 2026. ENTITY records UPSTREAM_ACCEPTED_RECORDED, exact accepted commit lineage and reconstructable evidence.
Maintainer-reviewed, follow-up applied, CI/security green and upstream merged on September 29, 2026. ENTITY records UPSTREAM_ACCEPTED_RECORDED.
| Evidence | Status | Boundary |
|---|---|---|
| Issue #28 focused remediation | 76/76 PASS | BTG-controlled source qualification |
| Full repository source suite | 279/279 PASS | BTG-controlled source qualification |
| Compiled Rust qualification | PASS inherited unchanged scope | v3.4.2 exact qualification scope |
| Real-world BTDU training qualification | PASS inherited unchanged scope | v3.4.2 exact qualification scope |
| 30-day wall-clock qualification | time-dependent | not reset by v3.4.3 |
An unrelated GitHub contributor reproduced the Java v3.4.2 26-vector campaign with matching sealed-kit/canonical-result hashes. That is meaningful external reproducibility evidence, while remaining distinct from an independently authored ENTITY implementation.
Read the external report →Build ENTITY semantics from public material without BTG implementation code.
Independent challenge →Exercise venues, instruments, execution, recovery, settlement verification and participation against independent systems/workloads.
Market model →Outside assessors or institutions define methodology and control evidence.
Qualification paths →