A follow-up to the previous post about seeding and RNG madness. That work is done, but then I needed to figure out how an author creates tests in the IDE. My first reach was to copy Inform 7, but that doesn't really align with how I see

The whole concept of versioning software that is built using GenAI is that things change fast and in large ways. In the before times, large feature additions would be considered, designed, and took a long time to deliver. With the models progression from Opus 4 in December of '25

Over the last two weeks I have aligned Sharpee with a new parser-IF modeling language called Chord. This effort was not to adhere to one side or the other. It was a true alignment where both sides were required to maintain their "way", be elegant, and in

After the first pass at designing Chord, I followed the same step as I did with Sharpee. I worked with Claude to build first an Author's Guide, then documentation for the Standard Library. The first document used Family Zoo as its spine and although we found a few

Now that version 2.2 of Sharpee is shipped with the website and developer manual updated, I took a swing at developing a more author friendly syntax that compiles to Sharpee. I'm calling it Chord. It's currently implemented in a branch and working with Cloak of

Phrase Algebra Fully Implemented * Sharpee 2.x replaces the entire text-rendering system. Text is no longer a string with embedded formatters; it's a tree of typed Phrase values that defer realization, rendered by one per-locale Assembler at the end of the turn. * The old formatter chain

There is still one glaring weakness in Sharpee directly related to separating logic from text emission. Sharpee is intentionally a developer-first/author-second platform and I've leaned into that design. I often use the words, "The Sharpee Way," when talking to Claude. As an exercise

If you hate GenAI, you probably want to skip this episode, though I would assume anyone reading my blog should already know what I do. Sharpee has been stable-ish for a few months. I bumped it to 1.0 and started revising the repository documentation. It occurred to me