DRAM.GOLD // ABOUT · AUTHOR
WHY
ABOUT THE AUTHOR · BANKING → EXECUTABLE QUESTIONS

SLAVA SOLODKIY — WRITES BUILDS PROVOKES.

I came to AI from banking, compliance, digital identity and transactions. I founded Arival Bank. My work asks how institutions establish who may act, on whose behalf, with which evidence — and how to keep that meaning when software acts for them.

ProfessionPRODUCT × TECH × TRUST
BaseUK / GLOBAL
Artefacts 2026BOOKS + EXPERIMENTS
MethodAI-NATIVE, HUMAN-OWNED
NOT A CHIP DESIGNER OR AI RESEARCHER.
AN OPERATOR TURNING INSTITUTIONAL QUESTIONS INTO TESTABLE SYSTEMS.
⚠ THE AUTHOR IS EXPERIENCING VERTIGO
THE PROFESSIONBanking · compliance · identity

The difference between a system accepting an instruction and an institution being entitled to act on it.

THE PRACTICAL CONTINUATIONAuthorityClaw · First Place

NVIDIA Claw Agent Challenge: London, 2026. A fictional-business payments experiment; recognition of the demo, not endorsement of the book.

Project and evidence ↗
I wrote the question.
Then I built a test.— the October continuation
BANKING × IDENTITY × TRANSACTIONS ◆ WORKING QUESTIONS ◆ EXECUTABLE TESTS ◆ EVIDENCE BEFORE CLAIMS ◆
THE AUTHOR · WHAT HE PUBLISHES PREQUEL → MAIN → SEQUEL
[01]THREE ARTEFACTS, ONE NERVOUS SYSTEM

The books are
working questions.

Each volume hands the same anxiety to a different actor — fear to the self, power to the industry, ambition to a licensed fintech.

THE AUTHOR · HOW HE WORKS EVIDENCE, NOT ADJECTIVES
[02]THE PRACTICE BEHIND THE BOOKS

What he can actually operate.

Technical ability measured not by memorised syntax, but by framing the problem, specifying constraints, directing the build, inspecting the evidence and getting to a reproducible artefact.

3
physical AI compute nodes
NVIDIA + AMD; different jobs, one lab.
24/24/12
GB GPU VRAM by node
Heterogeneous local inference rather than one-box demos.
128
tests in a full-stack identity reference build
AI-assisted implementation; inspectable repo and test suite.
0
AI authority override in the decision-plane demo
The model can propose evidence. It cannot overrule controls.
01 / LOCAL INFERENCE

Deploy & compare local models

GGUF / llama.cpp / Ollama-style runtimes, quantisation choices, context, VRAM, latency and practical fit across NVIDIA and AMD hardware.

02 / AGENTS

Orchestrate cloud → local execution

Use cloud reasoning as the planning/review layer while Linux-hosted CLI agents, local models and services do the execution.

03 / EVALS

Turn “seems better” into a test

Baselines, matched prompts, controlled conditions, synthetic cases, regression checks, raw evidence and explicit failure criteria.

04 / FORMAL METHODS

Separate AI output from authority

Deterministic validation → First-Order Logic / Prolog → institutional policy / OPA, with AI kept outside the final authority path.

05 / MULTIMODAL

Run speech, image & research stacks

Local STT/TTS, image generation/editing, research pipelines and specialist model roles rather than forcing one LLM to do everything.

06 / PRODUCT SYSTEMS

Direct AI-assisted full-stack builds

APIs, data models, onboarding logic, web/mobile surfaces, test suites and public technical artefacts — without pretending every layer was hand-typed.

[03]THE WORK BEHIND THE BOOK

The expertise stayed.
The form changed.

A document, an executable test, a counterexample. The point is not the number of computers on the desk.

FRAME THE PROBLEM

Who may act?

Identity, role, delegation, scope, revocation and evidence — questions carried over from banking and regulated transactions.

BUILD THE SMALL TEST

Make the distinction executable.

In AuthorityClaw, the model reads an invoice. The deterministic authority gate decides whether the simulated payment may proceed.

CHALLENGE THE RESULT

A prize is not a stopping rule.

The published post-challenge formal checks found counterexamples, which were replayed, fixed and retained as regression tests.

THE AUTHOR · SELECTED BUILDS / 2026 OPEN, INSPECT, RERUN
[04]THINGS YOU CAN OPEN

Not a gallery — an evidence set.

Infrastructure, evaluation, identity systems, formal reasoning and AI-assisted product builds.

AI-01 / LOCAL INFRASTRUCTURERESEARCH SETUPS

Slava AI Lab

Local-model and multi-node experiments exploring role separation, heterogeneous hardware, and cloud-assisted planning with local execution. Individual setups are dated in the linked research.

PROOF SIGNAL / measured VRAM, latency, context behaviour, services, local outputs
ID-02 / FULL-STACK REFERENCE BUILDPUBLIC REPO

LarePass Reference System

AI-assisted self-sovereign identity reference system with web + mobile surfaces, PostgreSQL, OpenAPI 3.1, generated clients and a branching KYC/KYB onboarding engine.

PROOF SIGNAL / OpenAPI · branching onboarding · tests
FL-03 / FORMAL REASONINGEXPERIMENT SERIES

