harivansh-afk/betterNAS
1
1
Fork 0
mirror of https://github.com/harivansh-afk/betterNAS.git synced 2026-04-15 09:01:13 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
betterNAS/openspec/changes/define-platform-foundation/specs/device-access-layer/spec.md
Harivansh Rathi dc7969e579 rename2
2026-04-01 02:28:45 +00:00

1.4 KiB
Raw Blame History

ADDED Requirements

Requirement: Distinguish cloud-drive access from true remote mounts

The platform SHALL explicitly distinguish between cloud-drive style access and true remote mount behavior.

Scenario: Device access strategy is discussed

  • 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

The platform SHALL not require a custom device-native agent for the first backend and control-plane planning unless true remote mount orchestration is confirmed as a near-term requirement.

Scenario: Delivery sequencing is chosen

  • WHEN implementation order is planned
  • 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 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 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