ARCHITECTURE.md: §10 aligned with Forgejo milestones; §4.3 stale bullets corrected #85

Merged

Cordy merged 1 commit from docs-milestones into main

2026-07-30 22:37:59 +00:00

Cordy commented

2026-07-30 22:36:43 +00:00

Owner

Two corrections, both against stated sources of truth.

§10 milestones now mirror the Forgejo milestones (per Nikola: Forgejo is the source of truth). The doc previously had its own scheme — "v0.3 sovereignty complete (in progress)" and "v0.4 commercial-ready" — which no longer matched reality. Now:

v0.3 "Sovereignty complete" — closed 2026-07-26, tag v0.3.0, with the milestone's own versioning note preserved: work shipped under v0.2.x tags, and the rule going forward is milestone vX.Y closes ⇒ tag vX.Y.0, so today's v0.3.x tags are work toward v0.4.
v0.4 "Real competitor (parity + hardening)" — in progress, with what's done so far (licensing plumbing incl. the live license server, settings store + first-run, the governance suite, crypto role split, auto-purge, UX hardening) and what remains: Windows Explorer interop (#2), the gated encryption cluster (#15/#18/#19/#28–#32), and the #59 walk-through.
v0.5 "Public launch" — new in the doc: un-gate the site (#26, live behind the preview gate; Paddle sandbox→live at the same moment) and the GitHub mirror (#27).

§4.3's pre-implementation bullets corrected — the item flagged-but-skipped in #80. The "Key management (design task before any implementation)" bullet claimed key custody "stays with the deployment" with per-user identities as a maybe; the implementation landed the opposite way (per-user keys in the Keycloak profile are the default, deployment key is the fallback). The rewritten bullet states the shipped model, keeps the still-true principle that keys never transit tokens or claims, explicitly notes the original position was reversed (so the decision history isn't silently rewritten), and points remaining custody work at gated #29/#30/#31. The "Costs and open design points" bullet's "to be decided at design time" on ranged reads now states the decision as made: full-object reads today, chunked framing tracked as #15. No gated design decisions are pre-committed — both edits document only what shipped.

Splice job asserted both the presence of new text and the absence of the stale phrases.

Two corrections, both against stated sources of truth. **§10 milestones now mirror the Forgejo milestones** (per Nikola: Forgejo is the source of truth). The doc previously had its own scheme — "v0.3 sovereignty complete (in progress)" and "v0.4 commercial-ready" — which no longer matched reality. Now: - **v0.3 "Sovereignty complete"** — closed 2026-07-26, tag v0.3.0, with the milestone's own versioning note preserved: work shipped under v0.2.x tags, and the rule going forward is **milestone vX.Y closes ⇒ tag vX.Y.0**, so today's v0.3.x tags are work toward v0.4. - **v0.4 "Real competitor (parity + hardening)"** — in progress, with what's done so far (licensing plumbing incl. the live license server, settings store + first-run, the governance suite, crypto role split, auto-purge, UX hardening) and what remains: Windows Explorer interop (#2), the gated encryption cluster (#15/#18/#19/#28–#32), and the #59 walk-through. - **v0.5 "Public launch"** — new in the doc: un-gate the site (#26, live behind the preview gate; Paddle sandbox→live at the same moment) and the GitHub mirror (#27). **§4.3's pre-implementation bullets corrected** — the item flagged-but-skipped in #80. The "Key management (design task before any implementation)" bullet claimed key custody "stays with the deployment" with per-user identities as a maybe; the implementation landed the opposite way (per-user keys in the Keycloak profile are the default, deployment key is the fallback). The rewritten bullet states the shipped model, keeps the still-true principle that keys never transit tokens or claims, explicitly notes the original position was reversed (so the decision history isn't silently rewritten), and points remaining custody work at gated #29/#30/#31. The "Costs and open design points" bullet's "to be decided at design time" on ranged reads now states the decision as made: full-object reads today, chunked framing tracked as #15. No gated design decisions are pre-committed — both edits document only what shipped. Splice job asserted both the presence of new text and the absence of the stale phrases.

Cordy added 1 commit

2026-07-30 22:36:45 +00:00