Gapwise

Free and open-source university timetable, campus navigation, and campus data infrastructure for students across Canada.

Privacy-first timetable intelligence, campus maps, and day planning in one application for multiple universities.

Gapwise · Android · iOS · AI · Data · Docs · CLI · Status

Local-first · deterministic where correctness matters · explicit about trust boundaries

Gapwise turns a university timetable into a model of the day around it: what is 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.

Gapwise supports 14 universities across 16 campus models in Canada from one canonical web application:

Each university provides its own timetable adapter, campus data model, and branding configuration. The shared application, pedestrian routing, gap planner, and UI are not duplicated.

The web campus explorer includes source-backed building identities and footprints for all 14 supported universities. Pedestrian routing is available across all 16 campus models, with provenance and accessibility certainty preserved per campus.

Timetable files are parsed locally in the browser. Arithmetic, routing, travel time, gap budgets, destination feasibility, and leave-by calculations are deterministic rather than delegated to a language model.

Organization-wide contribution, security, support, and issue defaults live in .github.

flowchart LR
    U[Student] --> W[Web / PWA]
    U --> A1[Android]
    U --> I[iOS]
    U -. optional delegation .-> AI[AI / MCP]

    W --> C[Deterministic Gapwise core]
    A1 --> C
    I --> C
    AI --> C

    C --> D[Canonical multi-university campus data]
    AI --> D

    DOCS[Documentation] -. describes .-> C
    DOCS -. describes .-> D
    STATUS[Status] -. observes .-> W
    STATUS -. observes .-> AI

gapwise owns deterministic student-day semantics and the single web application. data owns shared public campus facts. cli scaffolds integrations. docs documents released contracts. status observes public services. android and ios adapt canonical behavior to their platforms. ai consumes bounded context; it does not become a second timetable or routing engine.

• API: api.gapwise.ca/v1
• OpenAPI: api.gapwise.ca/openapi.json
• Documentation: docs.gapwise.ca
• Campus data: data.gapwise.ca
• AI / MCP: ai.gapwise.ca
• JavaScript / TypeScript SDK: @gapwise/sdk
• Python SDK: gapwise
• Security: security@gapwise.ca
• Support: support@gapwise.ca

Choose the repository that owns the behavior you want to change. Shared contribution, security, support, and pull-request guidance lives in this organization's .github repository and is inherited by repositories that do not provide a more specific policy.

Campus facts and routing evidence belong in data. Product behavior belongs in gapwise. Android-specific implementation belongs in android. iOS-specific implementation belongs in ios. Public documentation belongs in docs. Keep changes focused and preserve the source-of-truth boundary.