Public resources: where each claim, right and status is explained
A serious public reference library should help a technical evaluator, customer, contributor or institutional reviewer locate the exact relevant explanation and determine what kind of evidence exists. It should not require access to protected source repositories, publish sensitive data, or treat a conceptual instrument design as a live financial record.
PUBLICATIONS AND GUIDES
Begin with the complete economic and technical model
Building a Knowledge Capital Economy (October 2026) introduces the seven system-level transformations and the relationship among invention, durable knowledge, executable software, lawful rights, economic participation and future finance. Its 24-stage robotics example shows how those functions are meant to fit together, and where a research result must stop until the next kind of authority is established.
The source is available as a PDF and a navigable chapter library. When the original describes an internal demonstration, an internal demonstration remains distinct from independent certification or a product launch.
Find the correct document for a commercial right
Prospective buyers first need the asset or service version, scope of use, contractual restrictions, delivery model, operating limitations and what evidence supports the performance claim. The Rights Passport concept provides the consistent vocabulary. A candidate U, A or I instrument should never be reduced to a ticker-like label and a price without identifying the legal arrangement.
For DCO-000001 and DCO-000002, the identified subjects are a robotics failure-and-recovery dataset and a separate robotics algorithm. Their public reference material should distinguish these asset families and show unknown rights or issuer fields rather than supplying invented figures.
Use the evidence resources to understand claims
A test report documents the code and cases evaluated. A source hash helps identify exact bytes. A legal agreement establishes permitted activity if valid. An independent laboratory reports what it observed. A payment provider confirms an actual financial receipt. They may be linked through a common record structure but cannot be substituted for each other.
The published engineering foundation includes a bounded 65,536-case algorithm result. It does not document a fully completed global network of independently enrolled institutions or an authorized securities market. These missing claims should remain explicitly outstanding.
Read governance and adoption material before contributing data
Privacy and contractual rights travel with an asset. Indigenous governments and collectively governed sources may require entirely different consent structures from an individual account. Public-sector bodies have statutory, records and procurement duties. A Bridge connection is therefore only a controlled access path, not permission to publish or monetize all data that can be fetched.
The adoption framework should distinguish a research review, technical pilot, commercial licence and regulated financing. It should also explain what a visitor can expect from the site today and what remains dependent on outside authorization.
Proprietary code and public accountability can coexist
BTG can keep the Exchange implementation, specific algorithms, signing infrastructure and security-critical details private while publishing serious high-level documentation, verifiable methods, data-rights boundaries, public commitments and appropriately redacted proofs. A public document need not include private repository credentials or protected customer payloads to describe its function and acceptance standard.
Where an external source is cited, its date, methodology and meaning matter. Market-sizing figures, Canadian intangible-capital research and experimental U.S. data-asset estimates are distinct economic measures, not cumulative valuation of the BTG system. The public library should also retain correction and revision history when interpretations change.
What the records must establish
Facts that belong in the supporting evidence
| Core reference | Complete whitepaper and 62 numbered chapters |
|---|---|
| Technology | NIKI, FarmNodes, BTDU, Chips, Circuits, Genomes, SDK |
| Economic rights | Rights Passport, candidate DCOs, commercial versus investment |
| Trust | Sources, evidence classes, privacy and governance |
| Commercial status | Actual documented activity, not sample app records or estimates |