Skip to content
Felipe Arce
About
Cover sheet · Rev 2026.10Systems architect · infrastructure engineer

Felipe Arce

  • Lead Software EngineeratExowatt
  • Founding engineer & CTOatOlie, side project
  • Co-owner & maintaineratCopper

Ships today. Stands for ten years. Carries the first million users.

Now
Before
Studied
What this isGet in touch
Key · what you are reading10 sheets · about 5 minutes

A drawing set in ten sheets: what Felipe builds now at Exowatt, what he builds alongside — Copper and Olie — what came before at Microsoft, and the record.

  1. Part I — NowSheets 01 – 04
    Exowatt (opens in a new tab)

    Lead Software Engineer

    Jul 2026 →

    An agent collaboration platform, energy-fleet infrastructure, two fine-tuned models and the internal platform.

    commits
    3,900+
    repositories
    65+
  2. Part II — AlongsideSheet 05
    Copper (opens in a new tab)

    Co-owner & maintainer

    Sep 2026 →

    A small, fast Mac browser that agents can drive.

    commits
    128
    download
    ~7 MB
  3. Part II — AlongsideSheet 06
    Olie (opens in a new tab)

    Founding engineer & CTO

    2025 → · side project

    A cross-border wealth app, built from the screen down to settlement.

    commits
    5,278
    networks
    3
  4. Part III — BeforeSheet 07
    Microsoft (opens in a new tab)

    Software Engineer, Azure

    2022 – 2026 · intern 2021

    Azure’s incident platform, released into public, sovereign and air-gapped clouds.

    years
    4+
    cloud classes
    3
Part IV — The record
Sheet 00 / 10
Drawing index

Chapter 00: The drawing set

The whole set at a glance — ten sheets in four parts.

  1. Step 01 / 01

    Now, alongside, before — then the record. Every sheet opens its chapter.

    Engineering note: Index · 10 sheets · 4 parts

01AgentsI02FleetI03ModelsI04AppsI05CopperII06OlieII07MicrosoftIII08CareerIV09Open sourceIV10ContactIV
Fig. 0.1 — The drawing set

Part I2026 →

Part I: Now

Sheet 01 / 10
Part I — Now

Chapter 01: Agents, together

Built the shared layer that lets a team of AI agents work as one.

Exowatt (opens in a new tab) · Lead Software Engineer · Jul 2026 →

  1. Step 01 / 03

    Many agents, one codebase: left alone, they collide on the same work and files.

    Engineering note: 16 agents · identity · heartbeats

  2. Step 02 / 03

    Work routes to the right board; agents claim files first, and overlapping claims are turned away.

    Engineering note: 30 boards · artifact claims · overlap checks

  3. Step 03 / 03

    Agents pull ready work in dependency order, close it, and leave a trail to resume.

    Engineering note: 43 tools · 6 skills · 7 hooks

    Work items opened by agents and their humans.
    13,481tracked
    Finished and closed: 95% of everything tracked.
    12,831closed
    Multi-step efforts carried from plan to done.
    923+epics closed

    As of October 2026.

same file, twice
claimed first · the overlap is turned away
dropped, then resumed
95%closed
Fig. 1.1 — Swarm to structure · one dot ≈ 50 work items
Sheet 02 / 10
Part I — Now

Chapter 02: The energy fleet

Software that runs energy at every site: built from bare metal, tunneled home, shipped deliberately.

Exowatt (opens in a new tab) · Lead Software Engineer · Jul 2026 →

  1. Step 01 / 03

    A bare industrial computer becomes a running site, one repeatable role at a time.

    Engineering note: 25 Ansible roles · k3s · 21 bundles

  2. Step 02 / 03

    Every site dials out over an encrypted tunnel to one gateway. Nothing dials in.

    Engineering note: WireGuard hub-and-spoke · MQTT/TLS · ~30 s heartbeat

  3. Step 03 / 03

    Releases move site by site. One failed check halts the wave; that site rolls back.

    Engineering note: Preflight → apply → gate · known-good pin

    Everything a site runs, from one audited snapshot.
    21bundles / site
    Up to 49 simulated systems per site, before metal.
    10Hz digital twin
    His, across the energy-management repos.
    ~1,800commits

    Since July 2026: site controller, deployment, cloud, telemetry, simulators.

