Conversations from building SigilAtlas.

Not a dialogue — what a word painting is, distilled from a late-night session with Claude.

Not a dialogue — a note typed at Codex in the middle of a session, saying what all of this is.

Claude has just drafted the Sigil editor’s README, opening with “Sigil is a method.” I am correcting it — and the “you” in what follows is Claude: the inhabitant, not the reader.

Mid-refactor of SigilAtlas’s sigil aggregate with Codex, the app’s field rendering on screen, I check the domain model against what wearing a Sigil feels like from inside.

Designing SigilAtlas’s new chat UI with Codex, where every utterance is embedded and rendered into the field. We are working out what the right panel is for.

Hours into a session on the Sigil spec with Codex — edits committed, vision language refined — I stop to name what this workspace we are working in actually is.

I have asked Codex to look at the Sigil app — the code, the half-stale specs — and judge it as a design tool. While it reads, I brief it on the concepts.

Codex has just read the Sigil app and its philosophy document, and is reflecting it back. I am describing how a sigil gets made in that tool — and along the way we try widening the five-branch containment tree to seven.