docs

openspec/changes/define-platform-foundation/specs/nextcloud-substrate/spec.md

@@ -0,0 +1,29 @@
+## ADDED Requirements
+
+### Requirement: Nextcloud substrate boundary
+The system SHALL explicitly define which storage, sharing, and client primitives aiNAS adopts from Nextcloud and which concerns remain aiNAS-owned.
+
+#### Scenario: Product planning references Nextcloud capabilities
+- **WHEN** aiNAS decides whether to build or reuse a capability
+- **THEN** the planning artifacts MUST classify the capability as either Nextcloud substrate, aiNAS-owned logic, or a later optional fork/reference path
+
+### Requirement: Reuse external storage backends
+The platform SHALL treat Nextcloud external storage support as the first candidate substrate for connecting backend storage systems.
+
+#### Scenario: aiNAS selects initial backend storage types
+- **WHEN** aiNAS chooses the first storage backends to support
+- **THEN** the plan MUST assume reuse of Nextcloud-supported external storage backends before proposing custom storage ingestion infrastructure
+
+### Requirement: Reuse desktop and mobile references first
+The platform SHALL treat the public Nextcloud desktop and iOS clients as the first reference implementations for cloud-drive style access before planning fully custom clients.
+
+#### Scenario: aiNAS evaluates native device access
+- **WHEN** the product needs Finder-style or mobile file access
+- **THEN** the plan MUST document whether Nextcloud clients are being used directly, referenced, branded later, or intentionally replaced
+
+### Requirement: Keep Nextcloud as substrate, not system of record
+The platform SHALL not let Nextcloud become the long-term system of record for aiNAS-specific product semantics.
+
+#### Scenario: New product concept is introduced
+- **WHEN** aiNAS introduces workspaces, devices, policies, mount profiles, or similar product concepts
+- **THEN** the design MUST model those concepts in aiNAS-owned contracts rather than relying on implicit Nextcloud-only representations