Direct answers, from the build side of the category

• How do you integrate an agent mesh network into an enterprise stack?

  The mesh is coordination infrastructure. The integration work is deciding what it is allowed to touch.

• Agent mesh network or a single agent deployment — which does an enterprise actually need?

  Most enterprises that ask about mesh infrastructure need one well-governed agent first.

• What does integrating an agent mesh network actually cost?

  The mesh licence is rarely the expensive line. Your own authority model is.

• What should you ask before adopting an agent mesh vendor?

  The questions a technical evaluation should ask before the first pilot, not after the first incident.

• How do you decide between a shared ledger and a database?

  The question that should end most blockchain evaluations in the first meeting.

• Should you build a blockchain platform or license one?

  The honest version of this comparison names the case for building nothing at all.

• What does a production blockchain deployment cost to run, after launch?

  The number the launch budget rarely includes, and the reason year-two surprises happen.

• What does white-labelling a crypto wallet actually include?

  The distinction a technical evaluation should surface in the first call, not the third.

• How do you white-label a rewards or loyalty programme without inheriting someone else’s liability?

  The mechanics are the easy part. The balance-sheet question is the one that gets skipped.

• What has changed in how a token distribution programme is built, compliance-first?

  The same mechanics the category used in 2018. A different starting question.

• What does a tokenization or custody engagement cost for a financial institution?

  The scoping question a regulated institution should ask before the RFP, not during it.

• What should a capital markets desk ask before adopting blockchain settlement infrastructure?

  The interesting engineering in this sector sits behind the price, not in front of it.

• What does building a durable in-game or in-title asset economy cost?

  A durable asset system needs a sink as carefully designed as its faucet. Neither is primarily an engineering problem.

• How do you evaluate whether a supply chain blockchain programme is worth building?

  The commercial negotiation decides the outcome here more than the engineering does.

• What does building a certificate, allowance or provenance registry cost?

  The question is almost never issuance. It is double-counting.

• What can a healthcare organisation put on a shared ledger, and what can it never put there?

  The governing constraint rules out most of the category before the design starts.

• What does building a tokenized real estate or fractional-ownership register cost?

  Fractional ownership is an off-chain legal structure with an on-chain register attached. The failure mode is disagreement between the two.

• How do you evaluate a rights and settlement ledger vendor for telecom or media?

  Rights and settlement here is a many-party reconciliation problem, run today by spreadsheet and dispute.

• How does a retail brand evaluate a loyalty or points ledger vendor?

  These programmes are judged by finance long before they are judged by engineering.

• What does launching a fan token or membership system cost, and what capacity does fixture day require?

  The system’s peak load is known to the minute. Everything else follows from that.

• Should you white-label an existing platform or build your own consumer-facing product in-house?

  The question underneath this comparison is rarely engineering capability. It is what you are actually trying to own.

• Managed services or an in-house team for node operations — how do you decide?

  The comparison is rarely about capability on day one. It is about who is on call in year two.

• Permissioned ledger or public chain — how do you choose, once you know you need a shared ledger?

  The wrong version of this comparison is ideological. The right version is an operating-cost and settlement-obligation question.

• What changes in a build for a VARA-regulated entity in Dubai?

  Dubai’s virtual-asset regime is entity-licensed. The vendor’s job is building systems the licence-holder can defend.

• What does MiCA change for a token issuer’s technical vendor?

  The EU regime turns an issuer’s technical architecture into the proof behind its public statements.

• What does building for a MAS-supervised institution in Singapore look like?

  The regime’s technology-risk expectations are the closest any regulator comes to a code review.

• What changes in a build for a GIFT City IFSCA mandate?

  A financial centre with its own perimeter, inside a market this practice has worked with since 2017.

• What does Swiss practice expect from tokenization engineering?

  Where the ledger entry is legally the instrument, register engineering is the whole game.

• ADGM or DIFC mandate — what does the choice change for the build?

  Two centres, two rulebooks. The build should know which one it answers to before the first diagram.

• What changes when a government agency adopts an agent mesh network?

  The mesh does not change what a public body owes its citizens. It changes what has to be built to keep owing it.

• How does a government agency procure a blockchain or agent system defensibly?

  The procurement structure is itself part of the system design, not paperwork around it.

• How should a public body evaluate a technology vendor’s security claims?

  Three artifacts separate a vendor who has been audited from one who is about to be.

• What belongs in a public-sector RFP for a blockchain or agent system?

  Specify the obligations the system must satisfy, not the technology you expect it to use.

• How do you run a public-sector proof of concept that actually produces a decision?

  A pilot that cannot fail cannot inform a decision. Design the stop condition first.

• Who is accountable when an automated system acts on a citizen’s record?

  The question a public accounts committee asks first, and the one architectures answer last.

• How do you procure open-source-based infrastructure in the public sector?

  The code is free. The obligations are the procurement.

• What does it take for a public body to issue credentials a third party can verify?

  Issuing is straightforward. Revocation is the engineering.

• What does it take to build a token register that survives an audit?

  The register is the product. The token is how it is transferred.

• Should a software company build blockchain infrastructure in-house, or license and embed it?

  The domain most software teams lack is not engineering capacity. It is custody, finality and the operational discipline around them.

• How do you build a credit and debit path that survives retries?

  The failure that turns a delivery bug into a financial one.

• How do you index on-chain events without missing or double-counting them?

  The indexer’s hard problem is not throughput. It is that history can change under you.

• How do you test a smart contract system before it holds real value?

  The audit is the last step, not the test plan.

• What does key rotation actually involve in a running system?

  If rotation has never been rehearsed, assume the system cannot do it.

• How do you integrate a ledger with an ERP or core banking system?

  Two systems, two consistency models, one set of numbers that has to agree.

• What does running a node in production actually involve?

  Running the process is easy. Running it in two years is the commitment.

Market structure, valuation and the agent-economy vocabulary are defined at gda.group/answers. Where one of these pages depends on a term GDA owns, it links up rather than redefining it — the same term contract published on the glossary.