FOL × Qwen × Nemotron

Experiments around whether natural-language model outputs can be translated into explicit, inspectable logic and then constrained by deterministic or institutional policy layers.

PROOF SIGNAL / Prolog · OPA/Rego · evidence regeneration · reproducible demo
RG-04 / REGULATED SYSTEMSDESIGN + PROTOTYPE

Revolut / Governed Agent

A set of experiments asking a harder question than “can an agent act?”: under what evidence, mandate, scope and revocation state should an agent be allowed to act?

PROOF SIGNAL / authority schema · scope · provenance · revocation · deterministic gates
MM-05 / MULTIMODAL LOCAL AIWORKING TOOLS

Audio + Image Local Stacks

Local speech recognition and TTS in local experiments; ComfyUI image generation and editing in the local lab; specialist workloads kept separate from the main LLM path.

PROOF SIGNAL / local WAV · local transcription · generated & edited images · isolated runtimes
DI-06 / DOMAIN DEPTH2025—2026

Digital Identity Research

The domain behind much of the technical work: reusable identity, compliance-grade architecture, proof-of-personhood, government wallets, KYC/KYB and AI-era institutional trust.

PROOF SIGNAL / public research repository · releases · reports · DOI-linked work
THE AUTHOR · AI-NATIVE BUILD MODE FRAME → SHIP
[05]THE LOOP AROUND THE CODE

Doesn't compete with programmers at typing.

The useful skill is turning a hard problem into an executable experiment, using specialist AI as leverage, and refusing to accept a green screen without evidence.

01FrameWhat is the actual problem? What is not the problem?
02SpecifyConstraints, invariants, schemas, expected outcomes.
03DelegateChoose cloud agent, CLI, local model or specialist tool.
04BuildLet the machine do machine work; keep architecture inspectable.
05AttackCounterexamples, false premises, edge cases, matched comparisons.
06VerifyDeterministic checks, tests, formal logic, CI, raw evidence.
07ShipRepo, page, report, benchmark or reproducible artefact.

Not claiming

  • career software engineer
  • ML researcher who designs model architectures
  • CUDA / kernel / compiler specialist
  • that every line in his repos was typed by hand

Actually doing

  • AI-native technical product building
  • systems prototyping & orchestration
  • local inference and model evaluation
  • agent supervision and technical specification
  • formal decision experiments
  • AI-assisted full-stack prototyping
REVISION LEDGER / HOW EVIDENCE CHANGES THE SYSTEMINCIDENT → INVARIANT → TEST
R001 / CHANNEL
A real channel is evidence, not authority. Government-domain origin can start verification; it cannot release data.
R002 / HOLD
Irreversible disclosure stays null until authority resolves. A “small provisional payload” still leaks. HOLD means zero outbound PII.
R003 / CAPACITY
Identity is not enough; current capacity must also hold. The ontology changed when the evidence showed that role and authority can diverge.
THE AUTHOR · WORKING TOOLBOX NOT A KEYWORD CLOUD
[06]TOOLS THAT HAVE SHIPPED SOMETHING

The stack he can reason about and operate.

LayerToolbox used in the experimentsWhat it is for
Local LLM Qwen · Nemotron · Mistral · Gemma-class experiments · abliterated sandbox models Inference, extraction, synthesis, coding, adversarial comparisons.
Runtime llama.cpp · Ollama · LM Studio · FreeToken experiments Local serving, GPU offload, quantised inference, heterogeneous hardware tests.
Agents ChatGPT / Claude / Codex / Claude CLI · desktop/CLI hand-off patterns Plan → execute → inspect → revise loops across cloud and local environments.
Formal SWI-Prolog · First-Order Logic · OPA / Rego · Z3 model checks Make assumptions explicit; keep policy and AI output separable.
Research Local Deep Research · SearXNG-style search layer · local LLM synthesis Evidence-led research without treating the base model as a current-information oracle.
Media ComfyUI · FLUX-class image models · Whisper · local TTS Local image generation/editing and speech workflows.
Product build OpenAPI · React / Vite · React Native / Expo · PostgreSQL · Docker Compose AI-assisted reference systems and prototypes with inspectable interfaces and tests.
Evidence Git · GitHub Actions · hashes · manifests · raw outputs · regression suites Turn a demo into something another person can inspect and rerun.
THE AUTHOR · WHY THESE PROBLEMS INSTITUTIONS FIRST
[07]ENTERED TECH THROUGH INSTITUTIONS, NOT COMPUTER SCIENCE

Banking, fintech, compliance and digital identity taught him to care about who is allowed to do what, on whose evidence, under which rules.

Not a career change — the same profession.
Only the subject of trust changed: first the institution, now the model.

That is why the technical experiments keep converging on authority, evidence, provenance, identity, local control and regulated decision-making.

Not trying to become a better programmer than programmers — but very good at turning difficult institutional problems into systems that can be built, attacked, measured and inspected.

TRUST
OPEN TO HARD PROBLEMS PRODUCT × AI × REGULATION

Give him a messy system with real constraints.

Most useful where product, AI, regulation, identity, infrastructure and institutional reality collide — and where a slide deck is not enough. The preferred output is something you can run.