Auto Build Log

Auto Build Log is the automation system behind my own developer portfolio at seannam.com. It is not a product for other people to run; it is a bespoke pipeline wired to one site, one GitHub account, and one person’s publishing taste. The system includes five distinct phases: Scout (discovery), Draft (AI enrichment), Review (human approval), Shipping (PR generation), and Live (published state).

The architecture includes worker-based job processing for enrichment and publishing, admin surfaces for bulk operations across every phase, and cascade cleanup that retires pipeline artifacts when builds are archived or repositories are ignored. Phase transitions support both forward progression and selective back-edges for iteration.

The enricher agent validates generated drafts against a schema, retries malformed outputs up to a cap, and forces tool invocation when models fail to call the record_draft function. The system maintains audit history through activity rows and preserves failed jobs for forensic review while filtering them from active admin surfaces.

Why

Maintaining my own portfolio by hand became impractical once I was shipping frequently. This system automates the tedious parts (scanning for new projects, drafting descriptions, formatting) while preserving my judgment at the approval gate. The goal was to eliminate manual portfolio updates for one specific site, mine, without sacrificing editorial control.

How

The system is built on a PostgreSQL schema tracking builds, proposals, jobs, and activity. Worker processes claim jobs from a queue and invoke specialized handlers for enrichment, detection, and publishing. The enricher communicates with LLM providers through a unified adapter layer that supports both OpenAI-compatible and Anthropic APIs, with model floor constraints and forced tool choice as guardrails. Admin pages are built with Next.js and expose bulk actions, keyboard shortcuts, and selection UX across every phase table. Phase transitions write activity rows that feed a phase-derivation function, enabling back-edges like Draft-to-Scout and Review-to-Draft without corrupting the forward pipeline.