TYRIEN JONES AI ENGINEER · FOREMAN
THE LEAD PROJECT v1 SHIPPED 28 JUN 2026 · v2 PLANNED

OPERATIONAL_CORE

Business software a small operator buys once and owns. It runs on their own PC, keeps working with the internet off, and there’s no monthly bill.

BUILT17 – 29 Jun 2026
COMMITS66
TESTS356 · 6 suites
RUNSTheir own PC, offline
AI INSIDENone
PRICE MODELBUY ONCE
OPERATIONAL_CORE's Home screen: 2 jobs today, $400.00 outstanding, $544.50 paid this month, today's callouts and the recent invoices.
HOME · THE DAY AT A GLANCE
A printed tax invoice from OPERATIONAL_CORE: jetting, a drain camera inspection and 2.5 hours labour, subtotal $636.36, GST $63.64, total $700.00, $300.00 paid and $400.00 owing.
TAX INVOICE · AS IT PRINTS
Two job cards: a bathroom rough-in quoted for 6 November, and a leaking stop valve on site for 4 November, each with its next-step buttons.
JOBS · BOOKED BY DATE
The money panel: $944.50 billed and $544.50 paid this month, 58% collected, $400.00 outstanding and nothing overdue.
MONEY · BILLED, PAID, OWED
The Backup panel: backed up today, 47 files saved to a separate drive, with a Back up now button.
BACKUP · RAN TODAY

All five from v1 running on my PC · demo data for a made-up plumbing business · plumber skin

00 · IN PLAIN TERMS

Most small operators rent their business software. Stop paying and you lose access to your own records. OPERATIONAL_CORE goes the other way: you buy it once, it lives on your machine, and your files stay yours.

It’s built for the sole trader or a crew of one to three: someone who wants to quote it, get paid, and hand clean numbers to their accountant, without paying for payroll, tax lodgement and bank feeds they’ll never use.

01

The job

The daily paperwork of a small business, done properly and kept on the owner’s own machine.

WORKING TODAY · v1
Customers
Who you work for, and what each one owes
Jobs
The work, scheduled by date
Invoices
With GST, laid out as a proper tax invoice, ready to print
Payments
Money received against each invoice
Settings
The business’s own details on every document
Backup
Daily local backup, a nudge if the off-site drive hasn’t been seen, and a written restore guide

No subscription. No account. Nothing phoning home.

02

What’s mine

The design, the rules and every decision. The code was written by AI under those rules, and nothing was sealed until it passed.

THE RULES IT’S BUILT ON
No AI inside
AI built it; there’s no AI in it. Invoices have to come out exact and the same every time, and a model that’s confidently wrong about a tax figure is a liability.
The disk is the truth
Every record is a plain file on disk. The database is only an index: delete it, rebuild it, and the same records come back.
Money in whole cents
No rounding drift. Half a cent is rejected, not stored.
Boring on purpose
Same inputs, same outputs. No hidden state, no background magic.
Secrets stay out
Nothing sensitive is ever written into the code.
ONE CORE A neutral business engine. Nothing in it is hard-wired to one trade.
MANY TRADES Each trade is a skin. Plumber, mechanic and neutral ship today. Fitting a new trade is a settings job, not a rebuild.
03

Wired in

Deliberately short. The only outside packages are the web framework and its server; everything else is the Python standard library.

MATERIALS LIST
Records layer + rules
Customers, jobs, invoices, payments, the money rules
MY DESIGN
Web screens
Plain HTML, CSS and JavaScript, print-ready invoices, trade skins
MY DESIGN
Backup + restore
Daily job, off-site nudge, restore guide
MY DESIGN
Storage engine
My own FORGE records engine from L.I.LY, lifted read-only and re-fitted to this schema
MY DESIGN
FastAPI · uvicorn
The local web server
WIRED IN
SQLite
The rebuildable index
WIRED IN
04

How I ran it

The same shape as every job: one agent plans and writes the work up, another builds it, a separate one audits it, and nothing is sealed until I’ve checked it first-hand.

PLANLead
BUILDBuilder
CHECKAuditor
SIGN OFFMe

It was built in sealed phases, each one finished and tested before the next began: the storage engine first, then record history, then customers, jobs and money, then the web layer, then the screens.

05

The receipts

LEDGERSOURCE: GIT HISTORY + TEST FILES
356tests across six suites: engine 108 · money 88 · web 105 · backup 37 · screens 14 · skins 4 66commits, 17 to 29 June 2026, each one a single described change ~8,400lines of app code, with only two outside packages SoakedA stress harness that hammers it with hostile input and checks the books still add up
07

Why it counts

This is what I mean by built to last. No AI to drift, no vendor to change the rules, no subscription to lapse. It does the same thing tomorrow that it did today, on the owner’s own machine.

If your business needs software that just keeps working, this is how I build it.

WORK WITH ME Need software that keeps working for years, not months?
LET’S TALK ABOUT THE JOB →