docs: clarify mobile v1 scope and trading control ownership

This commit is contained in:
Saravana Achu Mac 2026-04-04 02:28:21 -07:00
parent 401671a5eb
commit c747fe82fe
2 changed files with 13 additions and 2 deletions

View File

@ -199,7 +199,7 @@ Platform-service owns:
- product-aware auth primitives
- feature flags
- kill switch and maintenance controls
- product-level kill switch and maintenance controls
- telemetry ingestion and diagnostics hooks
- shared product metadata and cross-product policy controls
@ -208,6 +208,9 @@ Trading backend owns:
- trading state authority
- orders, positions, lifecycle, and reconciliation authority
- runtime loop controls
- global trade halt
- tenant-level trade disable
- profile-level trade disable
- trading admin operations and domain audit events
Web and mobile own:
@ -234,6 +237,12 @@ Web and mobile own:
- backend loop safety gates
- clear UX behavior when the product is disabled or degraded
Ownership model:
- platform-service owns product accessibility controls such as product-wide kill switch and maintenance state
- trading backend owns trading-behavior controls such as global trade halt, tenant-level disable, profile-level disable, and loop-level execution safety
- web and mobile render these states and expose only authorized actions; they do not become the enforcement authority
### 9.3 Runtime observability
- health, loop status, reconciliation status, and operational warnings
@ -274,9 +283,10 @@ Foundation release scope:
Product v1 scope:
- authenticated web dashboard
- authenticated mobile monitor surface
- authenticated mobile monitor and incident-intervention surface
- backend authority for trading state and controls
- overview, alerts, positions, history, and runtime controls
- limited, explicitly approved mobile interventions such as pause/resume and other tightly scoped safety actions
Deferred:

View File

@ -285,6 +285,7 @@ Build mobile as a real ecosystem surface, not a mock UI shell.
- recent history
- settings and sign out
- safe operator controls limited to explicitly approved actions
- mobile is monitor-first, but not monitor-only
### Do not do in mobile v1