One machine.
A growing stack of useful systems.
This is the public edge of a small, locally controlled computing lab.
The work here is about turning messy inputs into useful systems: automation, reconciliation, analysis, agents, and software that quietly does the work it was built to do.
The machine is the tool.
The systems are the leverage.
Most of the interesting work happens somewhere you can't see.
A laptop serves as the lab's primary compute environment: running experiments, processing data, coordinating automations, and hosting the systems behind these projects.
The public site intentionally reveals only the parts that need to be public.
Just the work.
Financial clarity for residential communities.
Real-world financial records are rarely clean.
Payments arrive through different channels. Statements use different formats. Utility readings live somewhere else. Reconciliation becomes someone's recurring headache.
Green Ledger is an attempt to turn that mess into a consistent, auditable operational picture.
The goal isn't another spreadsheet.
It's a system that makes the spreadsheet unnecessary.
Demonstrations use synthetic data. No resident or private financial records are exposed here.
From scattered records to structured data.
Statements, messages, exports and other financial inputs can arrive in whatever shape the outside world happens to produce.
Ledger Intake exists to make the first difficult step boring:
Less copying.
Less manual checking.
More time spent on the exceptions that actually need a human.
Small measurements. Useful signals.
Electricity and water consumption become much more useful when they're captured consistently.
Utility Tracker turns readings into a history that can be inspected, compared and acted upon.
No magic.
Just better records.
Let machines handle the repetitive parts.
Some work doesn't need another human staring at it.
Automations connect events, data and actions across the lab — while keeping sensitive systems behind their own boundaries.
The public interface doesn't expose the machinery behind it.
That's intentional.
Computation for the beautiful game.
A smaller experiment in decision systems.
Fixture data, player statistics, constraints and a little obsessive analysis — combined into tools for exploring Fantasy Premier League decisions.
Because not every useful system has to manage money.
The interesting question isn't:
It's:
A local machine can be a development environment, a data processor, an automation engine, a research assistant and a laboratory at the same time.
The constraint is no longer having another SaaS subscription.
It's imagination — and occasionally RAM.
This site is public.
The systems behind it aren't.
Sensitive data, credentials, operational interfaces and internal infrastructure remain separated from the public surface.
Projects shown here use intentionally limited or synthetic information where appropriate.
The principle is simple: