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

6
openspec/changes/define-platform-foundation/specs/device-access-layer/spec.md
View file

@ -4,7 +4,7 @@
The platform SHALL explicitly distinguish between cloud-drive style access and true remote mount behavior.
#### Scenario: Device access strategy is discussed
- **WHEN** aiNAS plans device-native access on macOS or mobile
- **WHEN** betternas plans device-native access on macOS or mobile
- **THEN** the planning artifacts MUST state whether the capability is based on cloud-drive style client behavior, true remote mounts, or both
### Requirement: Defer custom native agent work until justified
@ -15,8 +15,8 @@ The platform SHALL not require a custom device-native agent for the first backen
- **THEN** the design MUST allow heavy reuse of Nextcloud client references before requiring a custom native device daemon
### Requirement: Keep future device agent possible
The architecture SHALL preserve a clear boundary where a future aiNAS-owned device access layer can be introduced without rewriting the control plane.
The architecture SHALL preserve a clear boundary where a future betternas-owned device access layer can be introduced without rewriting the control plane.
#### Scenario: Product later adds login-time mounts or stronger native behavior
- **WHEN** aiNAS decides to add explicit mount orchestration or device-native workflows
- **WHEN** betternas decides to add explicit mount orchestration or device-native workflows
- **THEN** the design MUST place that behavior in a device access layer separate from the core control-plane domain