harivansh-afk/betterNAS
1
1
Fork 0
mirror of https://github.com/harivansh-afk/betterNAS.git synced 2026-04-17 14:01:21 +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

12
openspec/changes/define-platform-foundation/specs/control-plane-core/spec.md
View file

@ -1,11 +1,11 @@
## ADDED Requirements
### Requirement: aiNAS control plane as product system of record
The system SHALL define an aiNAS-owned control plane as the authoritative home for product-level domain concepts.
### Requirement: betternas control plane as product system of record
The system SHALL define an betternas-owned control plane as the authoritative home for product-level domain concepts.
#### Scenario: Product semantics require persistence
- **WHEN** aiNAS needs to represent devices, workspaces, storage sources, shares, mount profiles, policies, or audit history
- **THEN** the planning artifacts MUST place those concepts inside the aiNAS control-plane domain model
- **WHEN** betternas needs to represent devices, workspaces, storage sources, shares, mount profiles, policies, or audit history
- **THEN** the planning artifacts MUST place those concepts inside the betternas control-plane domain model
### Requirement: High-level domain contracts
The platform SHALL define a first high-level contract map for core entities and API categories before implementation proceeds.
@ -17,9 +17,9 @@ The platform SHALL define a first high-level contract map for core entities and
### Requirement: Standalone service posture
The control plane SHALL remain architecturally standalone even if it is temporarily packaged or surfaced through Nextcloud-compatible mechanisms.
#### Scenario: aiNAS backend is consumed by multiple surfaces
#### Scenario: betternas backend is consumed by multiple surfaces
- **WHEN** a standalone web app, Nextcloud shell, or future device client needs backend behavior
- **THEN** the design MUST treat the control plane as a reusable aiNAS service rather than as logic conceptually trapped inside the Nextcloud app model
- **THEN** the design MUST treat the control plane as a reusable betternas service rather than as logic conceptually trapped inside the Nextcloud app model
### Requirement: Single modular backend first
The platform SHALL prefer one modular backend service before splitting the control plane into multiple distributed services.