Privacy, intellectual property and Indigenous data governance
The system's engineering separates public discovery of an asset from private access to its source information. A catalogue may say that a qualified algorithm exists and is available for a specified use. That is not permission to publish the data used to develop it, identify a person mentioned in a source record or transfer a community's confidential knowledge. Sensitive data may have to remain in a controlled institution, with computations brought to it under strict conditions or the entire use refused.
Canadian privacy and public-sector information laws apply according to the organization and activity. In British Columbia, private organizations and public bodies may be governed by different statutes. Institutions should identify the correct legal basis, permitted purposes, affected individuals' rights, retention and security obligations before granting access. Labour agreements, intellectual-property contracts, research ethics and cross-border export restrictions may also matter.
Indigenous data sovereignty is not exhausted by a checkbox or individual consent screen. Indigenous governments and communities may have collective governance principles and legitimate authority over information about their peoples, territories and knowledge. Any system involving such information must be developed through appropriate relationships, defined authority and community-controlled limits. Sometimes the correct decision is that the information should not enter a marketplace.
Why legal rights cannot be generated by software
An algorithm can be tested and reproduced. A file's bytes can be signed and compared. A public catalogue can show an issuer's statement about an invention. None of those actions automatically gives the issuer the legal right to sell it. Legal title may depend on employment, assignment, confidentiality, copyright, patents, licences, privacy and the rights of contributing organizations.
Likewise, a database entry saying someone owns 1,000 investment units is not enough to establish that the units were lawfully issued shares. The governing corporate documents, statutory or authorized registers, investor eligibility, source of funds and applicable securities regime matter. A wallet should reflect legal reality rather than attempt to replace it.
This is not a weakness in the concept; it is the architectural reason ENTITY, ADAM, Verifiable Reality and the separate financial registries exist. The system is engineered to make such boundaries explicit so autonomous software cannot create legal or financial authority merely by calling a convenient API.
Why a commercial data marketplace and a securities exchange are different
A customer paying for permission to run a DataChip normally enters a commercial agreement for utility. An investor buying shares in a company accepts different risks and obtains different legal rights. Securities are subject to particular rules about issuance, disclosure, distribution, advice, dealing, resale, custody and marketplace activity.
In Canada, the B.C. Securities Commission administers relevant provincial securities law. Federal and national frameworks, including Canadian Securities Administrators instruments and the rules of CIRO where applicable, shape the requirements for dealers and markets. An alternative trading system and a recognized stock exchange are regulated institutional activities. A consultation letter or approved private primary securities offering does not itself authorize public secondary-market trading. [5] [6]
BTG's engineering dossier therefore separates a commercial marketplace for permitted data and software uses from any live investment-market function. The investment layer can be specified, simulated and independently examined while the required legal operating arrangements are pursued through the appropriate channels. That is a more credible foundation than assuming that describing a share as a 'bit' avoids securities law.
Security and responsible autonomy
An agent that writes and runs software must be treated differently from a simple reporting tool. Generated code can contain errors, consume excessive resources or attempt access outside its assigned project. Research execution therefore belongs inside a bounded environment with recorded limits. The relevant operating system or virtualization layer, not an AI's own promise, must enforce critical restrictions.
Across the broader ecosystem, identity verification, short-lived permissions, access limits, encrypted communications, recorded approvals, versioned software, signed evidence and independent security testing protect users and organizations. Cash and securities records require exact financial reconciliation. A failure should lead to a defined halt, quarantine or correction instead of an invisible override.
No technical design can guarantee the absence of all security incidents. The appropriate claim is that the architecture specifies controlled permissions, separation of authority, observable results and independently reproducible evidence. Those controls must be tested in the environments in which the system is actually used.
The October 2026 research evidence
BTG's technical record includes actual local research, code execution, knowledge reconstruction, Circuit execution and encrypted research-reference delivery. Those records are more substantive than a proposal consisting only of diagrams and written specifications. They also concern specific, bounded experiments, not yet a verified global commercial economy.
One research challenge required an algorithm to decide whether at least three of four encoded sensors reported the same valid reading. There were 65,536 possible input combinations. NIKI's first recorded generated C expression gave incorrect answers for 57 combinations, including cases in which a missing sensor was mistakenly counted as an agreeing measurement. The failure was preserved and the repair process produced a corrected source version with its own recorded provenance.
The corrected source was compiled to a 240-byte WebAssembly module. The recorded Windows Wasmtime execution returned correct results for all 65,536 inputs. A later Debian WSL2 execution using Bubblewrap and cgroup controls also returned 65,536 correct results. The recorded compiled binary hashes matched. The Linux environment ran on the same BTG workstation, so this is a real second operating-environment test, not a claim of reproduction by an independently controlled external institution.
The associated BTDU and ADAM records preserved the original research material and allowed local cold reconstruction. The Recursive Fabric runtime initially executed an evidence-processing Circuit Genome connected with the research chain. Later engineering advanced the demonstration: a recorded local receipt shows the actual repaired NIKI sensor algorithm operating as a typed executable node in a two-node Circuit, followed by an evidence-digest operation. The complete result matched the frozen oracle across all 65,536 inputs. Subsequent internal engineering records describe an immutable DataChip descriptor retained and reconstructed through BTDU, along with targeted and negative-test results. These findings form part of the documented internal engineering record and are distinct from external independent certification.
The record also includes three encrypted research-reference deliveries to three local Windows worker processes with durable acknowledgments and duplicate handling. Those workers were not three separately controlled physical research institutions, and the deliveries did not create legal commercial rights. An earlier downstream suite recorded 312 local regression tests passing after a process-launch correction; a later engineering report records 356 Windows backend regression tests passing as the integration progressed. These are software tests within their stated scopes, not counts of inventions or market transactions.
The relevant historical artifacts are held in the BTG qualification workspaces, including source and binary hashes, execution receipts and research delivery files. These provide a basis for future external reproduction. These development records do not establish independent institutional certification, owner-authorized production DataChip issuance, three separately enrolled physical hosts, a completed customer sale or authorized securities trading. Each is a distinct matter requiring its appropriate evidence and authority.
Why this real engineering example matters to a public reader
It demonstrates the kind of continuity the architecture is meant to preserve. A candidate can be generated, found wrong, repaired, executed as working software, reconstructed from retained knowledge, connected into a larger working Circuit and transferred as a research reference - while each stage has its own record. The more important later economic and institutional claims become credible only when independent organizations and paying customers complete their corresponding stages.
