I study Computer Science at the University of Toronto Mississauga, with a strong interest in information security, mathematics, systems, formal reasoning, and software architecture.

My work is centered on software where correctness and trust boundaries matter: deterministic planning and routing, source-backed real-world data, privacy-preserving application design, APIs and SDKs, native clients, developer tooling, and infrastructure.

I prefer systems with explicit contracts, conservative failure modes, clear ownership of truth, visible uncertainty, and privacy and security built into the architecture rather than added afterward.

Free and open-source multi-university timetable, campus navigation, and student planning infrastructure.

I created Gapwise around a simple problem: a university timetable tells you when class happens, but not how to use the time around it.

Gapwise turns a schedule into a campus-aware model of the day: what comes next, how much usable time exists between classes, where a student can realistically go, when they need to leave, and how certain the underlying campus information is.

It is one shared platform supporting eleven Canadian universities:

• University of Toronto — Mississauga, St. George, and Scarborough
• Carleton University
• Toronto Metropolitan University
• Queen’s University
• Wilfrid Laurier University
• York University
• McMaster University
• Western University
• University of Guelph
• University of Ottawa (uOttawa)
• Brock University

Each university edition uses its own timetable adapter, campus data, building and entrance context, routing graph, terminology, branding, and import guidance while sharing one canonical application and deterministic planning core.

• local-first, university-aware timetable import and parsing
• gap detection and usable-time calculations
• deterministic leave-by and walking-time planning
• source-backed campus maps, building data, entrances, and pedestrian routing
• canonical multi-university campus data with provenance and validation
• public API, OpenAPI specification, TypeScript and Python SDKs
• MCP / AI tooling that understands every supported university
• native Android and iOS clients
• public documentation, contribution tooling, SEO/discovery surfaces, and service monitoring

• App: gapwise.ca
• Public API: api.gapwise.ca/v1
• OpenAPI: api.gapwise.ca/openapi.json
• Developer docs: docs.gapwise.ca
• Campus data: data.gapwise.ca
• AI / MCP: ai.gapwise.ca
• Service status: status.gapwise.ca

The same supported-university model is carried through the app, campus data, timetable adapters, routing, API, OpenAPI, SDKs, MCP, AI, documentation, status monitoring, SEO, and machine-readable discovery surfaces.

The architecture follows one rule:

Canonical facts and deterministic calculations have an owner. Interfaces consume those contracts instead of inventing parallel truth.

TypeScript · JavaScript · Python · Kotlin · Swift · SQL · Bash

React · TanStack · MapLibre · Supabase · Bun · Vercel · Cloudflare · Resend · OpenAPI · MCP · Jetpack Compose · SwiftUI · PostgreSQL · GitHub Actions · Linux

• explicit security and trust boundaries
• deterministic behavior where correctness matters
• clear provenance and uncertainty for real-world data
• local-first behavior before requiring accounts or cloud state
• stable public interfaces and versioned contracts
• maintainable multi-platform architecture
• accessible interfaces that do not sacrifice technical rigor
• failures that are visible and honest rather than silently guessed around

My broader interests include computer science, information security, mathematics, research, technical writing, and software tooling.