From f4a1c0de3bab901096e8fec37af1899badf29643 Mon Sep 17 00:00:00 2001 From: LucaCappelletti94 Date: Sat, 19 Sep 2026 09:36:58 +0200 Subject: [PATCH] Move R69 to done in the phase table, README and diagram --- README.md | 4 ++-- docs/architecture/architecture-diagram.svg | 2 +- plans/master-implementation-plan.md | 6 +++--- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index fa3456a4..817a90a9 100644 --- a/README.md +++ b/README.md @@ -30,11 +30,11 @@ On the client, a SQLite replica on native and in the browser is read with Diesel ## Where it stands -The plan in `plans/master-implementation-plan.md` tracks 87 phases, 63 done and 24 open. The core is built and proven, and what remains is the last mile around it. +The plan in `plans/master-implementation-plan.md` tracks 87 phases, 64 done and 23 open. The core is built and proven, and what remains is the last mile around it. | Remaining | Phases | |---|---| -| Files in every demo, storage quotas | R69, R87 | +| Storage quotas and deployment ceilings | R87 | | Native unlock gates and the mobile demo build | R51 to R53, R88 | | One page codec, Linux key custody across a reboot | R21, R71 | | Schema majors, shared public store, portability download | R31, R11, R61 | diff --git a/docs/architecture/architecture-diagram.svg b/docs/architecture/architecture-diagram.svg index 046390d6..d90195e3 100644 --- a/docs/architecture/architecture-diagram.svg +++ b/docs/architecture/architecture-diagram.svg @@ -605,7 +605,7 @@ transfers bounded by silence, never by elapsed time. No redirect is followed resolver: a signed URL by default, local bytes when unsent or pinned query-shaped content pins, a sweep that asks the store what it holds, a wipe with the replica - demos driving the content surface: not started, R69 + built: the demos drive the content surface end to end, R69 diff --git a/plans/master-implementation-plan.md b/plans/master-implementation-plan.md index 5a443820..a945abf9 100644 --- a/plans/master-implementation-plan.md +++ b/plans/master-implementation-plan.md @@ -132,6 +132,7 @@ Execution order and nothing else. Status, blockers, landing dates and what each | done | ~~R66~~ | The connetto seam, on R65 | | done | ~~R67~~ | The native file client, on R66 | | done | ~~R68~~ | The browser file client, on R67 | +| done | ~~R69~~ | Files in every demo. Seven pull requests, G first, then A, B and C concurrently, then D and E, then F | | done | ~~R81~~ | Aggregate read time bound | | done | ~~R82~~ | Grouped and re-executed delivery, first of the R30 derivations | | done | ~~R83~~ | The client resting table, on R82 | @@ -149,8 +150,7 @@ Execution order and nothing else. Status, blockers, landing dates and what each | any | R61 | The portability download. Deadline is the first real deployment, the R31 class | | any | R11 | The shared public store. Off the critical path | | any | R31 | Application schema majors. Deadline is the first deployment intending to survive a schema change | -| any | R69 | Files in every demo. Seven pull requests, G first, then A, B and C concurrently, then D and E, then F | -| any | R87 | Storage quotas and deployment ceilings. Needs the file routes in the executable, R69's pull request A | +| any | R87 | Storage quotas and deployment ceilings | | any | R70 | Backup and restore. Steps 1, 3 and 4 wait on nothing. Step 2 waits on R75, whose frontier is what it demonstrates against | | any | R71 | Linux replica-key custody. Independent, and it makes R74's Linux caveat go away | | any | R72 | Clock discipline. Independent, and it absorbs the certificate clock rule R74 states | @@ -4634,7 +4634,7 @@ Storage quotas and the deployment-wide ceilings are NOT in this phase. They are **Status.** NOT STARTED. Raised 2026-09-08 while scoping R66, because the maintainer asked for a deployment-wide maximum and the mechanism turned out to belong in the file server rather than in connetto. The four points the 2026-09-12 review found undefined were decided 2026-09-13 and are recorded under Decided. -**Blocked on** R69's pull request A, which puts the file routes in the shipped executable: until then no deployment serves files, so saturation has nowhere to be observed. R67 and R68 do NOT depend on this phase. +**Blocked on** nothing as of 2026-09-19. The blocker was R69's pull request A, which put the file routes in the shipped executable, and #28 landed it, so a deployment serves files and saturation has somewhere to be observed. R67 and R68 do NOT depend on this phase. ### Purpose