Fig. 2.1 — One box, then the fleetA row of identical sites on a horizon. One bare industrial computer fills layer by layer as its 25 setup roles run, then every site gets the same build. Each site dials out over an encrypted tunnel to one gateway; nothing dials in. A release then crosses the row like daylight, committing each site's new layer; one site fails its gate, steps back to its known-good layer, and the light halts there while the sites beyond wait.
one inventory entry → one site
dials out · nothing dials in~30 s heartbeat
gate failed → back to known-good
Fig. 2.1 — One box, then the fleet
Sheet 03 / 10
Part I — Now

Chapter 03: Two models

Same principle, two physics: a small model at the site, a bigger one in the cloud.

Exowatt (opens in a new tab) · Lead Software Engineer · Jul 2026 →

  1. Step 01 / 03

    A 1.7B model triages site alarms on the site's own computer, with no internet.

    Engineering note: F1 0.91 · fabricated claims 28 → 0

  2. Step 02 / 03

    A 14B model, fine-tuned in the cloud, reads the energy market and cites its evidence.

    Engineering note: 2,000 held-out packets · 98.3% events right

  3. Step 03 / 03

    On market events it beats a frontier model, and costs 49× less to run.

    Engineering note: Macro-F1 0.975 vs 0.625 · stock 0.415

    Market events named, on 2,000 held-out packets.
    0.975macro-F1
    $0.60 vs $29.26 per 1,000 packets, against a frontier model.
    49×cheaper
    Typical answer time; in production since September 2026.
    10 sp50

    Scored on packets the model never saw in training.

Fig. 3.1 — Scale you can see · 1 block = 100M parameters
Sheet 04 / 10
Part I — Now

Chapter 04: The quiet platform

The internal apps every other app quietly stands on.

Exowatt (opens in a new tab) · Lead Software Engineer · Jul 2026 →

  1. Step 01 / 03

    Dozens of internal apps, each solving login, people, access and mail on its own.

    Engineering note: Duplicated roster · keys · access · mail

  2. Step 02 / 03

    He built the shared hubs they lean on: connectors, one roster, access, mail.

    Engineering note: Scoped grants · hash-chained audit · self-revoking access

  3. Step 03 / 03

    Underneath, the shared app platform he helped build: push a manifest, get an isolated app.

    Engineering note: Push → isolated app · TLS · database

    Read one people roster instead of keeping their own.
    13+apps
    Company tools reached through one audited gateway.
    10connector families
    Ways an agent asks for time-boxed admin access.
    6access tools
    His, on the virtualization operations console.
    248of 250 commits

    Lower bounds, counted from code and docs.

Fig. 4.1 — App constellationA star chart of internal apps. First every app carries its own four satellites — people, logins, access and mail — each solved alone. Then four shared hubs ignite — a people roster, a connector hub, just-in-time access and a mail relay — and the satellites of the apps that lean on them fall in (13+ apps read the one roster); each hub grows by what it absorbed. Last the hubs settle onto a horizon, the shared app platform that 33+ repositories stand on, and a pushed manifest lands on it as a new, isolated app.
every app, alone
13+ apps read one roster
push a manifest, get an isolated app
Fig. 4.1 — App constellation

Part II2025 →

Part II: Alongside

Sheet 05 / 10
Part II — Alongside

Chapter 05: Copper

A small, fast, quiet browser for the Mac — and the one agents actually drive.

Copper (opens in a new tab) · Co-owner & maintainer · Sep 2026 →

brew install --cask copper-browser/copper/copper

  1. Step 01 / 03

    One native Mac window on WebKit — the whole browser is a 7 MB download.

    Engineering note: SwiftUI + AppKit · WebKit · Apple Silicon

  2. Step 02 / 03

    Sleeping tabs cost nothing until opened; sign-ins stay in your Mac’s Keychain. No telemetry.

    Engineering note: Lazy tabs · Keychain sign-ins · no account

  3. Step 03 / 03

    Agents drive the window you already have open — real tabs, real sign-ins, every step traced.

    Engineering note: Local MCP server · ~200 ms per decision

    His, as co-owner and maintainer, since September 2026.
    128commits
    The whole download; about 11 MB once installed.
    7MB
    Per agent decision; a small model only writes the text.
    ~200ms

    Commits from the public repository; sizes and timing as published.

