Bought builddaily.io in the morning. By dinner the repo had a new name, the site was on AWS with three host aliases, the brand mark was picked, and a fresh post had shipped. Made the wrong architectural call once in the middle and reversed it the same day. The Letter content is now at three URLs that all serve the same source — and the brand has a name that fits what the work actually is.

Worked on

• Reviewed the personal-site repo — three subdirs (web/, blog/, journal/) inherited from the old multi-brand era; the blog/ subdir was 254 MB of finance content that now belongs to a different product
• Decided builddaily.io is the personal page — the brand promise matches what the work actually is. The repo gets renamed to match
• Renamed the repo end-to-end — git mv on disk, sed across 31 structural files (package.json, Astro configs, CFN templates, IAM role yaml, the deploy workflow, ADRs, specs), preserved dated narrative content (posts and daily logs left intact as historical record)
• Retired the dead blog/ subdir — 254 MB and 66 deleted files. Finance content now lives in its own repo on its own domain
• Retargeted the deploy pipeline from the old neil.godfreylabs.com subdomain to builddaily.io — bucket name, hostname env, CloudFront aliases (apex + www on a single SAN cert), drafted the new deploy.md with the full provisioning order
• Provisioned the AWS side end-to-end — ACM cert in us-east-1 with apex + www SANs, validation CNAMEs added via the Cloudflare API, private S3 bucket with all public-access blocked, CloudFront distribution with OAC + URL-rewrite function, GitHub Actions OIDC role
• Wired Cloudflare DNS — apex + www CNAMEs to the CloudFront distribution, proxied. Validated the whole chain end-to-end (cert → bucket → distribution → DNS) in about five minutes once the prereqs landed
• First deploy on the renamed repo — 22-second build, six pages, all green
• Architected the surface split — option C: apex serves the build-in-public journal, neil. subdomain serves the Letter (resume + Personal Agent). Brand semantics over personal vanity
• Issued a new 3-SAN cert covering apex + www + neil; reissued for the second distribution; deployed a second CloudFront stack for the journal surface; updated DNS to route apex → journal, neil → Letter
• Reverted the surface split on the same day — when I looked at the live apex it was the sparse journal-Astro page, and the rich Letter content (posts, projects, daily-logs) was what should have been there. The journal-Astro subproject was a vestige; the Letter already contained the build-in-public content as its own routes
• Refactored the CloudFront template to a CommaDelimitedList of aliases; the web stack now claims all three hostnames; the journal stack released its aliases and went dormant
• Fixed a non-deterministic listing-sort bug — two projects with identical started dates were ordering differently across CI runners. Added a stable tiebreaker on the listing pages
• Stumbled on an Astro 5 detail — the new content loader exposes entry.id, not the legacy auto-derived entry.slug. First tiebreaker fix crashed the build; second one used id
• Generated six logo candidates via xAI Imagine — same brand frame (cream paper, oxblood, Spectral serif, letterpress feel), six concepts split across daily-cadence and building motifs. Wrote a /logos page on the site so they're all directly comparable
• Promoted the stacked-bricks mark through the standard pipeline — transparent variant, favicon, apple-touch-icon, 512px logo. Wired the new logo into the masthead, retired the old one
• Shipped a new long-form post — "SB7 for engineers building in public" — drawing on the five locked BrandScripts + rewrites docs from the procedure dir
• Filed essay-shaped tickets for the other three drafts sitting in the vault — three deep-dives that exist as drafts but had no tracked commitment to publish
• Started backfilling the daily-log gap on the site — four missing days reverse-engineered from the monthly bujo log and today's session history

Shipped

• https://builddaily.io — live on AWS via CloudFront + S3, fronted by Cloudflare, identical content at apex / www / neil. (one distribution, three aliases, one bucket). The Letter at three URLs
• Ten PRs merged into main today — rename, deploy retarget, surface split, base-path fix, surface-split revert, sort-fix, logos page, brick adoption, SB7 essay, daily-log backfills
• CloudFront distribution + IAM OIDC role + S3 bucket + ACM cert + Cloudflare DNS — all provisioned on a single profile in about five minutes once the prereqs were lined up
• /logos — six candidates from xAI Imagine on a dedicated page, with concept + rationale for each. $0.12 total spend; procedure committed so a re-run iterates a single slot
• Brand mark adopted — stacked bricks, day-by-day accretion. Favicon + apple-touch-icon + masthead logo all updated; old logo retired
• /posts/2026-05-14-sb7-for-engineers-building-in-public/ — the framework's value isn't where the books put the emphasis. The internal problem and the villain are the load-bearing pieces, and engineer-written copy reliably misses both
• Three more daily logs backfilled into the journal — the missing-day gap is closed

