Index Expertise
Fields of work
Five fields, one method: read the constraint, model it as data, make it executable, keep it auditable.
- Depth
- Written from build experience
- Claims
- Verifiable or marked to confirm
01 Field
Financial infrastructure
The components a transactional system needs before a product can exist on top of it.
- Electronic money
- Payment systems
- Ledger architecture
- Wallets
- Reconciliation
- Transaction systems
Electronic money
Electronic money is a claim on an issuer, not a balance in a database. The system has to know what was received, what was safeguarded, what was issued, what is held by whom, and what has been redeemed, at every moment and after the fact.
Payment infrastructure
Accounts, wallets, transaction rules, limits, holds, reversals, reconciliation and settlement. The interesting part is not the happy path; it is what the system does when a movement is partially complete.
02 Field
Regulation
Regulation read as a specification, not as a document to file after launch.
- EME
- ACPR
- Compliance engineering
- Regulatory reporting
- Internal control
Compliance engineering
Controls, workflows, verifications, auditability and follow-up built as software, so that the evidence of a control is produced by the control itself rather than reconstructed later.
Regulatory reporting
One data structure, several projections. Reports become a query over the operating data rather than a manual assembly exercise.
03 Field
Artificial intelligence
AI put to work where the output has to be checkable by someone who did not write it.
- LLMs
- Agents
- AI workflows
- AI governance
- EU AI Act
- Automation
EU AI Act
Read as a system specification: scope, classification, documentation, human oversight, logging and traceability. The output is a design, not a policy document.
04 Field
Trust systems
Systems where the guarantee has to survive the operator, not depend on it.
- Cryptography
- Privacy
- Digital identity
- Electronic voting
- Verifiability
Cryptography and privacy
Membership proofs, unlinkability and verifiability studied as primitives for systems where the operator must not be trusted with the correlation between an identity and an action.
05 Field
Digital platforms
Acquisition and distribution treated as engineering problems with measurable throughput.
- Marketplaces
- SEO at scale
- Lead generation
- Conversion systems
- Automation
- Demand generation
Digital platforms at scale
National information architecture, quote generation, qualification and matching. Acquisition treated as a system with throughput, loss and latency.
Contact
Building something difficult?
Fintech, regulated infrastructure, AI, cryptography or complex digital platforms.