Repository navigation
Closed
Labels
area: repositoryThe repository itself: settings, governance, guidanceThe repository itself: settings, governance, guidancedecisionA decision record (ADR) comes before codeA decision record (ADR) comes before codeneeds leadOnly the project lead can close itOnly the project lead can close it
Milestone
Description
The project lead set the direction on 2026-11-18: this repository becomes a monorepo. Mail is the first module of a suite; a calendar, file storage and bookings follow as modules developed as packages; a mobile app may come later. Today the repository is one package with one Worker and one single-page app, and the feature scope lists calendar, booking and files as phase C, "decided after phase B".
Nothing is moved yet. A change of layout touches every path, every check and several sticky names, so it starts with research and a decision record that the project lead accepts (GOVERNANCE.md).
The decision record must answer
- The layout. Which directories are apps (the mail Worker and its web app, later a mobile app) and which are packages (what mail, a calendar and files would share: sign-in and access, the design components, messages and languages, the storage and logging helpers, the contracts of the API). What stays out of a shared package on purpose.
- What a module is. How a module brings its routes, its rights in the route table, its Durable Object classes and migrations, its screens, its messages and its tests, and how the shell composes them. One Worker for all modules or one for each, and what that means for an installer and for the same-site rule of ADR-0003.
- Sticky names survive the move. Durable Object class names, binding names, migration tags, D1 migration order and R2 keys of an instance that already runs must not change because a file moved.
- The checks keep holding.
copies.json(the seed's paths), the size and lint ratchets, the static checks that read paths, the Cloudflare ledger, the vendored skill hashes, the three test tiers, and the required status checks of themainruleset: each either follows the move in the same change or is listed with what replaces it. - The tooling. pnpm workspaces alone or with a task runner; one lockfile; how versions stay pinned in one place; what CI runs for a change that touches one package.
- Other clients. What a mobile app needs from the API that the web app gets for free today (a session a native app can hold, push), read together with ADR-0005, which already names its first candidate for a native client and the triggers to look again.
- Names. Whether "Podbay" is the suite and mail one module of it, or Podbay stays the mail product inside a suite with another name; this meets the open name review (#4).
- The order. When the move happens relative to the open work (the rules of ADR-0008, snooze and mute, version 0.1), so that no large pull request is open across it, and whether it is one move or several.
- What it does not decide. Building a calendar, files or bookings is not pulled forward by this record (roadmap, section 6).
Done when
- The research is written from current primary sources (pnpm workspaces, Workers with several entry points or service bindings, Durable Object migrations when a class moves), each fact in the ledger where it is a Cloudflare fact.
- The record is proposed, and accepted or changed by the project lead.
- The roadmap and the feature scope say what the accepted record changes.
Metadata
Metadata
Assignees
Labels
area: repositoryThe repository itself: settings, governance, guidanceThe repository itself: settings, governance, guidancedecisionA decision record (ADR) comes before codeA decision record (ADR) comes before codeneeds leadOnly the project lead can close itOnly the project lead can close it
Activity
Madraka commentedon Nov 18, 2026
Data for the areas this record is about was collected on 2026-11-19, from current primary sources, and is in three issues: administration (#87), files (#85), calendar and booking (#86). None of them builds anything.
A proposed order, for the project lead to accept or change
This is the auditor's proposal from what was read; it decides nothing.
What the data changes for this record
Madraka commentedon Nov 18, 2026
Two things from the project lead on 2026-11-19 for this record.
The focus now is the architecture and the shape of the whole, ahead of wording and translation. This record moves up accordingly: it is written next, before the work on the screens' controls.
Languages: some thirty-five are expected later, not two. The record's part on what modules share should therefore answer, for messages and languages:
Nothing of this is built by the record; it is what the layout has to leave room for.
Madraka commentedon Nov 18, 2026
For the "other clients" part of this record. The project lead put the shape forward on 2026-11-19: the web stays on the stack it has; iOS, Android, macOS, Windows and Linux are separate clients, and every client talks to the same JSON API. That is what ADR-0005 already decides (decisions 2 and 4), with Exact as the first candidate for a native client.
Exact says of itself that it changes daily, so it was read again today, two days after ADR-0005. Extracts through a summarising tool: each line is re-read at its source before it enters the record.
Exact on 2026-11-19, against ADR-0005's triggers
srcdocand a sandbox, on the web and nativelysrcdocframe. The author-facingsrcdocand a veto on the guest's navigation are still withheld. Linux has noiframe; Android's has an open defectHost by host, in its own words: the web, macOS and Linux "work"; iOS works on the simulator and on devices; Android and Windows are "early".
What a mail client would lean on:
The fallback picture today: the framework Expo itself documents targets Android, iOS and the web; macOS and Windows are partner projects of React Native with their own versions; Linux is community only.
What this asks of the record
The record does not choose a native technology. It makes the choice possible later, whichever it is:
Madraka commentedon Nov 18, 2026
Two references to the roadmap's sections in issues (this one's "roadmap, section 6", and the same words on #45) now mean section 7, "How the direction changes": #92 gives the shape of the repository a section of its own before it.
Madraka commentedon Nov 18, 2026
Done by #92 (merge b200fd7): ADR-0018, accepted by the project lead on 2026-11-19. Every question of this issue is answered there. The research is from current primary sources, with each Cloudflare fact in the ledger. The roadmap (section 5) and the feature scope say what the accepted record changes. The move itself is in the roadmap's four steps; none of it is done yet.