57 lines
2.0 KiB
Markdown
57 lines
2.0 KiB
Markdown
# NuQloud V1 Feature Scope
|
|
|
|
This document locks the first launch scope for `nuqloud-bootstrap`.
|
|
|
|
Companion function list: `docs/product/v1-functions.md`.
|
|
|
|
## 1) Powered mode (`SC_MODE=powered`) defaults
|
|
|
|
### User-facing
|
|
|
|
1. NuQloud dashboard terminology and branding.
|
|
2. Address, balance as publishing credits, primary name, registered names.
|
|
3. App gallery launcher.
|
|
4. Download encrypted wallet backup file.
|
|
5. Request initial publishing credits (if user publishing is enabled).
|
|
6. Send credits and register name (if user publishing is enabled).
|
|
7. Transaction/activity list.
|
|
|
|
### Admin-facing (dashboard + admin settings)
|
|
|
|
1. Admin request queue with `Send`, `Message`, `Deny`.
|
|
2. Admin operations summary card:
|
|
- pending/sent/denied counts
|
|
- users in queue
|
|
- total sent credits
|
|
3. Admin settings entry point from dashboard.
|
|
4. Broker/external-auth/node configuration and status panels.
|
|
5. Mode and policy toggles (including `Expose user publishing`).
|
|
|
|
## 2) Full Qortal mode (`SC_MODE=full_qortal`) defaults
|
|
|
|
1. Existing Qortal-native naming/labels.
|
|
2. QORT display instead of credit abstraction.
|
|
3. Existing advanced/debug flows remain available.
|
|
4. Existing approval and request policy behavior retained.
|
|
|
|
## 3) V1 behavior rules
|
|
|
|
1. Admin dashboard operations remain visible even when user publishing is disabled.
|
|
2. User publishing toggle affects normal user actions, not admin operations.
|
|
3. Save actions in admin settings are section-scoped to avoid accidental runtime overwrite.
|
|
4. Runtime secrets stay env-first and are never cleared by empty UI submissions.
|
|
|
|
## 4) Explicitly out of scope for initial V1
|
|
|
|
1. Live package checkout/purchase flow.
|
|
2. Integrated payment processors and invoicing automation.
|
|
3. Fully automated package entitlement enforcement.
|
|
4. Cross-instance replication marketplace or tenant federation.
|
|
|
|
## 5) Next implementation targets (post-scope lock)
|
|
|
|
1. Package catalog UI in admin operations.
|
|
2. Payment method configuration and webhook ingestion.
|
|
3. Credit ledger audit panel with export.
|
|
4. Usage-based enforcement hooks from package limits.
|