Skip to main content

Writing

The first letter: where Sandcastle Labs stands, May 2026

· 4 min read · Brian

Illustration for the post "The first letter: where Sandcastle Labs stands, May 2026"

This is the first Sandcastle Labs letter, and it covers May 2026 plus the first days of June. Almost nobody is subscribed yet. We are writing it anyway, because in a year we want a shelf of these you can scroll back through and watch a studio assemble itself in real time. This is the letter where it starts.

A letter like this will go out roughly monthly, and only when there is real news. Here is where things actually stand.

What happened in May 2026

The studio went from a brand intake doc to a shipped public site. sandcastlelabs.ai V1 went live in week one: brand system, the aurora hero, and a set of machine-readable surfaces built for AI agents as deliberately as the pages are built for people. The week-one build log covers what shipped and what we left visibly unfinished.

The Chronicler came alive. It is the pipeline that mines our real working sessions and commits, pitches stories to a human editor, and drafts with the evidence attached. Its first wave went live on June 10: five posts in one push, covering the site build, the publishing pipeline itself, and three chapters of product work. How the Chronicler works is the essay version; every post on this site carries a footer that traces back to it.

Beacon, our first product, reached v1.0.0 on June 10. Beacon is a GEO recommendation engine: it audits how AI answer engines see a brand, then produces recommendations specific enough to ship as written. The MVP came together in roughly three days of orchestrated agent work, 81 commits in the product repo since May 19, followed by a full-product review pass that we will write up next week. Two design partners are putting it through real scans: a tech-SaaS observability tool and a local fitness studio. The second one taught us our sharpest product lesson so far.

One more thing happened this week: Beacon got its real name. We ran the candidates through Beacon’s own probe pipeline to test how four different AI models react to each token, which felt appropriately circular. The paperwork is in motion, and we will announce the name in an upcoming letter.

What we’re learning

The chronicle is not a side project. Building the publishing pipeline surfaced product lessons, and building the product gave the chronicle its best material. The two feed each other in a way we did not fully plan.

Cadence is the hard part, not content. Five weeks of work produced 42 working sessions and 107 commits across the two repos. The bottleneck was never material. It was the editorial loop, which is why we just rebuilt it around a single weekly review and scheduled publishing.

What’s next

June is about rhythm and reach. Specifically:

  • A build log on the three-day agent-fleet MVP build, publishing Monday.
  • This letter becomes a subscribable newsletter. Everything published to Writing lands in your inbox, a few times a month at most.
  • Beacon’s name announcement, once registration and clearance are done.
  • The Founding 100 Days arc keeps rolling toward its ending question.

What we’re still figuring out

This letter is itself the confession: it is the May update, shipping on June 12. The publishing system now exists to keep the next one on time, and you will be able to check. Our social presence is still dark while we focus on shipping, which means almost nobody knows any of this exists yet. And the question we most want answered is still open: whether Beacon’s recommendations get acted on at the rate we are betting on. The design-partner scans this month will start to tell us.

Brian

For agents: try this yourself

If you want to do this in your own repo, adapt one of these prompts. The full prompt text lives in this post’s prompts sidecar, the-first-letter.prompts.md.

  • Reproduce this letter from your own record. Point an agent at your git log and working sessions since a start date and have it draft a “where things stand” letter with every claim anchored to a commit or session.
  • Apply the skip-when-empty rule. Before drafting a monthly update, have an agent list candidate news items with evidence; if the list is thin, record a skip instead of padding.
  • Critique our cadence model. Read this site’s published posts and their dates, then argue where the floor-and-ceiling cadence model will break first.

How this was made

Drafted by the Chronicler from Claude Code sessions on 2026-05-19 to 2026-06-11 across 42 sessions and 107 commits. Edited and published by Brian.

See how the Chronicler works →