Forward-deployed AI engineer. I sit with the people doing the work, break down what they actually need, and orchestrate teams of AI agents to ship it to production.
AI Solutions Architect at KW Corporation · Founder, CuREOsity Labs · REO Town, Lansing
About me / Interactive resume · Explore the collection · Enter the Journal Room · Read the philosophy
Field → Spec: on site with operators/customers; translate what they say into what they need.
Spec → Agents: decompose into staged work orders; run parallel agent lanes; I hold the context.
Agents → Evidence: nothing ships on the agents’ word — tests, runtime, and users decide.
- KWikSync — ServiceNow Store-certified and deployed in a large enterprise, managing a growing estate of 90,000+ IT and commercial assets, from infrastructure to edge devices.
- Stitch
- Q2Q middleware
- R.E.P.O. — Vision extraction + human review.
I build where real operations meet software: field service, warehouses, accounting, documents, integrations, and the people moving between them.
See the operation · company footprint and project progress
01 · See the footprint |
02 · Follow the work |
Facilities management & site surveys · proven across 2,000+ site surveys and visits
Built to support facilities management through structured site assessments, equipment documentation, photos, and human review. Proven across 2,000+ site surveys and visits, this implementation focuses on IT asset management—from infrastructure to edge devices. The survey approach can be adapted to other facility types and assessment needs.
The map connects the overall footprint to an individual location.
Survey review brings assessment notes, documentation quality, and reviewer feedback together.
The Curator · photo evidence and visual verification
Organized site photos give reviewers a visual record of equipment and conditions.
A closer look at visual verification: zoom into equipment photos, annotate details, and relate the evidence to the asset record.
Under the hood · data synchronization and activity log
A single dashboard for synchronizing operational records into ServiceNow, with per-table controls and progress indicators.
The activity log makes sync progress and outcomes visible.
Stitch |
cuREOsity Labs |
| 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.
"…instead of calling it work, realise it is play." — Alan Watts
Everything above is work in production. Everything below is how I keep up. When a new frontier model arrives, I give it a small, low-stakes world to build and watch what it can actually carry: a simulation, a 3D interface, a brain made of a few wires. These are toys, but the habit behind them is the same one I bring to business systems: learn exactly where the technology stands before trusting it with a warehouse, a field team, or a small business's books.
Move a control, disturb a system, and see what answers back.
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 →
Attention Is All You Need · Source |
The Chemical Basis of Morphogenesis · The shelf |
8.5 Ball × 2 · ChatGPT’s |
Rubik’s Cube × 3 · GPT-5.6 Sol’s |
Intelligence Explosion |
Gold Digger |
|
Pixel Pet × 2 · The original |
Crucible Dynamic |
Wind-Up Minds · Vehicles · Worm · Network |
|
| More to explore | Follow the question |
|---|---|
| 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? |
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.
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.
The diagram follows a scored feedback cycle. Click it to introduce dissent, fail a test, and decide when the work is ready.
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.























