BUILD JOURNAL

The build journal

These are the 276 days of the build register written as a sequence of decisions, with the most recent first. Dates marked ~ are approximate.

OCT 12

CareerHub — a job search run like a sales pipelinePRIVATE

A local-only pipeline for my own job hunt: ingest postings, score them, draft outreach, and a human Approve on every send. The first three commits were the spec, the decision log, and a review pass, before any code. 1,352 commits across 15 active days by Oct 29.

SEP 4

AgentWrangler goes publicLIVE

First release on GitHub (Apache-2.0) and npm the same day. The public repo (a placeholder since Aug 20) now carries a curated export tree, not the private history, and every later update ships as a gated export PR.

AUG 21

AgentWrangler — first commit, offline

A local dashboard for Claude Code token spend, built on a private repo that never leaves the machine. By Oct 21 that repo held 3,686 commits across 57 active days.

AUG 13

SecuritySalesHub — a multi-vendor restack beginsIN PROGRESS

GridSignals, generalized: pre-sales signal intelligence across energy, financial services, and healthcare, recommending security products from 47 vendors instead of one. A two-hop event → capability → product path keeps every suggestion auditable. Still building; deploy not yet wired.

AUG 11

Seller-Admin-Tools publishedPUBLISHED

An offline, deterministic toolkit that turns a weekly CRM export into the forecast narratives, QBR decks, and account plans a seller builds by hand — adapted from an enterprise security-sales methodology. On-screen numbers and the exported decks cannot disagree. 72 commits · 10 PRs in 3 days.

AUG 11

GridSignals publishedPUBLISHED

Turns the public record around 172 US energy companies into scored, sourced signal cards, mapping regulatory and incident events to Microsoft security products. Stdlib-only pipeline, 84-module test suite, honest empty states. 337 commits · 115 PRs in 9 days.

AUG 10

Pipeline-Hygiene publishedPUBLISHED

A read-only sales-pipeline inspection agent: eleven deterministic hygiene rules flag stale, slipped, and mis-forecast deals before the forecast call, each flag tracing to a versioned threshold. Agents inspect, people sell. 137 commits · 37 PRs across 4 active days.

JUN 11

ReadySetBind live in pilot — and this register goes up

Eight products, two live, one published, one report delivered. The scrapped ones count as much as the launches.

JUN 9

StackBadger publishedPUBLISHED

A pentest harness extracted from TariffRefunded, scrubbed, and released. The extract → scrub → review playbook becomes repeatable.

MAY 26

ReadySetBind — first commitLIVE · PILOT

813 commits and 243 PRs in the first 17 days. Day one shipped the end of the pipeline before most of the middle existed.

MAY 20

DealFinder — a seven-day MVP, then a pausePAUSED

Ideated inside the SafeCircleOps build, three days in. 130 commits to a working real-estate intelligence MVP, then paused unlaunched.

MAY 17

SafeCircleOps — a five-day sprint for a friendPRIVATE

140 commits in 5 days. Local-only, evidence-grade, deliberately unpublished. Report delivered to law enforcement.

~MAY 6

CyberReadyAI paused with intentPAUSED

Near-launch after 747 commits. The project that taught me to audit my own guardrails.

~APR 16

TariffRefunded beginsLIVE

The tariff rate monitor PRD dies; refund recovery for SMB importers replaces it, racing a 180-day protest window.

~APR 8

PartMatch scrapped at PRD reviewSCRAPPED

Adversarial review said “spike first.” Stopping it cost a review session instead of a build month.

MAR 20

RiskScanAI shelved — and forked the same daySHELVED

The honest read: nobody pays for an AI-interview risk assessment. Everything carried directly into CyberReadyAI on the day of the last commit.

~MAR 15

PreCloseIntel — full PRD, then a pausePAUSED

First run of the 7-phase Idea → Build framework. The PRD survived; the build slot went elsewhere.

FEB 27

RiskScanAI — first commit lands on GitHub

First product, first AI-agent workflow. 160 commits over the next 15 active days.

~JAN 27

RiskScanAI begins — before the repo

The first build starts off GitHub: landing pages and product shaping ahead of any version control.

Trust belongs in the schema, not the application.
The operating principle behind every project here. A rule the database enforces can't be forgotten in a hurry. Constraints, denied-by-default access, append-only logs — the controls that hold are the ones the system won't run without.