I build working systems from ambiguous intent — and small worlds that make an idea tangible.
About me / Interactive resume · Explore the collection · Enter the Journal Room · Read the philosophy
The diagram follows a scored feedback cycle. Click it to introduce dissent, fail a test, and decide when the work is ready.
Software is one way to think out loud. These experiments let you move a control, disturb a system, and see what answers back.
| Enter an artifact | Follow the question |
|---|---|
| Chasing the Flush | Can you read the woods and catch ten days of Michigan morel season? |
| Pixel Pet | What grows when you care for a small, persistent world? |
| Polycentric Orchestra | What changes when evidence and human acceptance govern the loop? |
| Feedback Knot | What happens when development doubles back on itself? |
| What the Wren Hears | Can you understand a radio signal by playing with its shape? |
Chasing the Flush — a 3D mushroom-foraging game set in a Michigan spring woodland. Sonnet 5.5 handled the coding, testing, and deployment with Opus 5.5 orchestrating; my part was repo/Space setup and a UI walkthrough. Spring is playable; more seasons and species are planned. Explore or customize the source →
Streamlit worlds: Gold Digger · Crucible Dynamic · Tiny Gods · The Turning · AI Think Tank · Synapse · Office Hours.
Community work: Project reoWren explores community-owned reporting and radio-mesh communication. Follow its proof-of-concept development on Patreon.
Crown & Cinder remains in the collection alongside the earlier browser experiments.
The early browser games are still here. Their code was entirely generated by the frontier models available when I made them; I supplied prompts, guidance, and testing. I was the crash test dummy. They preserve what those models could make, the questions I was asking, and the revisions that followed.
I build where real operations meet software: field service, warehouses, accounting, documents, integrations, and the people moving between them.
| System | What it connects |
|---|---|
| KWikSync | Field operations, locations, assets, tasks, evidence, and ServiceNow |
| Q2Q | Accounting, time tracking, service management, fleet, and operational data |
| R.E.P.O. | Receipts and invoices, AI extraction, validation, and human review |
| Warehouse management | Materials, vehicles, facilities, labor, billing, and inventory history |
| Enterprise operations | Dispatch, CRM, routing, workforce coordination, and reporting |
Python · JavaScript · ServiceNow · Quickbase · REST APIs · Docker
Meet the person behind the systems → Archaeology, fieldwork, operations, and AI-assisted software: explore the career connecting them.
The conversation is often the first draft. An observation becomes a question; the question becomes a sketch; the sketch becomes something we can test.
I work with Claude, Codex, Gemini, NotebookLM, Grok, and tools for images, music, research, and implementation. Roles change with the task. A useful collaborator can propose, build, question, or reveal something the others missed.
The responsibilities stay distinct:
- Human direction: purpose, boundaries, taste, and acceptance.
- Generation and criticism: make a proposal, expose assumptions, preserve disagreement.
- Verification: compare the claim with tests, runtime behavior, and user experience.
- Revision: let what happened change what happens next.
Confidence is not evidence. Passing a test does not transfer responsibility to the test. An accepted result can still be reopened when new evidence arrives.
Software is not the only product here. Understanding is.
I am learning the formal language of cybernetics through patterns I first met in practice: feedback, distributed judgment, delayed consequences, and systems that can correct their own mistakes. This is a developing practice, with a notebook to match.
Philosophy · Workflow · Timeline
New field notes · September 30, 2026: Repo Excavations II — When the Map Has to Answer to the Territory follows aging evidence, shared meanings, and Ghost’s archived layers. I Was the Crash Test Dummy records what the model-generated games were exploring.
Can a system preserve a useful minority report? Can an interface teach an idea before naming it? Can environmental sensing help a neighborhood notice its own feedback?
The Journal Room holds the observations, contradictions, and field reports behind the artifacts. Entries can remain a paragraph, become software, or change my mind and stop there.