ALVIN REYES  /  AR DATA
TAKING ENGAGEMENTS  /  Q3 2026
↓ ALVIN REYES FOUNDER — AR DATA 20 YEARS / NO VC / NO BENCH

We don’t prototype
and disappear.
We ship.

Twenty years at Oracle, IBM, HP, Macquarie, Scotiabank, and Protocol Labs taught me what production looks like. I built AR Data to deliver the AI & blockchain systems most consultancies fake — bootstrapped, no investors, no prototype-and-disappear. The AR is me.

01 About

The AR
is me.

My arc started at Oracle and IBM, where I learned what enterprise delivery actually demands — not what the SOW says, but what it takes to ship a system that survives production. At HP/DXC I led large-scale infrastructure engagements across multiple continents.

At Macquarie Bank and Scotiabank I saw firsthand how financial institutions demand systems that cannot fail — and how few consultancies can actually deliver that. Then came Protocol Labs, where I contributed to IPFS and Filecoin infrastructure — the decentralized storage layer that powers Web3.

Most firms sell roadmaps and prototypes. Few can ship. The gap between a demo and a production system is where every engagement actually lives, and most consultancies never cross it. I started AR Data — one of the operating companies under ARCE Holdings Inc. — to close that gap. Bootstrapped. No investors. No bench warmers. Just engineers who have shipped, shipping again.

02 Holdings — The Group

AR Data is one of several operating companies under ARCE Holdings Inc. One principal. One standard. One bench that ships.

Engagements run through the company that owns the domain — agentic systems through AR Data, vertical intelligence through Caiden, computer vision through SelfVision — but the engineering standard is the same across all of them. Selective joint ventures sit alongside when the right shape is a co-owned vehicle rather than a service engagement.

PARENT · 100%
ARCE Holdings Inc.
Bootstrapped · Privately held · Founded by Alvin Reyes
SUB · 01 · OPERATING
AR Data Intelligence Solutions ardata.tech
Production AI & agentic systems. Where the consulting work lives. WATED & BMAD applied.
STATUS · Accepting engagements
SUB · 02 · OPERATING
Caiden Intelligence Solutions caiden.ai
Applied intelligence for vertical workflows. Domain models, embedded agents, and the analytics that make them measurable.
STATUS · Active
SUB · 03 · OPERATING
SelfVision Inc. selfvision.ai
Computer vision & identity. Models, pipelines, and the rollback story that keeps them shippable in regulated contexts.
STATUS · Active
SUB · 04 · OPERATING
Koneksi Inc. koneksi.* · [confirm domain]
[Placeholder — tell me Koneksi’s scope.] Likely connectivity, integration, or platform layer powering the other operating companies.
STATUS · Active
SUB · 05 · OPERATING
MetaDev Inc. metadev.* · [confirm domain]
[Placeholder — tell me MetaDev’s scope.] Likely a developer-tools or platform engineering venture supporting the group’s build pipeline.
STATUS · Active
JV · 06+ · PARTNER-LED
Joint Ventures by partner
Selective JVs with domain partners where the right shape is a co-owned vehicle rather than a service engagement.
STATUS · Selective

↳ One principal, one standard — engagements book into the operating company that owns the domain.

03 The Arc — Two Decades of Shipping

Twenty years across enterprise, finance, and decentralized infra. Every line on this list was a system that had to survive in production.

↳ Dates & locations approximate — tell me which to refine.

04 My Approach — The Loop

My approach has three frames. The loop below is the meta-shape every engagement runs through. WATED is the five-pillar design framework. BMAD is the build crew that ships the system.

A repeatable shape I bring to every engagement — plan, ground, execute, verify, ship. The boxes change. The loop doesn’t.

00 · INPUThuman
Intent & constraints
What the business actually wants, what it can’t tolerate, and the success criteria the system will be judged against. Written down. Signed off. Not assumed.
↓   decompose
01 · PLANplanner agent
Task graph
Decomposes intent into a graph of bounded sub-tasks with explicit hand-offs and stop conditions.
02 · GROUNDretrieval
Context layer
Pulls the right code, docs, data, and prior decisions. Caches what’s expensive; invalidates what’s stale.
03 · GUARDpolicy
Guardrails & rollback
Allow-lists, budget caps, write-scopes, and the human gates that keep the system in its lane. If you can’t roll back, you can’t ship.
↓   execute
04 · EXECUTEworker agents
Specialist agents calling typed tools
Small, single-purpose agents with narrow tool surfaces. Each one is independently testable, observable, and replaceable. No mystery monoliths.
toolread
Code & docs
toolread
Data & metrics
toolwrite
On-chain / off-chain
toolwrite
PRs, tickets, comms
↓   check
05 · VERIFYcritic + evals
Critic loop & evaluations
Independent critic agents, deterministic tests, and a small set of golden evals. Failure routes back to plan; success routes to ship. Every run is traced.
06 · SHIPhuman
Hand-off, observe, stand behind
Outputs land where work already lives. We deploy, observe, and stand behind it. Not prototype-and-disappear.

04 / 02 My Approach — WATED, Five Pillars

Layer 2 of 3 · The Design Framework. Every agentic system AR Data builds is designed across five pillars. Skip one and the system works in demo, then dies in production.

We name them WATED so the conversation with your team is the same conversation every time. Each pillar has its own choices, its own failure modes, and its own rollback story. We make all five explicit before we write a line of code — and we revisit them every time the system grows.