Fig. 5.1 — Two hands, one windowA browser window drawn by hand, small, with air around it: traffic lights, five tabs, an address bar with a lock, a sidebar and a page. A bracket under it measures the whole browser at 7 MB. Four tabs fall asleep into dotted outlines while the one you are on stays awake, and a key leaves the lock for a Keychain ring outside the window. Then your cursor rests at the window's edge while the agent's cursor fills the message field with “Hello” and clicks Send, the path it took left behind as the trace, at about 200 ms per decision.
Fig. 5.1 — Two hands, one window
Sheet 06 / 10
Part II — Alongside

Chapter 06: All the way down

A cross-border wealth app — digital dollars, savings, Bitcoin — built from the screen to settlement.

Olie (opens in a new tab) · Founding engineer & CTO · 2025 → present · side project

The live product · oliecrypto.com(opens in a new tab)

  1. Step 01 / 03

    One product on web, iOS and Android: three lines, one design system, one API.

    Engineering note: 38 shared components · 117 vault screens

  2. Step 02 / 03

    Money never pretends to move instantly: reserve, queue, then work. Releases pass a health gate.

    Engineering note: k3s on Azure · Terraform · 27 workflows

  3. Step 03 / 03

    One transfer rides out to Ethereum, Polygon or Bitcoin — and its receipt rides back.

    Engineering note: CCTP bridge · 2-of-3 Bitcoin · receipt monitors

    His: about nine in ten of the product's commits.
    5,278commits
    Tests, images, gated promotion, app builds, TLS, secrets.
    27CI/CD workflows
    Ethereum, Polygon and Bitcoin; testnets outside production.
    3networks
    Any two of three keys sign; one key alone moves nothing.
    2-of-3Bitcoin custody

    Commits 2025 – Sep 2026; workflows and networks as in today's source.

Fig. 6.1 — One transfer, by lineA transit map drawn by hand. Three coloured lines — web, iOS and Android — run together into one API interchange; a single trunk line continues through Reserve, Queue and Workers to a junction that divides toward Ethereum, Polygon and Bitcoin. One transfer rides it: it leaves iOS, waits at Reserve while its balance is held, pulls into the Queue's siding behind two others and takes its turn, then rolls on to the Workers. It rides out to Bitcoin, where two of three keys turn, and comes back as a hollow receipt that fills in when it reaches the app.
one API
money never pretends to move instantly
its receipt rides back
Fig. 6.1 — One transfer, by line

Part III2021–26

Part III: Before

Sheet 07 / 10
Part III — Before

Chapter 07: Clouds you can’t reach

Azure’s incident tool can’t go down, and must ship to every cloud, even offline ones.

Microsoft (opens in a new tab) · Software Engineer, Azure · 2022 – 2026 · intern 2021

  1. Step 01 / 03

    An incident anywhere echoes back to one platform. He built the screens responders work in.

    Engineering note: Incident query + postmortems · C# · React

  2. Step 02 / 03

    Every release of it ripples out ring by ring: tests, public, sovereign. Bad changes stop early.

    Engineering note: Flaky tests set aside · multi-stage rollout

  3. Step 03 / 03

    The last ring has no internet. Each release is sealed, carried across, checked again.

    Engineering note: Air-gapped · sealed artifact · same verification

    Public, sovereign and air-gapped, on one staged release path.
    3classes of cloud
    Full-time on the incident platform, after a 2021 internship.
    4+years on Azure

    Facts from his résumé and profile; Microsoft’s internal numbers stay internal.

Fig. 7.1 — One release, ring by ring, past the air gapThree ripples spread around one incident platform: tests, public and sovereign clouds. Across a stretch of open water lies an island, the air-gapped cloud. An incident on each ripple echoes back to the platform. A release ripples out ring by ring, pausing at each; a bad change stops at the first ring. The water ends at the sovereign shore, so the release is sealed into a parcel, carried across where there is no internet, and opened on the island, where it is checked again.
echoes back to one platform
bad changes stop early
sealed, carried across, checked again
Fig. 7.1 — One release, ring by ring, past the air gap

Part IV2018 →

Part IV: The record

Sheet 08 / 10
Part IV — The record

Chapter 08: The arc

School, Microsoft, a fintech from zero, then agent infrastructure: eight years, drawn as a git log.

