James Wilkinson

I build self-contained intelligence systems, and I run them the way I was taught to run a reactor plant.

History

U.S. Navy, nuclear submarine force — 2014 to 2024. Ten years on naval nuclear propulsion plants: Machinist's Mate, then Engineering Watch Supervisor leading a 15-person watch team, staff instructor for more than 250 nuclear operators, project manager for pressurized-compartment testing, and maintenance manager for more than 100 people.

Google, data center critical facilities — 2024 to 2026. I operated and maintained the critical power and cooling infrastructure a data center cannot run without, and worked through construction and commissioning — taking new systems from installation to proven and in service. Most of the work was reliability: planned maintenance, change control, and managing the vendors and contractors who carried out specialised work, so that uptime came from procedure rather than luck. Project management was the daily tool.

Blackhull Systems — 2026. In August 2026 I left Google to build Blackhull Systems full time.

What I built

I learned this field the way the Navy taught me a reactor plant: by building the whole thing myself and running it.

On hardware I assembled and operate, there is a complete, self-contained intelligence system:

Its own models. Open-weight language models served locally from two GPUs in my own rack.

Its own fleet. Ten machines across two physical servers, each built and configured from code. A change reaches a machine only through a release I sign.

Its own engineers. Agents write and review much of the system's code, under rules they cannot loosen. Every change is tested before it lands — more than 1,200 so far, against a suite of more than 21,000 automated tests.

Its own safeguards. Credentials are held by a broker the agents can use but never read. Every safety-relevant action is recorded in a tamper-evident ledger — more than 5,600 entries.

Its own public face. The company website is published by the system, and every sentence on it is checked against its evidence before it goes out.

It runs my company. It is also why I can tell someone what is worth building: I have built, broken and repaired every layer of it myself.

Principles

Procedure before improvisation. If a task matters, it has a written procedure, and the procedure is followed or changed — never skipped.

Verify independently. A check proves something only if it could have failed. I test the test.

Nothing changes unsigned. Every change to a running system is reviewed and approved by a person before it ships — including mine.

Your data stays with you. A system I build runs where the data already lives. Nothing leaves unless you send it.

Hand it over. Documented so the people who own it can run it without me — and the choice to keep me on stays theirs.

Say what it doesn't do. Limits stated up front. Sometimes the right answer is not to build at all.

Silence is the healthy output. A good system reports what changed, or that it can no longer see — not that nothing happened.

Elsewhere

LinkedIn · GitHub · Blackhull Systems · james@blackhull.systems

Charleston, South Carolina · PMP · U.S. Navy veteran