Why does BTG need ADAM as well as ENTITY?
ENTITY describes the principal, asset and relevant rights. ADAM is the controlled decision process that decides whether a particular requested state change is authorized at that moment and records the result. Knowing that a person has permission is different from permitting a specific action on a specific version under current rules.
ENTITY describes a right; ADAM authorizes an action now.
A participant may have a valid general entitlement but still lack permission for a particular execution, export, payment or transfer at the present time. ADAM checks the requested action against current identity, rights version, scope, time, approval and policy. It records the result and prevents stale commands or duplicate network messages from being mistaken for new lawful grants or payments. This is important when an AI agent proposes actions affecting real resources.
A gate cannot replace its underlying authority.
ADAM does not act as a court, bank, issuer registry or securities regulator. It enforces supported rules within an authorized domain; it must reject or hold work where the authoritative contract, owner signature, operator permission or independent settlement proof is absent. A successful technical event receipt establishes that a system transition occurred, not that a financial liability was discharged.
The answer above preserves the original whitepaper text; this additional explanation is interpretive guidance, not a new claim of certification, legal authority or commercial launch.