docs: add deployment modes documentation and update plans
Add DEPLOYMENT-MODES.md with canonical mode taxonomy. Update CLI.md, DEVELOPING.md, PRODUCT.md, and SPEC-implementation.md with local_trusted/ authenticated nomenclature. Revise humans-and-permissions plan with Better Auth choice, bootstrap flow, unified invite semantics, and expanded criteria. Add implementation guide and additional plan documents for cursor cloud adapter and deployment auth mode consolidation. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -84,10 +84,12 @@ More detailed task structure TBD.
|
||||
|
||||
## Guidelines
|
||||
|
||||
There are two deployment scenarios that need to be maintained:
|
||||
There are two runtime modes Paperclip must support:
|
||||
|
||||
- a single user, local trusted deployment - this should be easy to install with a single `npx paperclip run` command and the environment is trusted and self-contained on a local machine (e.g. local files, agents, embedded db, easy to use)
|
||||
- multi-user cloud deployment - allows for a hosted deploy (remote deployment, user logins, hosted db, scalable)
|
||||
- `local_trusted` (default): single-user local trusted deployment with no login friction
|
||||
- `authenticated`: login-required mode that supports both private-network and public deployment exposure policies
|
||||
|
||||
Canonical mode design and command expectations live in `doc/DEPLOYMENT-MODES.md`.
|
||||
|
||||
## Further Detail
|
||||
|
||||
|
||||
Reference in New Issue
Block a user