Roadmap

What we are building.
And in what order.

Every product keeps its roadmap in its own repository and publishes a public version from it. This page collects them: status and progress come straight from the work, not from a slide deck.

new-campus

new-campus

v1 · as of 2026-09-08

Foundation

shipped

A repo lanes can work in.

Local environment, database core with RLS, auth, identity, rooms — and the skizze transplant.

2 of 2 done
  • Core packagesdone

    Database, auth, identity, rooms, local environment.

  • skizze transplantdone

    The blueprint workshop moves in from the monorepo; 81 e2e specs green.

Booking

shipped

A cell that books a monastery.

Occupancy plan, booking kernel, approval flow, demo data, public site and 3D tour.

2 of 2 done
  • Booking and occupancy plandone

    Booking kernel, approval flow, per-room week grid, demo week.

  • Public site and 3D tourdone

    The campus page and the tour, bilingual.

Milestones

undatedBooking demo for the clientdraft

Blueprint and access

now

A blueprint every cell can apply.

Catalog as git data, reference tables, roles, cookie sessions, portal sign-in, staging cell.

4 of 4 done
  • Catalog as git datadone

    Versioned package, reference tables, hydration at boot.

  • Blueprint roles and cookie sessionsdone

    blueprint_members, Better-Auth wiring, provider port, new e2e suite.

  • Portal sign-indone

    Sign-in, password reset and the six procedures that had no screens.

  • Staging celldone

    Namespace, CNPG cluster, deploy workflow, OTel.

Operations

next

A cell that can be run.

Observability, backups, promotion to production by PR, runbooks.

0 of 1 done
  • Operations: promotion, backups, runbooksproposed

    Promote production by PR, backup and restore rehearsed.

Second cell

later

A product rather than a project.

AMD or Fresenius as the second institution; the blueprint proves itself on two applications.

0 of 1 done
  • Second cellproposed

    A second institution on the same blueprint.

Live data

later

Real users in the cell.

People migration and credentials — once the data-processing agreement and client sign-off exist.

0 of 1 done
  • People migrationin progress

    Subject map, credential issuance, invite path.

Milestones

undatedData-processing agreement signeddraft