Elijah/newdrive
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update architecture baseline for sync, sharing, and gateways
All checks were successful
CI / Backend (push) Successful in 26s
Details
CI / Frontend (push) Successful in 11s
Details
CI / Contracts and repository policy (push) Successful in 4s
Details
CI / Container (push) Successful in 27s
Details

Browse source
This commit is contained in:
Elijah 2026-07-16 18:40:12 -07:00
parent 9e01df5d64
commit 099c53badf
7 changed files with 200 additions and 102 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/architecture.md
View file

@ -16,9 +16,18 @@ Transport code handles protocol concerns only. Application services own transact
No authoritative state lives only in memory. Upload sessions, commit intents, jobs, leases, and cursors are persisted in PostgreSQL. Committed blobs are immutable and become visible only after storage promotion and metadata commit.
## Sync-ready server contract
The server exposes neutral file and change primitives, not client sync modes. A consumer obtains a start cursor, recursively enumerates stable node/parent IDs, then replays the durable change feed until caught up. Events carry resulting state or tombstones and are safe to process more than once. See ADR-0008.
Node revision covers all meaningful mutations; content revision and SHA-256 distinguish content changes from rename, move, favorite, or trash metadata changes. Persistent idempotency and authenticated client attribution apply to every transport.
## External protocols
REST and application services are canonical. A future WebDAV gateway translates protocol requests into those services, and a native rclone backend may consume REST directly. Neither may touch managed object storage or repository tables. Rsync server access is not planned. See ADR-0009.
## Frontend
Each feature owns its routes, API hooks, components, state, and tests. Cross-feature access goes through a small public entrypoint. Server state stays in TanStack Query and local UI state remains close to the component or feature that owns it.
Preview rendering is capability-driven and lazy-loaded. Adding a format must not require editing the file manager.