Sitemap
Every page published on this site — 246 in total. The machine-readable versions are at /sitemap.xml and /llms.txt.
The firm 12
Our work 11
- Our Work — the engagement record
- Case studies — index
- Client results
- Settlement infrastructure for a gold-backed monetary system
- Books anyone can audit, rules anyone can fork
- One identity, three surfaces, no fork
- The mechanics that make a programme habitual
- A programme inside the messenger, not beside it
- A rewards ledger that reconciles, by construction
- Redemption without a liquidity promise the catalogue could not keep
- A learning platform where the certificate means something
Answers 46
- Answers — index
- How do you integrate an agent mesh network into an enterprise stack?
- What changes when a government agency adopts an agent mesh network?
- Agent mesh network or a single agent deployment — which does an enterprise actually need?
- What does integrating an agent mesh network actually cost?
- What should you ask before adopting an agent mesh vendor?
- How do you decide between a shared ledger and a database?
- What does it take to build a token register that survives an audit?
- Should you build a blockchain platform or license one?
- What does a production blockchain deployment cost to run, after launch?
- What does white-labelling a crypto wallet actually include?
- How do you white-label a rewards or loyalty programme without inheriting someone else’s liability?
- What has changed in how a token distribution programme is built, compliance-first?
- What does a tokenization or custody engagement cost for a financial institution?
- What should a capital markets desk ask before adopting blockchain settlement infrastructure?
- How does a government agency procure a blockchain or agent system defensibly?
- What does building a durable in-game or in-title asset economy cost?
- How do you evaluate whether a supply chain blockchain programme is worth building?
- What does building a certificate, allowance or provenance registry cost?
- What can a healthcare organisation put on a shared ledger, and what can it never put there?
- What does building a tokenized real estate or fractional-ownership register cost?
- How do you evaluate a rights and settlement ledger vendor for telecom or media?
- How does a retail brand evaluate a loyalty or points ledger vendor?
- What does launching a fan token or membership system cost, and what capacity does fixture day require?
- Should a software company build blockchain infrastructure in-house, or license and embed it?
- Should you white-label an existing platform or build your own consumer-facing product in-house?
- Managed services or an in-house team for node operations — how do you decide?
- Permissioned ledger or public chain — how do you choose, once you know you need a shared ledger?
- What changes in a build for a VARA-regulated entity in Dubai?
- What does MiCA change for a token issuer’s technical vendor?
- What does building for a MAS-supervised institution in Singapore look like?
- What changes in a build for a GIFT City IFSCA mandate?
- What does Swiss practice expect from tokenization engineering?
- ADGM or DIFC mandate — what does the choice change for the build?
- How should a public body evaluate a technology vendor’s security claims?
- What belongs in a public-sector RFP for a blockchain or agent system?
- How do you run a public-sector proof of concept that actually produces a decision?
- Who is accountable when an automated system acts on a citizen’s record?
- How do you procure open-source-based infrastructure in the public sector?
- What does it take for a public body to issue credentials a third party can verify?
- How do you build a credit and debit path that survives retries?
- How do you index on-chain events without missing or double-counting them?
- How do you test a smart contract system before it holds real value?
- What does key rotation actually involve in a running system?
- How do you integrate a ledger with an ERP or core banking system?
- What does running a node in production actually involve?
Platforms 20
- Platform catalogue
- White-label programme
- Licensing model
- Deployment & support
- Partner & reseller programme
- Developer documentation
- Identity & accounts
- Engagement & social systems
- Telegram & messaging apps
- Wallet — service, mobile & extension
- Swaps & redemption gateway
- Bridges & settlement
- Exchange & OTC infrastructure
- Custody & wallet
- Token issuance & tokenization
- Loyalty, points & rewards
- Distribution & community systems
- Agent coordination runtime
- AI operations & data tooling
- Learning & certification platform
Insights 9
Trust & procurement 10
Contact & utility 4
Capabilities 9
Industries 12
Capability × industry 6
Articles 8
- Threshold signing fails at the rate your staff resign
- Chain selection under a finality constraint
- Custody design for tokenized reserves
- Building a reconciliation job against an EVM chain
- Upgradeable contracts as a governance question
- Key ceremonies that can be repeated
- Evaluating a model before a pilot
- The practice, and this site
Glossary 91
- Agentic Autonomous Operating Stack
- Cross-organizational settlement and reputation layer
- Enterprise agent risk and clearing problem
- Agent execution protocol
- Agent execution infrastructure
- Reconciliation break
- Finality window
- Signing boundary
- Custody design
- Chain selection
- Decision boundary
- Automation boundary
- Audit trail
- Authoritative record
- Idempotency key
- Threshold policy
- Key ceremony
- Recovery rehearsal
- Upgrade capture
- Bytecode verification
- Allowlisting
- Transfer restriction
- Register of holders
- Node operations
- Agent coordination
- Break procedure
- Build-or-buy assessment
- Service-to-service trust boundary
- Anti-gaming control
- Readiness assessment
- Agent rollback
- Published status
- Settlement tolerance
- Expiry policy
- Enterprise integration boundary
- Authority model
- Policy-checked service
- Verifiable credential
- Escalation threshold
- Vendor exit plan
- Entity file
- Reserve-backed instrument
- Irreversible retirement
- Coalition programme
- Embedded delivery
- Knowledge transfer
- Proof obligation
- Counterparty commitment
- Schema agreement
- Accrual recognition
- Metering boundary
- Consent revocation
- Read-only degradation
- Regulatory permission boundary
- Peak-window capacity
- Proposer–committer split
- Decision evidence
- Policy version
- Bounded pilot
- Acceptance gate
- White-label licence
- Licensee support obligation
- Disclosed origin
- Related-party disclosure
- Naming permission
- Engagement record
- Stated direction
- Status vocabulary
- Canonical home
- Term contract
- Machine surface
- Ring manifest
- Security questionnaire
- Control environment
- Data residency
- Subprocessor register
- Coordinated disclosure
- Source escrow
- On-call rota
- Runbook
- Incident post-mortem
- Daily reconciliation close
- Settlement instruction
- Trade capture
- Record-date entitlement
- Documentary flow
- Exception workflow
- Bridge trust model
- Redemption gateway
- Eligibility versioning
- Fee market exposure