SOFTWARE, MOSTLY. SINCE JUL 2025.
I wanted a better map, so I built one. It got slightly out of hand.
PLATE IEVE FRONTIER, 24,018 SYSTEMS AT THEIR REAL POSITIONS
ROUTE… → … · … HOPS · SOLVED IN THIS TAB IN … MS
Opening plate: every visible star system in EVE Frontier, drawn as a slowly turning point cloud, with a route solved between two of them.
Timeline of the projects on this page from July 2025 to 24 SEP 2026, one row each. Scout Optimizer came first, in late July 2025, and its idea moved onto EF-Map, which started in August 2025 and is still running. EF Helper, a native Windows app that talks to the map, shipped to the Microsoft Store in October 2025. Civilization Control, Flappy Frontier and Shadow Broker Protocol came out of the March 2026 hackathon; Civilization Control placed third overall and Shadow Broker Protocol won the weirdest-idea category. Civilization Control runs under EF-Map, Flappy Frontier now lives inside the map, and Shadow Broker Protocol is separate. RootFit followed in June 2026 under EF-Map. Frontier Commerce and the SSU open shelf are separate Sui projects from July 2026. EO-Map was forked from EF-Map in August 2026.
In July 2025 I wasn't building software. I was trying to work out what order to visit a couple of hundred stars in, and the in-game map is not built for that.
So I made Scout Optimizer. No map. You give it a start system and a radius, and the tab just chews on a route. That was the first thing I got an LLM to produce that actually ran, and the first time I put something on the internet.
Scout Optimizer didn't know about gates, and it couldn't show you anything. That's why EF-Map exists. None of what follows was a plan.
PLATE IISCOUT OPTIMIZER, RE-RUN IN THIS TAB
A live re-run of the Scout Optimizer idea: a start system and every system within a fixed radius of it, ordered first by nearest neighbour, then improved by 2-opt swaps and simulated annealing. Straight-line distances only; nearby gates are drawn faintly and ignored.
It started as a better map. Now it answers most of the questions people used to ask in chat, in one place.
PLATE IIITHE SAME SYSTEMS, WITH GATES
EVE Frontier's systems and gate links, with a route between two systems solved live in the browser, taking gates where it can and otherwise jumping up to 100 light years at a time.
Fitting in EVE Frontier is a packing problem, not a slot list. RootFit is a browser planner on the real hull grid, using data pulled from the client, so you can try a fit before you spend the materials.
Schematic hull grid of 60 cells holding six modules of 26 cells in total. Placed first wherever they fit, the largest free block is 10 cells. Moved so the free space is in one piece, it is 32cells. Not a real fit.
This one isn't a website. EF Helper is a Windows app, C++ talking to a DirectX 12 overlay inside the EVE Frontier client on one side and to EF-Map over localhost on the other. Routes show up in-game. I put it on the Microsoft Store.
Chain of four parts: the game client, the injected overlay, the helper process, and EF-Map. Below it, a schematic of the game client with the overlay drawing a route panel, fed with a real route solved in the browser.
It's the open-source payment side of a Sui app, written once so the next one doesn't have to invent it. One-off payments, subscriptions and entitlements, prepaid credits, merchant treasuries, revenue splits and refunds.
Applications on one side, a reusable commerce layer in the middle, and the capabilities it provides on the other side.
It's for running EVE Frontier infrastructure from a browser. Smart gates, turrets, storage and trade structures, without hand-assembling Sui transactions to do any of it.
Ownership capability leads to governance, which controls gates, turrets and storage or trade structures. With script, the power switches work while you hold the capability and refuse when you don't.
| SMART GATE | ACCESS POLICY | |
|---|---|---|
| TURRET | DEFENSIVE POSTURE | |
| STORAGE / TRADE | TRADE TERMS | COMMERCIAL POSTURE |
| NETWORK | INFRASTRUCTURE STATE | EVENT FEED |
A marketplace for intelligence you can't show before selling it. Encrypt it locally, store it on Walrus, publish two seconds of it, and sell ownership in a single atomic transaction. Nobody holds anybody's money.
Seller encrypts intel and stores it on Walrus as an IntelObject. A two second teaser informs the buyer. An atomic purchase makes Seal release the key.
IT WAS ALWAYS GOING TO BE A MAP.
ENCRYPTED · STORED ON WALRUS · FOR SALE
A Smart Storage Unit where the hangar is a shared shelf. Anyone can take, once the owner turns it on.
A silly game I made for the March hackathon. The standalone site's retired and the game lives inside EF-Map now.
Almost a year after EF-Map, I pointed the same idea at EVE Online. It started as a 3D map and a route planner. Sovereignty, faction warfare, incursions and traffic have started attaching themselves to it, and you can watch that happen below. It's new, and it's already more than a map.
PLATE IVTHE SAME IDEA, POINTED AT NEW EDEN
The EVE Frontier point cloud rearranges itself into New Eden, EVE Online's map, as the page scrolls. Then a route between trade hubs is solved over New Eden's gates, and layers attach themselves in turn: security status from EVE Online's static data export, then live sovereignty, faction warfare, incursions and traffic fetched from ESI, EVE Online's public API.
Three of the things above came out of the same EVE Frontier hackathon. Civilization Control placed third overall and Shadow Broker Protocol won the weirdest-idea category, which still makes me laugh a bit. Flappy Frontier didn't win anything, which is fair.
THIRD OVERALLI ended up on stage at FanFest talking about EF-Map to a room of people who actually use it.
ONE TALKThe tools also led to me joining the first Conclave of Luminaries, a player group that talks directly with Fenris Creations.
NOT A BADGEPeople use EF-Map to decide whether a route is worth flying. They find the wrong number before I do, and they tell me about it.
THIS IS THE PARTAlmost all of this happened because of EVE Frontier and the people around it. That's where the problems came from, and the bug reports.
CATALYST, NOT THEMERunning all of this means ingest, caching, uptime, and keeping the lights on after every game patch. I didn't have that job in 2025.
STILL RUNNINGI don't write any of the code.
Not a line of it. I couldn't write hello world if you asked me to, and I don't think that's anything to be ashamed of. The job is everything around the code. I investigate, I understand the architecture well enough to spot when an answer is wrong, and I define what should exist and what done looks like, usually with an LLM helping me think it through. Then I point agents at it and they build it on a branch. I test the preview and send back anything that isn't right, and once it ships, the people who use it tell me what I missed.
End-to-end path of a change: human intent and architecture, a coding agent on a branch, automated tests and preview, human review, commit, production, then users finding what was missed and the loop starting again. Dashed lines are iteration, not a second kind of work.
One box in that loop writes the code, and it isn't me.
At the moment it's EO-Map, which is new enough that I'm still finding out what it wants to become, and rewriting the parts of EF-Map I built before I knew better.
If you use one of these and it's wrong, tell me. That's usually how it gets fixed.
