I wanted a better map, so I built one. It got slightly out of hand.
SOFTWARE, MOSTLY. SINCE JUL 2025.
Lineage of the projects on this page, laid out by month from July 2025 to August 2026. Scout Optimizer leads to EF-Map. EF-Map is still running and has EF Helper, Civilization Control, Flappy Frontier and RootFit attached to it, and EO-Map forked from it. Shadow Broker Protocol, Civilization Control and Flappy Frontier came out of the March 2026 hackathon. Frontier Commerce and the SSU open shelf are Sui projects separate from the map.
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.
None of what follows was a plan. Scout Optimizer did not know about gates, and it could not show you anything. That limitation is why the map exists.
It started as a better map. It is now routing, reachability, activity, structures, search, overlays and history. Most of the questions people were asking in chat, answered in one place.
Schematic of a star-system graph with a selected route from origin to destination. Some neighbouring systems sit outside jump range. Not measured data.
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 with modules packed into usable cells. Not a real fit.
This one is not a website. EF Helper is a Windows app: C++ talking to a DirectX 12 overlay inside the EVE Frontier client, and to EF-Map over localhost. 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.
Open-source payment infrastructure for Sui applications: one-off payments, subscriptions and entitlements, prepaid credits, merchant treasuries, revenue splits, refunds. Written once, so the next application doesn't have to invent its own payment plumbing.
Applications on one side, a reusable commerce layer in the middle, and the capabilities it provides on the other side.
Operating EVE Frontier infrastructure from a browser: smart gates, turrets, storage and trade structures, instead of hand-assembling Sui transactions to do it.
Ownership capability leads to governance, which controls gates, turrets and storage or trade structures.
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.
A Smart Storage Unit where the hangar is a shared shelf. Anyone can take, once the owner turns it on.
A silly game for the same hackathon. The standalone site is retired. The game now lives inside EF-Map.
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 already started attaching themselves to it. It is new. It is already more than a map.
The same small star-system graph shown three times. Routing marks one selected path. Sovereignty marks a different set of systems. Faction warfare and incursions mark another. Schematic, not measured data.
Two of the things above came out of the same EVE Frontier hackathon. Civilization Control placed third overall. Shadow Broker Protocol won the weirdest-idea category, which still makes me laugh a bit.
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 the studio.
CATALYST, 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 THEMEWhich means ingest, caching, uptime, and keeping the lights on after a game patch. I did not have that job in 2025.
STILL RUNNINGI don't write much of the code.
I still don't. I write what I want, and I write what done has to look like, usually with an LLM helping me think it through. An agent does the implementation on a branch. The actual work is deciding what should exist, and refusing the version that isn't right.
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.
The sentence at the top of this section is doing a considerable amount of hiding.
Currently: EO-Map, which is new enough that I'm still finding out what it wants to become, and 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.