ENTITY: the identity, rights and economic relationship system
What ENTITY is
ENTITY gives a durable identity to people, organizations, software capabilities, datasets, inventions and related economic rights. It records the relationships that matter when knowledge moves between systems. A DataChip may travel from one cloud service to another while remaining the same underlying version. A researcher may grant a manufacturer permission to run it for a limited purpose. A contributor may be entitled to part of a particular commercial revenue stream. ENTITY is designed to preserve and verify these distinctions.
Imagine a land registry combined with a library catalogue and a permissions desk. The catalogue identifies an item. The permissions desk determines who is allowed to use it and in what way. The registry preserves claims and supporting documents. But the office does not become the law itself: if a legal title is disputed, contracts, legislation and relevant authorities must decide the outcome.
Provenance: knowing where something came from
Provenance means the origin and history of an item. In BTG, an asset record can point to its original research project, source data, code version, parent DataChips, test evidence and contributing organizations. Provenance answers, 'Where did this come from?' rather than merely, 'What is this file called?'
A cryptographic fingerprint can establish that two versions of a file contain the same bytes. A digital signature can establish which key signed a statement. Neither is automatic proof that the signer owns the copyright, has the right to sell the dataset or can issue shares. ENTITY therefore distinguishes a technical claim from documentary legal authority and recognizes conflicts, expiring permissions and revocations.
Rights Passports
A Rights Passport is a readable and machine-verifiable description of what permissions are associated with an asset. It might say that a buyer may execute a particular algorithm for one year, only inside its manufacturing systems, with no permission to download underlying private data, modify the original source or sublicense it. Another agreement might allow research use but forbid commercial use. An assignment of intellectual property, a commercial licence and a share in a company have different legal meanings; a generic 'owner' label cannot replace those meanings.
Before a protected action takes place, a participating service checks the relevant rights, identity, time period, purpose, version and restrictions. If an entitlement expires or is lawfully revoked, a new unauthorized action should be blocked. The historical audit remains available as law permits so parties can determine what happened when a contract was still active.
Contributor relationships and sovereignty
ENTITY also relates assets to their creators and contributing sources. The system can represent multiple parent assets, companies, researchers, data contributors and agreed allocations of commercial proceeds. It can identify that a derived invention depended on a particular licensed dataset without automatically asserting that every source contributor owns the derived invention. Contributions and economic entitlements are established under actual agreements.
Organizations and Indigenous Nations may have distinct data-governance requirements, and some information is not appropriate for commercialization at all. The system is designed to enforce purpose and jurisdiction boundaries rather than treating everything that can be copied as freely transferable.
Why ENTITY matters beyond a single BTG service
An important distinction is portability. If the asset, its right and its evidence are legible only inside one company's private database, participants depend entirely on that company. ENTITY's role within the wider architecture is to support interoperable verification so legitimate rights can remain meaningful as assets are reused by different applications, farms and commercial partners. Its design is not to impose an automatic fee on every unrelated party merely because an asset has an ENTITY record. Service fees and ownership income must come from the appropriate contracts.
ADAM: the controlled engine for decisions that change the system
ENTITY describes identities and claims. ADAM determines whether a requested action is permitted and commits an accountable change to the relevant system state. A state is simply the system's current agreed record: a licence is active, an asset version is qualified, a research budget is approved or a transaction request is on hold.
To understand the difference, imagine a business keeps a secure employee-access register. ENTITY identifies an employee and their job permissions. ADAM is the gate that checks a particular request and either permits a recorded change or refuses it. The fact that the employee once had permission does not mean that every later request is automatically allowed.
A NIKI agent might request that a completed experiment be retained. ADAM checks the appropriate authorization, the exact asset version, the owner's current rules and whether the record has changed since the request was prepared. If valid, the authorized domain makes the change and records its receipt. If stale, disputed or unauthorized, it rejects or holds the command. An attempted replay of a completed transaction must not create a second payment or second issuance merely because a network message was sent twice.
ADAM is central to autonomous systems participating in real business activity. Intelligence can recommend an action; a governed state engine decides whether that recommendation can produce a real side effect. That is safer than handing an AI agent unrestricted access to a company's databases, funds and legal records.
ADAM is not the registrar of securities, a bank, a judge or a substitute for the authorization of a human rights holder. It enforces rules backed by legitimate authority within its scope.
Universal Transaction Fabric: connecting the record of what happened
The Universal Transaction Fabric is the communication and event-recording layer connecting activities across the BTG systems. In everyday terms, think of it as the system of numbered receipts and dependable delivery between different departments. Each event can identify what happened, which asset or right it concerned, which authority acted, which rules were checked and how to retrieve the relevant evidence.
When NIKI produces an experiment result, the research service records it. When a DataChip version is qualified, the capability service records that event. When an owner grants a licence, the rights system records an authorization. When a customer actually pays, the financial service references the external payment evidence. A public transparency service may disclose a safe verification summary without publishing a private customer's identity or contract.
This fabric is designed to tolerate the ordinary failures of distributed computing. A message may be delayed, delivered twice or arrive after an outage. The architecture uses stable references, signatures, version checks and duplicate handling so repeated messages do not change legal balances twice. When one service fails after another has acted, the recovery process must reconcile the authoritative records rather than simply declaring all parts of the transaction successful.
The name 'transaction' has a broad meaning here: it may refer to a confirmed technical event, a licence permission or an actual financial transaction. A technical event receipt is not money. It is also not automatically a corporate share certificate or enforceable assignment of intellectual property. Each real-world authority remains separately identified.
Contributor participation: how people and organizations can share in legitimate value
The Knowledge Capital Economy is not just about paying technology companies for access to information. It also addresses people and organizations whose authorized contributions help create productive assets.
The word contributor can mean different things. A research institution may supply a lawful dataset. An engineer may contribute source code under an employment or licensing contract. A group of inventors may develop a method together. An individual may voluntarily permit a narrowly described use of personal information. A cooperative or Indigenous institution may manage a collectively governed source subject to its own legitimate authority. These cases cannot be treated as though everyone holds identical ownership rights.
From permission to a documented economic entitlement
A sound contribution arrangement begins with the precise right that can be granted. The agreement identifies the source, permitted purpose, duration, parties, privacy restrictions, ability to withdraw future permission where applicable and the economic return, if any. An entry in a database is not a substitute for consent or legal title.
The system can connect an agreed contribution to the assets that use it. If a manufacturer pays for a licensed application, and the agreement provides a portion of qualifying income to named participants, the payment can be traced to the specific receipt and allocation rule. The system must account for disclosed fees, taxes, refunds, other royalties and reserves before distributing the amount actually available under the contract. The combined claims against one receipt must not exceed the money the agreement makes distributable.
A straightforward example
Suppose a research collective and a machinery manufacturer jointly create a rights-cleared fault database. Their agreement provides that after specified expenses, the remaining eligible licensing proceeds are divided among the collective, the manufacturer and named contributors. A customer pays an invoice for a permitted use. The payment provider confirms settlement. The financial system calculates the shares using the actual receipt and agreed rules. Each participant receives a statement showing the basis for the allocation, pending payments and any withholding. If a refund later occurs, the adjustment is recorded rather than silently disappearing.
If a later Circuit uses the same dataset through three different component paths, that should not automatically triple the contributor royalty. The economic claim follows the legitimate contract and revenue allocation, not the number of times the asset's name appears in a software graph.
Privacy and fairness
Some data should not be commercialized, no matter how technically attractive it appears. Information about children, patients, precise personal movements, private communications or sensitive communities can carry heightened obligations. Public-sector records and Indigenous data may also be subject to governing rights beyond an individual's click-through consent. Participation should be understandable, voluntary where required, and supported by meaningful dispute procedures. A contribution record must not expose a person's private identity simply to prove that money was allocated.
This model does not give a person automatic royalties from every past use of data associated with them. Economic participation depends on enforceable arrangements and applicable law. The social opportunity is to provide clearer, auditable ways to negotiate participation in future authorized uses of valuable contributions.
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.
