layer 01
Hardware input
Sensors, boards, switches, and the physical constraints that make software honest.
FSR pressure board · Basys3 switches
I build and test hardware-software systems for reliable behavior in the real world.
A systems lab notebook spanning software verification, simulation, embedded engineering, and community technology - designed for the messy path between raw data and dependable behavior.
Focused on software testing, simulation, embedded systems, and community technology.
simulation/evidence traceauto · 1/3
what I build
Three layers, one feedback loop.
The portfolio works best when it shows the whole path from physical input to reliable human action.
layer 02
Software interpretation
Calibration, state machines, debouncing, and API boundaries that turn raw events into decisions.
dead zone · release timing · access rules
layer 03
Human-facing feedback
Interfaces that keep the system state visible without forcing people to chase noise.
calmer cue · enriched workflow payloads
Flagship case study · Simulation trace
KERES turns coordinated simulation into evidence engineers can inspect.
- Problem
- A visual swarm demo could not support controlled engineering comparison by itself.
- System
- Coordination, PX4 control, event accounting, metrics, and replay.
- Boundary
- Simulation prototype—not physical-drone deployment.
7 strategies6 formations417 passing tests
Replay viewtrace running
Abstract scenario01 / 06formation
asset
Current phase: formation.
How I work when reality gets messy
01Prototype under constraints
02Debug before polishing
03Explain tradeoffs clearly
Field context
Useful feedback for real people.
Teaching seniors through Digital Ready Hawaii showed me that technology earns trust when people can understand what it is doing and what to do next.
That lesson guides projects for volunteers, patients, and local communities: expose the system state, reduce noise, and make the next action clear.
Case files
Artifacts over abstractions.
Preview cards show what was built, what kind of evidence exists, and why the work matters.
Evidence is shown as project facts, roles, artifacts, and process notes - not invented impact numbers.
Simulation - Coordination and evidence system
Booz Allen simulation prototype
configcoordinatecontrolrecordreplay
simulation / PX4 / events / reproducible evidence
KERES
A simulation-first multi-drone research platform connecting coordination, PX4 control, experiment records, event accounting, and replay.
Role: Systems Engineer Intern
7 strategies, 6 formations, reproducible run records, 417 passing tests
note: turned a broad swarm concept into software engineers could configure, measure, and inspect
View case studyHardware-software - Calibration file
Hackathon prototype
sensor -> calibration -> cuecentered
L 52%R 48%
RAW pressure / 20 Hz stream / 4 FSR sensors
ReBalance
A balance feedback system using FSR sensors and Web Serial updates to turn noisy pressure data into a readable correction cue.
Role: Hardware/software developer
FSR sensors, Web Serial stream, calibration, feedback UI
note: learned to separate noisy input from readable feedback
View case studyMarketplace - Trust and verification system
Active MVP foundation
teamsponsorverifylistingreview
Marketplace / verification / Supabase / CI gates
Spontus
A college sports sponsorship marketplace built around verified teams, verified sponsors, structured listings, and application workflows.
Role: Co-founder / product engineer
Domain model, verification workflow, Supabase schema, CI/security gates
note: turned marketplace ambiguity into trust, data, and workflow systems
View case studyFPGA - Digital logic file
Course/lab deployment
clk scan / debounced inputcycle
1wait
2press
3release
4update
Cycles 0-9 like a scanned seven-segment display; hover to scrub WAIT -> PRESS -> RELEASE -> UPDATE.
Flip That Digit
A Basys3 game built around OTTER MCU constraints, seven-segment output, and precise debounce/release handling.
Role: Embedded game logic + hardware deployment
SystemVerilog + Assembly on Basys3 / OTTER MCU
note: learned how release timing shapes reliable state transitions
View case studySystemVerilogAssemblyBasys3
Backend - Operations workflow
Nonprofit production contribution
volunteereventroleapi
CRUD / permissions / MongoDB / coordination
Operation Surf
Backend and data workflows for nonprofit operations supporting volunteer coordination, access-aware CRUD, and API-driven workflows.
Role: Backend/API workflow contributor
MongoDB/Mongoose, Next.js, API workflows, permissions
note: learned how backend structure affects real-world coordination
View case studyvolunteer opsMongoDBaccess-aware CRUD
IDE extension - Learning loop
Hackathon prototype
explainquizgradeadapt
local IDE loop / validated output / adaptive engine
Vybe Tutor
A local-first VS Code extension that turns AI-generated code into learning opportunities: explanations, quizzes, and an adaptive engine.
Role: Contributor - adaptive engine & MCP integrations
Gemini-driven explanations, Zod-validated outputs, deterministic adaptive engine, MCP doc-enricher
note: privacy-first grading and deterministic difficulty transitions
View case studyTypeScriptVS Code Extension
Debug log / Failure notes
Raw engineering process stays visible.
A teaser for writing that reads like a lab notebook, not a polished victory lap.
Entry 006 · KERES event ordering
edge caseevent orderregression tests
When a hostile reached the asset during the same simulation step as an interception, the breach still had to count.
01Failure case
Model the edge case where a hostile reaches the asset during the same update as interceptor contact.
02Decision
Make breach and safety accounting run first, then resolve the abstract interception without rewriting the earlier outcome.
03Regression coverage
Lock the rule down with tests for single-contact resolution, sustained contact, separation and re-entry, and same-step breach precedence.