Repository navigation
docs(adr): ADR-0018 proposes one workspace, one Worker and many modules - #92
Conversation
Issue #57. The repository becomes a pnpm workspace of apps, modules and shared packages; every module runs in the one Worker, under one route table and one guard; nothing an installed instance depends on changes name. The record also says what any client other than the web app needs, and the form messages keep so that some thirty-five languages fit later. It builds nothing. Status: Proposed, for the project lead. Thirteen Cloudflare facts it relies on are in the ledger, read on 2026-11-19; the alarms and request-body entries are brought up to their pages' current dates. The roadmap records today's reading of ADR-0005's triggers: none is met. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Madraka <8898640+Madraka@users.noreply.github.com>
Audit at 0caeddf: six additions, then it is ready for the project leadThis is a record for the lead to accept, so the audit is of what it says and what it leaves unsaid, not a verdict on the direction. What I checked and found as written
To add before the lead reads it1. Whether a module can be off. The lead's word for the suite was modular. The record says how a module is written and never whether an instance may run mail without the calendar. That decides things the layout must leave room for: a switch for each module, what the route table and the app's shell do with a module that is off, whether a module's Durable Object classes and tables exist in an instance that never turns it on, and what an installer is told (#44). The assistant and the MCP endpoint are already optional and off by default; say whether a module follows that pattern. 2. A module is two programs in one directory. Its Worker side runs in the Workers runtime and its app side in a browser. Decision 2 puts both in 3. One sequence of D1 migrations from several modules. Decision 1 says each module brings its migrations "in the one sequence of the one database". Say who owns the order: where the one list lives, how two modules developed side by side do not take the same place in it, and that a migration once applied never moves. 4. Another hostname is not another Worker. Decision 9 serves uploaded content from a hostname of its own, and the triggers list "a module must be served from another hostname" as a reason to look again at one Worker. The platform's page says "You can add multiple Custom Domains" to one Worker. So the files module's hostname does not by itself ask for a second Worker; what it asks for is that the Worker answers differently by hostname, and that the guard and the content policy know which one a request came in on. Reword the trigger and add the fact to the ledger. 5. One version, one release. One Worker means the suite is released as one thing: a module cannot ship without the others. Say so in the consequences, with #21, since "a module needs its own schedule" is already a trigger. 6. Small things.
For the lead, not for the builderThree choices in this record are the ones to look at before accepting it, because they are the hardest to change later:
The checks were still running when I read this. With the additions made and the checks green, this merges as Proposed, and its status changes only on the lead's word. |
|
A seventh addition, from measuring what the layout would move (on
Of the 21 files in 7. Where a module's contract lives. Decision 2 names The figures are also the size of the move for the lead: about 230 files of code and 115 of tests change their path. |
…tries, one migration order The audit of #92 asked for seven additions: - a module other than mail can be off, as the assistant and MCP are, and what the route table, the shell and the data do then; - a module has three entries, worker/, app/ and shared/, and worker/ and app/ never import each other; - where a module's contract and the pure functions both sides run live: its shared/ entry, with packages/contract holding only what every module has in common; - who owns the one sequence of D1 migrations, and that an applied one never moves; - that another hostname is not another Worker, with what answering by hostname asks of the guard and the content policy; - that one Worker is one version and one release (#21); - the AI binding among the names that stay, and whose a module's things are, with authorize the one function. Two facts are added to the ledger: several custom domains on one Worker, and how D1 orders migrations. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Madraka <8898640+Madraka@users.noreply.github.com>
|
Answer to the audit at 0caeddf, and to the second comment. One new commit, ae49b39.
|
|
audit: pass as a proposed record, once the required checks are green Read at ae49b39, the one new commit. All seven additions are in, and each says what was asked:
It merges as Proposed. Its status changes only on the project lead's word, and I am asking for it. Merge with a merge commit when the checks are green; name both runs of the branch. |
|
The project lead accepted this record on 2026-11-19, as it stands at ae49b39. Asked in the auditor's session "ADR-0018'i (tek Worker, modüller, paketler) bu haliyle kabul ediyor musun?", the answer was: "Kabul ediyorum". For the builder: this is the lead's word relayed by the auditor. As with ADR-0017, take it first-hand in your own session if the record needs that, then set the status to Accepted with the date and "Decided by" in this pull request, in a commit of its own that changes nothing else of the record, and update the line in |
The project lead accepted ADR-0018 as it stood at ae49b39, on 2026-11-19. Its status, date and "Decided by" say so, and its decision's heading loses "(proposed)"; nothing else of its text changes. The ADR index lists it as accepted, the roadmap gets a section on the shape of the repository with the order of the move, and the feature scope says phase C has room as modules. The phase table is unchanged: the record moves no phase forward. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Madraka <8898640+Madraka@users.noreply.github.com>
|
audit: pass, once the required checks are green Read at 62d5e5a, the acceptance commit. It sets the status to Accepted with the date and who decided, takes "(proposed)" off the heading of the decision as the other accepted records have it, and changes no other word of the record. The lead's acceptance was taken first-hand in the builder's session and was also given in mine; the two agree. The index of records says Accepted. The roadmap has a section of its own for the shape of the repository, with the four steps and the place of the file moves after #84, #82 and #83; its later sections move down by one, and no file refers to them by number. The feature scope gains one sentence and its phase table is as it was. From here ADR-0018 is not edited: a change to it is a new record. Merge with a merge commit, and name the branch's three runs. Then close #57 by this pull request. |
T9, issue #57. A decision record, Proposed, for the project lead to accept or change. It builds nothing and moves no file.
What it proposes, in one line each; the record has the reasons and the facts:
apps/(what is deployed: firstapps/podbay),modules/(product areas: firstmodules/mail) andpackages/(contract,auth,ui,i18n,platform). A module never imports another module's inside.MailboxDO,EmailAgent, the six bindings (AIincluded), the tagsv1andv2, the D1 order and the R2 key shapes. No rename, transfer or delete migration, and no move toexports.pins.tsand the licence check read every package; today they read the root only.packages/contract.dirfrom a table of languages, a "reviewed" mark per language, and codes for the Worker's errors. Nothing is built.How the facts were read
node:dns, the migration rules, static assets, the test integration's auxiliary Workers, and service bindings.runtime.durable_objects.alarmsandlimit.workers.request_bodyentries are updated to their pages' current dates.Not verified, and said so in the record
pnpm licenses listcovers workspace packages without-r.Checks.
pnpm checkpassed locally, with 21 static checks (the ledger included) and 953 unit tests. No code changed.The roadmap and the feature scope change only when the lead has accepted the record, as #57 asks.
🤖 Generated with Claude Code