2018 → today · FIU · Johns Hopkins APL · Microsoft · Olie · Exowatt

  1. Step 01 / 04

    Miami, 2018: a computer-science degree, plus internships at Johns Hopkins APL and Microsoft.

    Engineering note: 2018 – 2021 · FIU B.S. CS · 2 internships

    git show
    commit b5c2112

    Merge branches 'fiu' and 'internships'

    MergeDec 2021main

    An octopus merge: the degree and both internships land on main together.

    Merge
    5e1d018 mainfa21c12 fiu1a21d0c internships
    Feeds
    9e26a07 main01e25a1 olie3c22a02 microsoft
    Lineage
    4 ancestors · 3 branches

  2. Step 02 / 04

    At Microsoft: the tool Azure engineers open mid-outage, then shipping it safely to air-gapped clouds.

    Engineering note: Feb 2022 · Azure IcM · full stack → CI/CD

    git show
    commit 3c24b07

    Reliability & CI/CD, Microsoft

    CommitJul 2024Miami, FLmicrosoft

    Flaky-test detection, test-pipeline resiliency, multi-stage rollouts across public and sovereign / air-gapped clouds.

    Parent
    3c22a02 microsoft
    Feeds
    9e26a07 main
    Lineage
    6 ancestors · 4 branches

  3. Step 03 / 04

    On the side, he builds a fintech from its first commit and becomes its CTO.

    Engineering note: 2025 → · Olie · founding engineer → CTO

    git show
    commit 01e26b9olieside project, ongoing

    Swap the deploy CLI for k3s

    CommitMay 2026olieside project · ongoing

    ~1,000 lines of homegrown deploy tooling replaced by stock rolling updates, probes, and rollout undo. Staging shipped in a day.

    Parent
    01e25a1 olie
    Lineage
    6 ancestors · 4 branches

  4. Step 04 / 04

    July 2026: Microsoft merges back, Exowatt branches off for agent infrastructure. Olie keeps running.

    Engineering note: Jul 2026 → · HEAD -> exowatt · olie open

    git show
    commit e26d01fHEAD -> exowatt

    ~90 days in

    CommitOct 2026exowatt

    1,200+ merged pull requests, 55 agent-runtime releases, 130+ platform workloads, 275+ CI/CD workflows.

    Parent
    e26a07b exowatt
    Lineage
    9 ancestors · 5 branches
Branches
Tap to isolate
git log --graph --oneline --all00 / 15 commits
e26d01fHEAD -> exowatt~90 days inOct 2026
0b26c23open-sourceCopperSep 2026
e26a07btag: v4.0.0Lead Software Engineer, ExowattJul 2026
9e26a07mainMerge branch 'microsoft'Jul 2026
01e26b9olieside project, ongoingSwap the deploy CLI for k3sMay 2026
0b26e04taggenMay 2026
01e25a1tag: v3.0.0Olie: founding engineer, then CTOJan 2025
3c24b07Reliability & CI/CD, MicrosoftJul 2024
3c22a02tag: v2.0.0Full-stack engineer, MicrosoftFeb 2022
b5c2112Merge branches 'fiu' and 'internships'Dec 2021
fa21c12tag: v1.0.0B.S. Computer ScienceDec 2021
0b21e99eggsecutorAug 2021
1a21d0cIntern, MicrosoftMay 2021
1a20e05Intern, Johns Hopkins APLMay 2020
5e1d018Initial commitAug 2018
Branch start
Commit
Merge
Milestone
Lineage
Live branch
Fig. 8.1 — Branch history

Sheet 09 / 10
Schedule · 07 entries

Chapter 09: In the open

Work you can read line by line: seven public repositories, from Rust to Swift.

Public repositories on GitHub · 2021 → today

  1. Copper — A small, fast, quiet browser for the Mac. (Sheet 05)
  2. tembedded — Firmware that rolls back its own bad OTA. GitHub (opens in a new tab)
  3. ITx daemon — Fleet agent: register, poll, ack, execute, report. GitHub (opens in a new tab)
  4. GALACTIC — Generate, deploy and read logs from one UI. GitHub (opens in a new tab)
  5. taggen — Every log line becomes a permalink to code. GitHub (opens in a new tab)
  6. eggsecutor — Rootless process supervisor on one state file. GitHub (opens in a new tab)crates.io (opens in a new tab)
  7. tz-rs — Typed Rust boundary for Tezos node RPC. GitHub (opens in a new tab)
Fig. 9.1 — Schedule of public workRanked by depth and recency
Sheet 10 / 10
Part IV — The record· Last sheet

Chapter 10: Let’s build something that lasts

Ship it today. Keep it running for ten years. If that’s what you’re building, let’s talk.

Miami, FL · Email is the shortest path

Fig. 10.1 — Channels