BTG-controlled development line for future ENTITY market, integration and protocol experiments.
Looking for the current supported release? Start with ENTITY v3.4.3 in the main ENTITY repository.
ENTITY-2 is a public development repository maintained by Blackmore Technology Group Limited (BTG). It contains post-release engineering work and experiments around sovereign data commodities, rights-aware exchange, market evidence, integrations and related protocol research.
This repository is not the current supported ENTITY release, not the authoritative external conformance target, and not an independent third-party implementation.
ENTITY-2 is a development/experimental engineering repository. It can explore future protocol or runtime ideas, but material here does not become normative merely because it is public or executable.
Keep these layers separate:
- ENTITY Protocol 1.0 — frozen public interoperability/conformance target;
- ENTITY v3.4.3 — current supported runtime release;
- BTDU 3.4.2 — current unchanged Blackmore Technology Data Universe component inside the v3.4.3 runtime;
- ENTITY-2 — future/development work that may be incomplete, superseded or never promoted.
| You want to… | Use |
|---|---|
| Evaluate or build against the current supported runtime | ENTITY v3.4.3 |
| Start as a developer | ENTITY Developer Portal |
| Try a Healthcare, Finance, Manufacturing, AI, Robotics or Defence package | ENTITY v3.4 domain packages |
| Review current and historical engineering evidence | ENTITY engineering evidence |
| Implement frozen Protocol 1.0 independently | ENTITY Protocol 1.0 Conformance Kit |
| Explore future/experimental engineering | This repository (ENTITY-2) |
Current supported runtime facts:
- release: ENTITY v3.4.3;
- release merge commit:
528b70aabd05b1e930b77e4933f157731e47274f; - v3.4.3 Issue #28 remediation module: 76/76 PASS;
- full repository source suite: 279/279 PASS;
- immutable predecessor: ENTITY v3.4.2 commit
6dfa3d6cc738d9369cf092d2782676bf4f2a46e4; - BTDU component: 3.4.2 unchanged;
- independent unrelated implementation: OPEN / PENDING.
The authoritative Protocol 1.0 conformance kit remains a separate frozen target. Historical v3.4.0/v3.4.1/v3.4.2 release evidence remains historical evidence and is not rewritten when the supported runtime advances.
Current development themes may include:
- sovereign data-commodity objects and rights-bearing instruments;
- listing, disclosure, order/RFQ/auction and price-discovery mechanics;
- clearing, settlement and entitlement state;
- usage evidence, derived outputs and economic consequences;
- rights-aware exchange and market recovery;
- ADAM/NIKI integration boundaries;
- provider-independent evidence and authority semantics;
- failure, rollback, recovery and portability testing.
The intended market lifecycle is:
Digital Commodity Object (DCO) → Instrument → Listing → Disclosure → Order/RFQ/Auction → Price Discovery → Trade → Clearing → Settlement → Entitlement → Usage → Derived Output → Economic Consequence
Data economics in ENTITY concerns governed rights and authority around data, not artificial scarcity of byte copies.
Work in this repository can be incomplete, experimental, superseded or awaiting qualification. A branch, commit, pull request, passing local test or merged development change does not automatically become:
- a supported ENTITY release;
- a frozen protocol revision;
- external conformance evidence;
- independent interoperability evidence;
- an independent security review;
- a legal, regulatory, accounting or market determination.
Release claims belong with the evidence package and supported release in the main ENTITY repository.
BTG-controlled work—including clean-room work in other BTG repositories—is not described as unrelated third-party validation.
Registration, mirroring, ingestion, verification, provenance recording or custody do not themselves transfer upstream ownership or create automatic economic entitlement.
Development work must preserve the project’s authority boundaries:
- identity is not an account;
- registration is not ownership;
- provenance is not truth;
- protocol origin is not downstream asset origin;
- a valid signature is not objective external truth;
- possession, hosting and storage do not create sovereign authority;
- external evidence sources do not silently become protocol authority;
- generic application events cannot mutate protected authority, rights or economic state;
- historical signed state is superseded rather than silently rewritten;
- internal qualification is not independent external validation;
- ingestion or fork custody does not create automatic upstream ownership or economic rights.
main is protected. Changes should flow through pull requests and required checks. Development work should identify the exact branch/commit tested and should not describe an unqualified development branch as a release.
Python 3.11+ is recommended for the current reference/development runtime.
git clone https://github.com/blackmore-technology-group/ENTITY-2.git
cd ENTITY-2
python -m pip install -r requirements.txt
python -m compileall -q src sdk protocol
python -m unittest discover -s tests -vPassing this local smoke path is useful engineering evidence for the checked-out commit. It is not by itself a release or interoperability qualification.
Unrelated implementers should work from published sealed/specification material rather than using this development repository as their implementation source:
- ENTITY Protocol 1.0 Conformance Kit
- ENTITY external verification challenge
- ENTITY interoperability challenge
- Interoperability status
Independent external implementation and live interoperability remain evidence-gated milestones and should be recorded only when an unrelated party produces the required evidence.
Never commit private signing/recovery keys, credentials/tokens, principal/device/application binding instances, .entitybackup files, production databases/runtime state, or unredacted user/customer/business data.
Security-sensitive findings should use the private reporting process described by the main ENTITY project's SECURITY.md.
Public governance and release discipline live in the main ENTITY repository:
ENTITY development material in this repository is published under the Apache License 2.0 where the repository license applies. See LICENSE.
Blackmore Technology Group Limited
Repository: blackmore-technology-group/ENTITY-2
Role: BTG-controlled future/development engineering line