/ 01
W
Workflow
The business process being transformed — mapped end-to-end, with explicit hand-offs, decision points, and the human roles that already live in it. We change the workflow first; the agents come second.
/ 02
A
Agent
Specialist agents with bounded scope, defined prompts, and clear stop conditions. Small enough to test in isolation, narrow enough to replace. No mystery monoliths.
/ 03
T
Tools
Typed tool surfaces the agents can call — read-only by default, writes behind allow-lists. Every tool has a contract, a test, and a rollback path.
/ 04
E
Events
Triggers & signals — webhooks, queues, schedules, on-chain events. Async by default, idempotent on retry, observable on every hop. Agents react to events; they don’t live in a chat box.
/ 05
D
Data Storage
Where state lives — vector for retrieval, relational for truth, KV for cache, on-chain for trust. Right store for the right durability and read pattern. Schemas owned, not generated.

↳ WATED is AR Data’s own framework — proven across finance, enterprise, and Web3 engagements.

04 / 03 My Approach — BMAD, The Agent Crew

Layer 3 of 3 · The Build Crew. WATED defines what we build. BMAD defines how we build it — a structured crew of specialist agents from analyst’s brief to QA sign-off.

BMAD — the Breakthrough Method for Agile AI-Driven Development — is a public open-source method (BMad-Method) for AI-assisted software delivery. AR Data adopts it as-is and runs it inside the WATED frame, so the deliverables map cleanly to the five pillars.

Each hand-off is a typed artifact — replayable, reviewable, and reversible. Stories sized for a single agent to land. QA approves or routes back; nothing ships without a rollback.

01 · DISCOVERY
Analyst
Researches the domain, the users, and the prior art. Writes the project brief.
OUT: Project brief
02 · INTENT
PM
Turns the brief into a PRD with epics, success criteria, and explicit non-goals.
OUT: PRD
03 · DESIGN
Architect
System design across the WATED pillars. Trade-offs documented; rollback paths named.
OUT: Architecture doc
04 · PLAN
Scrum Master
Drafts shippable stories from the PRD & architecture. Sized for a single agent to land.
OUT: Stories
05 · BUILD
Dev
Implements each story end-to-end — code, migrations, tests, observability hooks.
OUT: Pull requests
06 · VERIFY
QA
Runs the golden evals, security checks, and rollback drills. Approves or routes back.
OUT: Sign-off

05 Principles

Four things I believe after two decades of shipping. They aren’t slogans — they’re how AR Data picks engagements.

/ 01
Production is the only thing that counts.
A demo is a hypothesis. A deployed system that survives a Monday morning is a result. We measure ourselves against the second.
/ 02
If you can’t roll back, you can’t ship.
Every system we deploy has a reverse gear. Migrations are reversible, agents have kill-switches, decisions are traceable. Forward velocity without rollback is a bug, not a feature.
/ 03
AI tooling moves fast. Maintenance doesn’t.
Generated code is cheap; the system it ships into still has to be operable on a Tuesday in three years. We pair AI speed with the engineering judgment that makes it durable.
/ 04
No bench. No prototype-and-disappear.
Bootstrapped means we only take work we can actually deliver. The team that wins your engagement is the team that builds it — and stands behind it after.
/ 05 · FOUNDATIONAL
Agentic workflow. Human drives the outcome. AI supports.
An agent is a tool, not a decision-maker. The human owns the goal, the success criteria, the trade-offs, and the sign-off. Agents accelerate the work between those decisions — they do not replace them. Every system we ship makes that boundary explicit: who decides, who executes, who reviews. Get this wrong and you don’t have an agentic workflow; you have an unattended liability.

06 Selected Work

Engagements where the workflow earned its keep.

[ case study screenshot ]
/ 01
CASE STUDY · 01 — FINTECH

Compliance-grade agentic review for a tier-1 bank

A trading-floor compliance team buried in document review. Built a small graph of specialist agents with a rollback-by-default policy, a typed audit trail, and a human review gate on every write. Survived audit. Still in production.

review throughput
100%audit trail
0false-ship
[ case study screenshot ]
/ 02
CASE STUDY · 02 — WEB3 INFRA

Filecoin / IPFS pipeline with an agent ops layer

Storage clients with petabyte-scale deal flow needed monitoring, retrieval verification, and remediation that didn’t require a human on every alert. Drawing on Protocol Labs work, we shipped an agent ops layer that handles the boring 95% — humans handle the rest.

PB-scaledeals managed
−70%on-call load
99.9%retrieval SLA
[ case study screenshot ]
/ 03
CASE STUDY · 03 — ENTERPRISE

Migrating a Fortune-100 chatbot to a multi-agent assistant

Took a single-prompt support bot and decomposed it into specialist agents with typed tools, a router, and a golden eval set built from real historical tickets. Quality, cost, and latency moved the right direction at once. Rare combo.

2.4×resolution rate
−38%cost / session
p95 −1.1slatency
[ ← placeholder — your engagement here ]
/ 04
NEXT · YOUR PROJECT

Your production system here.

If your team is between “we played with an LLM” and “we’re running it in production with our eyes open” — that’s the gap AR Data closes. Send a brief; let’s scope it.

discovery call

07 Contact

Let’s build
the production system.

AR Data takes a small number of engagements at a time. The discovery call is free, 30 minutes, and the fastest way to find out whether an agentic system is the right tool for your problem — or whether it isn’t.