Sparticle Loop field notes from building with agents
← The Loop
· WEEK 31 · 5 min

Building Spectroscope, part 4: the same-day pivot

TL;DR

One project ends and its successor begins inside twenty-four hours. Two jury rounds reject seventy-two name candidates before physics wins, and a six-phase migration flips the repo public, bit-identical and verified from an anonymous account.

Some pivots take a quarter. This one took a day.

git log — two repos, one daystdout
2026-07-19  workshop      fable verification confirms the wave - READY TO MERGE
2026-07-19  new repo      checkpoint: brand home baseline
                          (logo set, one-pager, kanban board, color study)
fig. 01 — The workshop's last commit and the successor's first, twenty-four hours apart.

The same day, the name hunt ran its full arc. Jury round one: thirty-five German-industrial candidates, winner rejected wholesale. Round two: thirty-seven English-creative candidates, rejected too. An interim winner called tracedeck even got its folder renamed before losing to the physics round, where I found the final name: spectroscope, always lowercase, CLI spectro, groupId dev.spectroscope. Availability was checked the same evening: GitHub org free, Maven Central empty, no DNS record on the domains. The naming doc's argument translates to one sentence: a spectroscope reads, from pure light alone, what a star is made of, which is exactly the product's observability stance. Instrument nothing; read the stream. The name says the thesis in one word.

The next day, the flip. The rename sounds cosmetic and was engineered like a migration, because it was one: six phases, script-backed, de-branding the code in five bisectable commits, each one building green against a parity baseline of 527 JUnit and 293 vitest tests. The public history was rewritten so the tree is bit-identical to the private one (same bytes, new name), and the result was verified from an anonymous account to prove nothing personal leaked. The commit that closes the act says it plainly: spectroscope is public. The flip landed, verified anonymously.

Read line by line, the rename is smaller than it sounds and larger in one place: five modules keep their code and change their prefix, one design document finally becomes a module, and an API that had existed only on paper ships as the public surface. forge becomes spectro-core; the fleet design becomes spectro-orchestrator.

the rename mapimage
The forge to spectroscope rename map
fig. 02 — Five modules keep their code and change their prefix; the orchestrator and the public agent surface are the two genuinely new pieces.

What I'd do differently

Sharpen the brief before convening the jury. Round one produced thirty-five serious candidates in a direction that was never going to win, because my "nothing German, be more creative" constraint only arrived as feedback after the round. One sentence of taste, stated up front, would have saved seventy-two names. It took me eleven naming rounds for this very blog to relearn that.