harivansh-afk/betterNAS
1
1
Fork 0
mirror of https://github.com/harivansh-afk/betterNAS.git synced 2026-04-19 06:01:17 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

rename2

Browse source
This commit is contained in:
Harivansh Rathi 2026-04-01 02:28:45 +00:00
parent 12c53f3515
commit dc7969e579
37 changed files with 177 additions and 177 deletions
Download patch file Download diff file Expand all files Collapse all files

14
openspec/changes/define-platform-foundation/specs/standalone-control-plane-web/spec.md
View file

@ -1,22 +1,22 @@
## ADDED Requirements
### Requirement: Standalone aiNAS web surface
### Requirement: Standalone betternas 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
- **WHEN** betternas needs an admin or product control interface that is larger than a thin Nextcloud page
- **THEN** the plan MUST place that interface in an betternas-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.
### Requirement: Web UI consumes betternas API
The standalone web application SHALL be designed to consume betternas-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
- **THEN** it MUST obtain those concepts through the betternas 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
#### Scenario: betternas 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