I'm Gautam, Computer Engineering @ uOttawa. I build software around the assumption that networks drop, APIs die, and hardware misbehaves. Don't take my word for it: flip the UPLINK switch in the corner and watch this page handle its own outage. Try it
This is the real AEGIS pipeline logic: detection → zone rules → state machine → alarm → async uplink, reimplemented in ~150 lines of browser JS. Workers without hard hats trigger a violation when they enter the hazard zone; the relay fires before the voice, exactly like the SCHED_FIFO ordering on the device. Now flip the UPLINK switch above and watch events buffer offline, then flush when the link returns. Nothing in the safety loop notices. Full design decisions in the engineering log. And the switch is not just a toy: turn your wifi off and reload this page. It still loads, and the switch flips itself.
AI drafts your Slack messages; nothing sends until a human approves. Fastify + Cloudflare Workers.
Digital-twin crisis management over 14 live APIs on NATS. Led a team of 4 at uOttaHack; outages degrade, never kill.
Agentic middleware turning natural language into audited action: budgets, approval gates, full transaction log.
Stateful RAG memory across Slack, email, and web. Top 9 at Backboard.io × McHacks.
Offline buffering, graceful degradation, and chaos harnesses go in the initial plan, not the retro.
PROVEN · GK-002 §05: the chaos harness that caught the lossy flushEnrichment and dashboards live upstream. Correctness lives on-device, where the network can't take it away.
PROVEN · GK-002 §02: the voice baked in at build timeApproval gates, audit trails, rollback. Every autonomous system I ship can be stopped, questioned, and reversed.
PROVEN · HyperShift: nothing deploys past the approval gateMock generators, load testers, fault injection, so the stack ships while the Pi is still in the mail.
PROVEN · GK-002 §05: the upper stack shipped before the Pi arrivedBuilt Cadence, a production inventory and rental system, solo, from requirements gathering with non-technical staff to deployed software. Audited and repaired data-integrity failures and automated recurring workflows.
Explained regulated financial products to high-volume customers under strict compliance: daily practice at making complicated things understandable to people who didn't ask for the details.
Data structures & algorithms, databases, software engineering, computer architecture, discrete math, probability & statistics.
Open to co-op placements and internships in systems, infrastructure, and platform engineering. If you're building something that has to survive failure, I want to hear about it. (Email works even during the outage; it's store-and-forward. That's the point.)