Adventure Radar
A free prompt builder and trip-cost reality check for people who care more about a great adventure than a random cheap fare.
Build faster
Systems built to solve real operating problems — with active engineering work clearly separated from production-proven builds.
A role-based operating layer for leasing, maintenance, accounting, and admin — built on top of a shared operational data foundation.
Captured app views · Today & Maintenance
The collection
Browse the projects, then open a build for the problem, approach, and evidence.
A free prompt builder and trip-cost reality check for people who care more about a great adventure than a random cheap fare.
A point-in-time market database built to notice local change before headline statistics make it obvious.
I stopped opening the CRM from the truck. Now a screenshot of the text thread writes the note and the task.
An accounting automation system for reconciliation, invoice workflows, duplicate protection, operator follow-up, and decision-level observability.
Turned 3-5 hours of copy-pasting numbers into a broker's PDF in, full 15-tab live pro forma out.
A role-based operating layer for leasing, maintenance, accounting, and admin — built on top of a shared operational data foundation.
Captured app views · Today & Maintenance
06 projects · Updated Sep 2026
Now building
Current systems and engineering work. Short status notes here; deeper write-ups only when a build earns one.
Architecture, PostgreSQL, security boundaries, financial reconciliation, and evidence-backed implementation gates.
Current focus · Financial core + trust boundariesRead the evidence note →Mobile-first workspaces that turn leasing, maintenance, accounting, and admin activity into the right next action.
Current focus · Daily work + cross-system evidenceRead the product note →Reconciliation, invoice intake, duplicate protection, bank evidence, write controls, and a decision-level Flight Recorder that explains what Books saw, decided, attempted, skipped, and verified.
Current focus · Reconciliation + observability + safe writesRead the write-safety note →Recent milestones
System milestones from source-repository history — not website edits or simulated live status.
A deterministic posting-manifest builder and expected-vs-observed comparator were implemented without persistence or production financial tables.
Follow the system →Sent writes that time out or return unreadable responses now stay not confirmed instead of being reported as unchanged or automatically retried.
Follow the system →A semantic activity history was added to show what the system observed, decided, attempted, and verified without becoming the accounting source of truth.
Follow the system →Notes from the bench
A green test proves something specific happened in a controlled environment. It does not prove a design was approved, a deployment gate passed, or production is behaving the same way.
Read the note →A write can leave your system, time out, and still succeed. Treating that as a failure can create the duplicate you were trying to prevent.
Read the note →Leasing, maintenance, accounting, and admin all touch the same operation. That does not mean they should see the same software.
Read the note →