ENTITY Documentation Portal
For architects, market/data infrastructure teams, security leaders and operators

Evaluate ENTITY for your organization

Start with the operating problem, not the “sovereignty” label. ENTITY combines persistent identity, delegated authority, explicit rights, governed information, evidence, digital market execution, economic participation, settlement verification and provider-independent recovery. This page helps determine which of those capabilities matter to your organization and what evidence would be required to trust them.

No procurement or endorsement claim: evaluation can be performed entirely from public source, documentation, releases and evidence. A negative conclusion is a valid outcome.

When ENTITY may be relevant

Rights or data marketsYou need explicit rights instruments, listings, balances, orders/RFQs/auctions, clearing, entitlements, usage and settlement evidence without pretending data bytes themselves are scarce.
Contribution or service economyYou need durable lineage between contributors, exact work, review/acceptance, licences, service obligations and later valid economic consequences.
Authority that must survive providersYou need identities and delegated authority to remain verifiable without a cloud account, venue or application becoming the permanent authority root.
Provenance that affects decisionsYou need to know where information, software, evidence or outputs came from, who controlled them and what changed before relying on them.
AI or agent economic actionYou need AI agents to access, purchase, license, execute or publish only inside explicit delegated authority and rights.
Portable market/economic recoveryYou need balances, entitlements, orders/trades, revenue rules, treasury participation and settlement evidence to survive provider/infrastructure failure.
Privacy/retention governanceYou need purpose-bound access, use caps, expiry, revocation, retention and evidenced destruction around governed information.
Independent verificationYou prefer public schemas, reproducible evidence and testable failure modes over vendor assertions.

A bounded evaluation path

  1. Choose one real object/workflow. A dataset, software contribution, model, service, organizational authority relationship or rights-market transaction.
  2. Define authority and rights. Identify who controls the object, who may act, what rights are valid and which constraints matter.
  3. Select the economic stages in scope. Instrument issuance, listing, price discovery, trade, clearing, entitlement, usage, participation or settlement.
  4. Define external evidence boundaries. Decide what requires an outside credential, upstream acceptance, payment confirmation, legal fact or independent attestation.
  5. Exercise a negative/recovery case. Test revocation, invalid rights, duplicate/replay, provider failure, partition conflict or unverified settlement.
  6. Record the result exactly. Success, failure and inconclusive outcomes should remain distinguishable.

Questions an evaluator should ask

Authority

Who can authorize what, under which scope, and can infrastructure custody ever accidentally widen that authority?

Rights

Are access, training, derivation, execution, redistribution, commercialization and transfer explicit rather than inferred?

Market execution

Are instruments, balances, listings, signed intents, RFQs, trades and cancellations deterministic and replay-resistant?

Settlement

Does the system distinguish execution, obligation, authorized payment evidence, settled value and realized cash?

Recovery

Can the complete authority/economic state move or recover without redefining rights, balances, entitlements or controller authority?

Evidence

Which conclusions come from BTG-controlled tests, independent reproduction, external acceptance, authorized attestations or independently controlled review?

Current real-world baseline

Vector #26501 / PR #26504 and Memnox #46 / PR #86 are both upstream-merged and recorded by ENTITY as UPSTREAM_ACCEPTED_RECORDED. Both remain pro bono with USD 0 realized cash. They provide real external contribution/economic-lineage cases without falsely implying payment.

Continue

Evaluation boundary: platform capability is not the same as institutional adoption; upstream acceptance is not payment; and modeled value is not automatically legal or accounting value.