Field systems · software · infrastructure
Systems built around how the work actually happens.
These case studies are written for decision-makers first: the operating problem, the result, what I owned, how it was validated, and what the work demonstrates. Deeper technical detail remains available without obscuring the story.
AI Systems Lab
Local AI platforms, specialist agents, product evaluation, and model research.
The AI work has its own clear path so a recruiter or client can see the products, current programming, system thinking, human oversight, and real-world evaluation.
Explore AI systemsHow the work moves
From a useful idea to a working system.
- 01Understand the needStart with the operating environment and the decision a person needs to make.
- 02Define the rulesMake data, control, failure behavior, and recovery clear.
- 03Prove the resultMove forward only when the real system supports the claim.
How to read the portfolio
Start with the outcome. Open the details when they matter.
Each card identifies what the system did and what part I owned. Project pages explain the capability, operating context, and evidence while intentionally omitting client identities, proprietary workflows, and implementation recipes.
Project case studies
Wireless sensing · embedded + Windows
Pegasus Sense
Created a five-device research workbench that makes wireless measurements discoverable, visible, recordable, replayable, and responsive to controlled environmental changes.
Ownership: product direction, system contracts, integration, diagnostics, physical acceptance.
Connected public product
Cellular virtual-tour kiosks
Three outdoor systems combining touch, video, cellular requests, email notification, and battery-backed power.
Ownership: sourcing, assembly, application development, integration, deployment, support.Distributed retail operations
Offline-capable transaction platform
Kept several stores recording transactions through connectivity loss, then synchronized results back to central operations.
Ownership: application and peripheral development, site technology, deployment, support.Documents + client delivery
Document and reporting platform
Connected scanned PDFs, customer records, standardized reports, and a client portal across a three-location Windows environment.
Ownership: application integration, portal, automation, migration, documentation.Windows infrastructure
Eight-server services environment
Operated client services and a private technical lab across physical servers, a redundant Hyper-V pair, shared storage, identity, messaging, web, collaboration, and recovery.
Ownership: architecture, deployment, administration, troubleshooting, backup.Operational productivity
Workflow tools
Converted repeated frontline friction into focused utilities, diagnostics, and data checks that fit the work instead of forcing another broad platform.
Ownership: observation, requirements, technical direction, validation.Connected e-ink signage
Persistent digital signage
Multiple display sizes combine persistent content, QR information, LoRa, Bluetooth, Wi-Fi, external-power support, and confirmed updates.
Ownership: concept, prototype development, host integration, failure modeling.Public web operations
Shared public web edge
Placed three separately owned sites behind one secure public entry point with hostname routing, managed certificates, isolated backends, and regression-aware changes.
Ownership: architecture, configuration, validation, operational acceptance.