mirror of
https://github.com/harivansh-afk/betterNAS.git
synced 2026-04-16 14:01:06 +00:00
22 lines
1.4 KiB
Markdown
22 lines
1.4 KiB
Markdown
## 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
|