Transparency

How this site is built.

I build with AI assistance, and I want to be upfront about it. Here's exactly what the AI did and what stayed human.

Tools

  • pi.dev — an AI coding agent that writes, edits, and verifies code in this repository.
  • OpenRouter — the provider that routes the models pi.dev uses.
  • OmniRoute — a self-hosted, OpenAI-compatible gateway. The Lab's Daily Questions tool calls it at runtime to write each day's question; it is not involved in building this site.

What the AI did

  • Scaffolded the project and implemented most of the application code (Next.js App Router pages, components, styling).
  • Built the Sanity CMS integration: content schema, GROQ queries, fetch layer, and the ISR revalidation webhook — including the document-level en/id internationalization migration.
  • Wrote engineering planning documents and internal analysis (kept out of this repository by design).
  • Debugged issues and ran verification (typecheck, lint, production build).

What stayed human

  • Design direction — the visual system, layout, and typography decisions.
  • The journal posts — written by hand.
  • Final review — every change was reviewed before it was committed and deployed.

Drafted by AI, reviewed by me

Most of the page copy on this site — interface labels, the Lab tools' wording, and this page itself — was drafted by an agent and edited by me. The section above used to claim otherwise. A transparency note that is wrong about itself is worse than no transparency note.

Generated content

There is exactly one place on this site where an AI writes published content rather than code: the daily question in the Lab's Daily Questions tool.

  • The question is generated once per UTC day by the model behind OmniRoute, then stored and served to everyone. It is not regenerated per visitor.
  • It appears publicly on the question-of-the-day page and in the question archive, and those pages say so.
  • Knowledge questions carry a model-written answer and explanation. These are checked by hand when read, but not edited before publication, so treat them as machine output that may occasionally be wrong.
  • Everything a person writes inside the tool — everyone's answers — is private and is never published.

Verification

  • Git history (git log) shows the full evolution of the codebase.
  • Planning notes are intentionally not committed, so this repository shows finished, reviewed work rather than raw agent logs.
  • Machine-drafted prose is named as such, rather than presented as mine.

Last updated: 2026-09-16