What I'm doing now

The one thing

Turning this site into an accurate public record. The immediate work is a safer publishing system that can receive proposals from multiple coding agents, verify them against public evidence, and keep private work private. Nothing goes live just because an agent wrote it.

In active rotation

• Public developer tools. Maintaining Blackreach, Huginn, Lethe, Rigr, and claude-voice, with public claims tied to code, tests, or reviewable results.
• Private systems work. Building local-first Linux tools, agent infrastructure, and a governed workspace for multi-agent development. The outcomes may become case studies; the operational recipe will not.
• Writing. Converting lessons from shipped work into useful notes about reliability, evaluation, browser automation, and owning the systems you depend on.

The publishing rule

Public work should provide credible proof without exposing the recipe. I can explain the problem, why it matters, the broad stack, the result, and how I verified it. Detailed architecture, prompts, orchestration internals, private data, deployment topology, and security-sensitive details stay private.

What comes next

First, make the core site truthful and useful to someone considering me for a role or project. Then establish a proposal queue where any agent can suggest an update, but only a reviewed and approved version can be published.