mirror of
https://github.com/harivansh-afk/betterNAS.git
synced 2026-04-17 00:04:51 +00:00
22 lines
1.3 KiB
Markdown
22 lines
1.3 KiB
Markdown
## ADDED Requirements
|
|
|
|
### Requirement: Standalone aiNAS web surface
|
|
The platform SHALL plan for a standalone web control-plane surface outside Nextcloud.
|
|
|
|
#### Scenario: Product UI expands beyond an embedded shell
|
|
- **WHEN** aiNAS needs an admin or product control interface that is larger than a thin Nextcloud page
|
|
- **THEN** the plan MUST place that interface in an aiNAS-owned standalone web application
|
|
|
|
### Requirement: Web UI consumes aiNAS API
|
|
The standalone web application SHALL be designed to consume aiNAS-owned backend contracts rather than Nextcloud internals directly.
|
|
|
|
#### Scenario: Web product feature requires backend data
|
|
- **WHEN** the standalone web surface needs workspaces, devices, shares, or policies
|
|
- **THEN** it MUST obtain those concepts through the aiNAS control-plane API design rather than by binding directly to Nextcloud internal models
|
|
|
|
### Requirement: Preserve Nextcloud shell as adapter
|
|
The presence of a standalone web app SHALL not remove the need for the thin Nextcloud shell as an adapter and embedded entry surface.
|
|
|
|
#### Scenario: aiNAS still needs a presence inside Nextcloud
|
|
- **WHEN** the broader product grows outside the Nextcloud UI
|
|
- **THEN** the shell app MUST remain conceptually limited to integration and entry-point responsibilities rather than absorbing the full standalone product
|