How the five products fit together
BTG Studio is intended to assemble complete, testable software or physical-system designs from reusable DataChips and Circuits. FarmNode Host runs permitted research and computational workloads. ENTITY is the identity, provenance, signed authority and rights foundation. Bridge enables permissioned connections to data and external systems. Bit Trade Global is the separate market infrastructure for describing qualified assets, issuers, economic rights and possible instruments.
The intended user experience is one authoritative BTG identity, with independently scoped access to each product. A common screen or the same email address alone does not establish a real shared account, ownership, or commercial entitlement. Local prototypes currently include separate account implementations, so unified hosted sign-on is not yet proven.
ADAM governs state changes; BTDU preserves authoritative reusable data and reconstruction evidence; NIKI proposes research; the Council is intended to challenge those proposals; DataChips, Circuits and Genomes carry qualified reusable functionality. These are supporting layers rather than substitutes for the five user-facing core systems.
1. Bit Trade Global — the exchange
Designed for distinct market information pages: issuer, ticker, underlying asset, use rights, transferable rights, proposed investment rights, disclosures, risks, orders, holdings and ledger proofs. The three rights families do not confer the same ownership. An investment instrument is not simply a copy of a dataset or a payment for computing time.
Engineering evidence: the original Exchange backend full-regression log reports 239/239 tests passed in the latest full retest (the earlier original backend regression also passed 221/221); current issuer HTTP tests separately reported 14 passed. The Windows cross-app qualification preserves original issuer, ticker, order and ledger structures. Those local tests do not establish functioning public account registration, completed live financial trades, settlements, payouts, physical-device iOS qualification or authorization for real market operation.
2. Bridge — consent and controlled access
Bridge is the gateway that lets a person or organization authorize particular data sources, uses and handoffs. Connecting a source does not automatically sell the information, surrender ownership, or create a listed security. Bridge grants must be checked by the service using them.
Engineering evidence: Bridge HTTP/ASGI integration reports 9 passed. Its latest broader 169-test regression still has one ImportError (the original farmnode_entity_process_peer is unavailable in that test environment). An earlier 161-test run had two import/environment errors, so the entire suite cannot be called passing. The original Bridge owner/device enrollment does not yet accept self-declared FarmNode accounts as authoritative.
3. ENTITY — identity, rights and provenance
ENTITY is intended to bind an authoritative account, device-specific public keys, ownership proofs, signed grants, revocations, provenance and execution rights. A verified signer may grant a specific research action without granting the right to list an instrument or execute a financial transaction.
Engineering evidence: the new Windows FarmNode implementation protects local account device credentials with Windows user-profile DPAPI, scrypt and an encrypted key envelope. Five focused device tests passed; a broader related local regression passed 97/97. The local device identity can survive migration without changing the device identifier. However the original ENTITY owner has not been production-bound to the same hosted account used by Studio, Bridge, Exchange and FarmNode. Mobile device identity and unified sign-on are not qualified.
Separately published ENTITY documentation → · Corporate ENTITY page →
4. FarmNode Host — permissioned computing
FarmNode Host provides a Windows user interface for local identity, opt-in computing, connection status and activity receipts. Users should be able to choose what resources they share, who may use them and under which verified rights. Device enrollment and receipts do not equal physically enforced CPU/RAM/GPU limits or a remotely attested network.
Engineering evidence: a native Windows executable and desktop shortcut were verified; Aurora GUI regression reported 92/92, and the later DPAPI-inclusive regression reported 97/97. These are overlapping test suites, not 189 independent acceptance cases. Original FarmNode three-app local signed-message tests passed. The qualification JSON explicitly records zero independently enrolled physical FarmNode hosts, no remote mutual-TLS worker qualification, no fully enforced compute quotas and no native signed/notarized macOS or runtime-qualified Linux product.
5. BTG Studio — the universal constructor
Studio is designed to let an owner describe a complete desired system, let NIKI propose tools and missing capabilities, connect typed, interlocking DataChip/Circuit pieces, test compatibility, run qualified components through FarmNode, and preserve successful verified creations for reuse. The goal is functional construction, not merely illustrated mockups or prompt responses.
Engineering evidence: original Composer/Studio integration logged 6/6 tests, with additional native puzzle 9/9, constructor/compiler 21/21 and original FarmNode 22/22 source-level test reports. A Windows Studio executable has been built and installed. The subsequent instrumented Studio–Bridge–Exchange–FarmNode suite passed 8/8 on 24 October in a fresh rerun after its earlier exception assertion and SQLite cleanup errors were repaired. Complete system construction, auto-wiring, production identity and paid instrument entitlement redemption remain unqualified. A demonstration of connected puzzle pieces is not a verified full autonomous invention.
NIKI Council — planned eight creators plus nine independent reviewers
The owner's target design has a Council of multiple models, not a single local model deciding everything. The intended eight creators propose alternatives, while nine independent reviewers challenge solutions and evidence. A Council result needs authenticated model responses, distinctness, quorum, bounded testing and attributable receipts; intended membership is not an operational Council.
Latest Grand Forks scenario: the durable Council's initial state was AWAITING_REAL_MODELS; its final reconciliation shows creator target 8, reviewer target 9, one actual creator response, zero independent reviewer models, quorum false. The creator selected and fetched eleven real government BC cutblock features; the model-directed puzzle assembly was rejected by the original compiler for an unconnected dataset input. An earlier live attempt timed out. No accepted complete Genome or production qualification was achieved. Eleven public BC cutblock features previously retrieved form a data-research foundation, not verified ecological, drone or autonomous-flight capability.
When a Bit Trade Global instrument controls computing
An eligible instrument may define a permitted computing or intellectual-property right. In the target workflow the account must own or otherwise hold the relevant right; Bridge or the instrument service verifies an entitlement; ENTITY confirms subject, device, scope and applicable grant; Studio supplies a compatible Circuit version; FarmNode checks job eligibility, quota and replay/duplicate protection; an attributable execution receipt is returned. Trading a security, buying a licence and obtaining the right to run a computation are separately documented actions.
A local research integration has introduced version, account, device, scope, compute and duplicate-job checks. The repaired local eight-test rights-integration suite passes 8/8, but this does not establish actual purchases or cross-product production entitlements. No live payment, entitlement redemption, cross-device owner-signature, real payout or commercial allocation is demonstrated by the published local record. Purchasing any proposed instrument must not be represented as automatically switching on every BTG product.
Reconciled test evidence and unresolved gates
| Area | Evidence from 24 Oct local logs | What the evidence does not prove |
|---|---|---|
| FarmNode Windows | 92/92 Aurora; 97/97 with DPAPI; executable/shortcut installed | Independent hardware federation, enforced quotas, production owner authority |
| Exchange backend | 239/239 full regression; earlier 221/221; 14/14 issuer HTTP | Live accounts, securities settlement, iOS release and commercial readiness |
| Bridge | 9/9 HTTP/ASGI; latest full 169-test run with 1 import error | Full environment readiness, unified cross-app sign-on |
| Studio | 6/6 integration; 9/9 puzzle; 21/21 compiler; 22/22 host | Latest 8/8 instrumented rights suite passes; complete qualified invention and actual purchases remain unproven |
| NIKI/Council | 12/12 durable-controller tests | 1/8 creators, 0/9 reviewers and no quorum; model assembly compiler-rejected |
The counts describe different scoped test suites, sometimes overlapping. They must not be summed into one system-wide pass total. Evidence sources are dated local CMD, PowerShell and Desktop Commander test outputs on the authorized BTG workstation; no private keys, credentials, internal paths or proprietary source files are published here.
Public status: local component progress is real, but end-to-end five-product production qualification is incomplete. Update after reproducible retests and actual model, account, entitlement and physical-host evidence, not on the basis of architectural intent.
Additional 24 October engineering verification
A full Exchange backend retest passed 239/239, including an 18-case signed research instrument-to-circuit check. A separately rerun Studio rights-integration suite passed 8/8. Bridge was retested against 169 cases but remains blocked by one missing original encrypted-ENTITY-process peer import.
Distinct local bounded checks passed for original FarmNode cutblock geometry (9/9), independent WGS84 cross-checks (10/10), model-authored numerical Circuit safety (16/16), and NIKI model-authored pipeline security (8/8). These are scoped tests, not counts of physically independent validators or verified ecological science.
The real NIKI creator fetched government cutblock features and proposed an interlocking recipe, but its first compiler attempt was rejected and its attempted automated feedback initially repeated the same invalid wiring. A qualified complete forestry/ecology/drone system and the multi-model Council quorum remain absent.
Where each audience should begin
Everyone: simple explanation → · Investors: what a right does and does not provide → · Regulators: accountable controls and test boundaries → · Engineers: validation scope, limitations and evidence →.