ALLENHBUILDS · FINANCE // TECHNOLOGY // DESIGN
I closed the books.
I did not sponsor the automation — I wrote it.
Software for the last week of the month, built by somebody who spent twelve years living it. Every number it produces can be traced to the cell it came from, and it says so out loud when it cannot explain one.
The work
A close engine, the harness that tests it against data with a known answer, an AI accounting employee that gets refused when it asks to post, and a rail-trail GPS app that has no business being in the same sentence. The case files are written and the work is built. This door opens when they do.
The dossier
Twelve years of healthcare accounting, what got automated, what it saved, and the parts that did not work. Written for somebody deciding whether to hire me.
01 What it is
I am building software that closes the books. While I build it, I will do the close work myself, and the software is how you can tell I know how.
The close is the last week of every month, and most of it is not accounting. It is reconciling what the ledger says against what the facilities actually sent, deciding what belongs in the month and what does not, and being able to say why afterward. I did that by hand for twelve years and then I wrote it down as code.
Written for the people who actually do it — a controller, a shared-services group, anybody who spends the last week of the month with two windows open and a calculator.
What goes in
A month of accounts payable, the ledger it has to agree with, and whatever the facilities actually sent — which is never quite what the process says they sent. It reads the files as they arrive rather than as they ought to arrive, because the second kind does not exist in a real month.
What it does
Rules run in a fixed order, and every row that leaves carries the reason it left. Nothing is erased — the row is copied out and stamped, the way you post a contra instead of scratching out an entry. Months later you can still ask any row where it went and get an answer.
What it refuses to do
Hand you a number it cannot explain. Where a row has no clean answer it says so and stops, instead of picking the likelier of two and moving on. That sentence is most of the work in there, and it is the reason it is not finished yet.
It is not a dashboard, it is not a chat window bolted onto a ledger, and it is not for sale yet.
02 Proof
Anybody can claim their software is right. Not many will hand you the check.
Accounting software is sold on adjectives. Fast, accurate, seamless — none of which a buyer can test before they have already handed over their books. So everything here is built the other way around: the checking is a program that fails the build, not a sentence above the data, and the results are things a stranger can verify without trusting me first.
A close run starts with a month of payables and one question: which of these belong in this month's accrual? That run was 890,222 rows. Under ten steps took the answer down, the balance and every declared check re-run after each one, and it tied at the end. Tying is not the same as being right — run the steps out of order and it stops at the step that broke.
It is tested against data I generate, and that data ships with an answer key: the count of what is wrong inside it, written down beforehand. So a run is graded against a number instead of against a feeling that the output looked reasonable. Four real defects turned up that way, and every one of them had produced a balanced, reconciled, plausible answer. That is why reading the code had not found them.
Nothing to do with accounting. Thirty-four total eclipses, recomputed from the orbital elements in Python and held against NASA's published tables before this site is allowed to build. Worst disagreement, half a second. It is here because checking it costs you nothing — pick one and look it up — and a man who will show his arithmetic on something that does not matter will show it to you on something that does.
Every figure on this page is in the evidence ledger with its basis, its source and the date I last checked it. Read the ledger.
03 The tower
Not open yet
Where the levers are
Build state, the run dashboards, the evidence packs, and the material that is not anybody else's business yet. Access is by invitation and by name — if you have not been given a door, there is nothing here for you to see. The door is not hung yet. When it is, it opens by invitation and by name.
04 THE RESEARCH
Making distributed
time visible.
Three clocks. One question: what happened before what?
Request the framework, then explore the advanced 3D Vector Clock Ledger. The paper and the application, side by side.
05 THE BUILDER / IN MOTION
I Built the Sky.
ALLEN HEIFNER / OFFICIAL MUSIC VIDEO
Your cue. The YouTube player loads only when you choose. Watch on YouTube
06 CURRENTLY BUILDING
Johns Hopkins Whiting School of Engineering
Applied study in generative and agentic AI.
The work continues. So does the study.
PROGRAM REGISTERCURRENT STUDY
-
In progress
Certificate Program in Applied Generative AI and Agentic AI
-
Enrolled
Certificate Program in AI and Agentic AI Engineering
Delivered in collaboration with Great Learning.