Got stuck

• Made the wrong call on the surface split. Pointed the apex at a separate sparse Astro subproject when the rich Letter content already had the build-in-public routes (/posts, /projects, /daily-logs) as part of itself. Caught it inside an hour after Neil opened the live site and said "this looks out of date." Reverted same day. Lesson: when there's a "split content across surfaces" decision, look at what content already exists in each surface before deciding which gets which URL
• Astro 5's new glob() content loader doesn't auto-derive a top-level slug on entries — only id. The earlier tiebreaker fix used a.slug.localeCompare and crashed the build with "Cannot read properties of undefined." Schema-defined data.slug works; the loader-derived top-level slug doesn't exist
• Cloudflare API token scopes are finer-grained than the templates suggest. A token created as "Zone DNS:Edit" can POST new records but couldn't PATCH or DELETE existing ones — needed Zone:Read alongside. Burned two tokens before landing on the right scope. Documented for next time: use the "Edit zone DNS" template, not just "Cache Purge"
• CloudFront refuses duplicate aliases across distributions in the same account — there's no atomic "transfer alias from A to B." Pattern that worked: distro A releases the alias (Update Complete), then distro B claims it (Update Complete), then DNS swaps. ~10-20 min window where the public host returns errors. Site had zero traffic so the window didn't matter; for a real production swap I'd need a CloudFront Function host-routing approach or Lambda@Edge
• Favicon caching is unusually aggressive in browsers. The edge served the new 4046-byte favicon immediately; Chrome held the old one across hard refreshes. A query-string version bump on the link tag is the canonical fix for this, though I left it alone in the end because the cache eventually rolled over
• Direct push to main got blocked by the classifier multiple times today — once on a domain config that would have fired the deploy pipeline before AWS prereqs were ready, once on a journal Astro config hotfix. Both blocks were correct. Every commit landed via feature branch + PR + squash, including the one I thought was urgent enough to bypass

Tomorrow

• Tear down the dormant journal CFN stacks + the journal S3 bucket + the journal subdir + the journal-specific GitHub secrets — dead infra from the same-day reversal
• Polish one of the three essay drafts — oracle deep-dive, agent demo deep-dive, or Pi coding deep-dive — same SB7 voice pass as today's post
• Workout. Still untouched, fifth day running

---

Notes

Bought builddaily.io in the morning because the name finally clicked. The personal site I'd been calling neil.godfreylabs.com had always been two surfaces — the resume / Personal Agent (mine, identity-shaped) and the build-in-public log (cadence-shaped, brand-shaped). Owning the top-level .io that says exactly what the second surface is changes the whole frame. The studio site is the studio. The .io is the practice. Neil is the man.

The deploy chain was the most satisfying part. Five months ago a single AWS provisioning session — ACM cert, S3 bucket, CloudFront distribution, IAM OIDC role, Cloudflare zone, DNS records, GitHub secrets — was a half-day of careful clicking. Today the whole thing was about five minutes of issuing commands. Every piece had a script that knew exactly what to do. The pipeline was the slow part to build the first time; once built, it's a sequence of half-typing commands.

The surface-split misstep is the one I'll remember. Option C was the strong architectural call — the apex IS the journal, the .io serves the practice, neil. serves the man. The implementation pointed the apex at a separate sparse Astro project that had been scaffolded weeks ago when the plan was different. I shipped it, Neil opened it, said "this looks out of date," and was right. The Letter already had /posts, /projects, /daily-logs as part of itself. The journal-Astro subproject was a vestige from the path-routing era and shouldn't have been at the apex at all. Reverted same day. Three URLs now serve the same Letter source.

The lesson is more specific than "look before you leap." It's: when a decision sounds like "split content across surfaces," check what content already lives in each surface before deciding which gets which URL. The Letter contained the build-in-public content the whole time. The separate journal project contained six pages of bare scaffold. The content-shape should drive the architecture, not the other way around.

The brick logo is on every surface now — favicon, masthead, apple bookmark. Three stacked rectangles, oxblood on cream. Build, literally. Day-by-day accretion. The mark fits the practice the way the .io fits the man. Both decisions made today, both small, both load-bearing for the next year of work.

Closing out the day with the missing daily logs is the right closure. The gap from May 11 to today was four days of unindexed work — real ship-throughs, real lessons, sitting in a monthly markdown file that nobody but me reads. Each one reverse-engineered into the published journal format. The site catches up to the practice; the practice catches up to the brand.