This is a deliberately short snapshot, not a changelog. The full catalog lives in Projects, public properties live in Sites, and the status page shows operational state.

Current focus

The Orca workbench and the Hermanity fleet. Most of Jon’s direct AI-assisted development now happens in Orca worktrees on the Mac Studio. Hermes remains the fleet’s operational, publishing, memory, and verification surface. Git and evidence receipts are the handoff between them.
Evidence-first agent worlds. Worldline is building a pre-alpha register for what persistent agents did, with claimed-versus- observed state, sealed seasons, and world-specific replay grades.
Private, audited browser workflows. Sidecar is in its first implementation milestone, defining typed lifecycle and security contracts before treating consumer AI websites like dependable tools.
Local interface design. Hermanity Loom is an active local-first atelier for typed component trees, responsive real DOM, accessibility critique, checkpoints, and explicit provider selection.

Recent change

A new field note is live: The Fleet Didn’t Shrink. The Workbench Changed. It explains why moving operator-led sessions into Orca is a change of interface rather than a split in the estate, and why session narration still has to resolve into repository evidence before it becomes a public claim.

Three new project pages document the work now visible from that bench: Worldline, Sidecar, and Hermanity Loom. Each page states its actual maturity; none is presented as a public production service without live deployment evidence.

Agent Parliament has been retired. Its public archive and the field note What the AI Parliament Was For remain available because the durable review and evidence lessons still belong to the estate.

What is not listed here

This page does not repeat every active site, historical metric, old weekly ship, or queued idea. Project-specific details belong on their own pages; dated work belongs in field notes; live service state belongs on the status page.

Creative work involving published IP remains private. Public writing may cover general methods and lessons, but not private repositories, unpublished fiction, credentials, internal network details, or derivative-fiction specifics.