init specification 1

openspec/changes/scaffold-nextcloud-control-plane/specs/control-plane-service/spec.md

@@ -0,0 +1,22 @@
+## ADDED Requirements
+
+### Requirement: Dedicated control-plane service
+The system SHALL provide an aiNAS-owned control-plane service that is separate from the Nextcloud shell app and owns product domain logic.
+
+#### Scenario: aiNAS adds a new control-plane rule
+- **WHEN** a new business rule for storage policy, RBAC, orchestration, or future client behavior is introduced
+- **THEN** the rule MUST be implemented in the control-plane service rather than as primary logic inside the Nextcloud app
+
+### Requirement: Client-agnostic internal API
+The control-plane service SHALL expose internal APIs that can be consumed by the Nextcloud shell app and future aiNAS clients without requiring direct coupling to Nextcloud internals.
+
+#### Scenario: New aiNAS client consumes control-plane behavior
+- **WHEN** aiNAS adds a web, desktop, or iOS surface outside Nextcloud
+- **THEN** that surface MUST be able to consume control-plane behavior through documented aiNAS service interfaces
+
+### Requirement: Nextcloud backend adapter boundary
+The control-plane service SHALL isolate Nextcloud-specific integration at its boundary so that storage and sharing backends remain replaceable over time.
+
+#### Scenario: Service calls the Nextcloud backend
+- **WHEN** the control-plane service needs to interact with file or sharing primitives provided by Nextcloud
+- **THEN** the interaction MUST pass through a dedicated adapter boundary instead of spreading Nextcloud-specific calls across unrelated domain code

openspec/changes/scaffold-nextcloud-control-plane/specs/nextcloud-shell-app/spec.md

@@ -0,0 +1,22 @@
+## ADDED Requirements
+
+### Requirement: aiNAS shell app inside Nextcloud
+The system SHALL provide a dedicated aiNAS shell app inside Nextcloud that establishes branded entry points for aiNAS-owned product surfaces.
+
+#### Scenario: aiNAS surface is visible in Nextcloud
+- **WHEN** the aiNAS app is installed in a local development environment
+- **THEN** Nextcloud MUST expose an aiNAS-branded application surface that can be used as the integration shell for future product flows
+
+### Requirement: Thin adapter responsibility
+The aiNAS shell app SHALL act as an adapter layer and MUST keep core business logic outside the Nextcloud monolith.
+
+#### Scenario: Product decision requires domain logic
+- **WHEN** the shell app needs information about policy, orchestration, or future product rules
+- **THEN** it MUST obtain that information through aiNAS-owned service boundaries instead of embedding the decision logic directly in the app
+
+### Requirement: Nextcloud integration hooks
+The aiNAS shell app SHALL provide the minimal integration hooks required to connect aiNAS-owned services to Nextcloud runtime surfaces such as navigation, settings, and backend access points.
+
+#### Scenario: aiNAS needs a Nextcloud-native entry point
+- **WHEN** aiNAS introduces a new product flow that starts from a Nextcloud-rendered page
+- **THEN** the shell app MUST provide a supported hook or page boundary where the flow can enter aiNAS-controlled logic

openspec/changes/scaffold-nextcloud-control-plane/specs/workspace-scaffold/spec.md

@@ -0,0 +1,22 @@
+## ADDED Requirements
+
+### Requirement: Repository boundary scaffold
+The repository SHALL provide a top-level scaffold that separates infrastructure, Nextcloud app code, aiNAS-owned service code, shared contracts, documentation, and automation scripts.
+
+#### Scenario: Fresh clone exposes expected boundaries
+- **WHEN** a developer inspects the repository after applying this change
+- **THEN** the repository MUST include dedicated locations for Docker runtime assets, the Nextcloud shell app, the control-plane service, shared contracts, documentation, and scripts
+
+### Requirement: Local development platform
+The repository SHALL provide a local development runtime that starts a vanilla Nextcloud instance together with its required backing services and the aiNAS control-plane service.
+
+#### Scenario: Developer boots the local stack
+- **WHEN** a developer runs the documented local startup flow
+- **THEN** the system MUST start Nextcloud and the aiNAS service dependencies without requiring a forked Nextcloud build
+
+### Requirement: Shared contract package
+The repository SHALL include a shared contract location for schemas and service interfaces used between the Nextcloud shell app and aiNAS-owned services.
+
+#### Scenario: Interface changes are modeled centrally
+- **WHEN** aiNAS defines an internal API or payload exchanged between the shell app and the control-plane service
+- **THEN** the schema MUST be represented in the shared contracts location rather than duplicated ad hoc across codebases