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

18
openspec/changes/define-platform-foundation/proposal.md
View file

@ -1,11 +1,11 @@
## Why
The scaffold phase is complete, but the repo still lacks a clear product-level plan for how aiNAS should evolve beyond a thin Nextcloud shell and a minimal backend stub. Before implementing more code, we need planning artifacts that define the system of record, the role Nextcloud should play, the control-plane domain we intend to own, and the delivery sequence for the first real product capabilities.
The scaffold phase is complete, but the repo still lacks a clear product-level plan for how betternas should evolve beyond a thin Nextcloud shell and a minimal backend stub. Before implementing more code, we need planning artifacts that define the system of record, the role Nextcloud should play, the control-plane domain we intend to own, and the delivery sequence for the first real product capabilities.
## What Changes
- Add a north-star planning layer for the aiNAS platform.
- Define the Nextcloud substrate that aiNAS will adopt instead of rebuilding from scratch.
- Add a north-star planning layer for the betternas platform.
- Define the Nextcloud substrate that betternas will adopt instead of rebuilding from scratch.
- Define the first high-level control-plane domain model and service contracts.
- Define the intended standalone web control-plane direction outside Nextcloud.
- Define the future device access layer boundary, including the distinction between cloud-drive style access and true remote mounts.
@ -13,10 +13,10 @@ The scaffold phase is complete, but the repo still lacks a clear product-level p
## Capabilities
### New Capabilities
- `nextcloud-substrate`: A documented contract for which server, storage, sharing, and client primitives aiNAS will adopt from Nextcloud.
- `control-plane-core`: A documented contract for the first real aiNAS backend domain model and API surface.
- `standalone-control-plane-web`: A documented contract for the future Next.js web console that will become the aiNAS product surface outside Nextcloud.
- `device-access-layer`: A documented contract for how aiNAS will eventually support native device access, including mount and sync modes.
- `nextcloud-substrate`: A documented contract for which server, storage, sharing, and client primitives betternas will adopt from Nextcloud.
- `control-plane-core`: A documented contract for the first real betternas backend domain model and API surface.
- `standalone-control-plane-web`: A documented contract for the future Next.js web console that will become the betternas product surface outside Nextcloud.
- `device-access-layer`: A documented contract for how betternas will eventually support native device access, including mount and sync modes.
### Modified Capabilities
- None.
@ -25,5 +25,5 @@ The scaffold phase is complete, but the repo still lacks a clear product-level p
- Affected code: planning artifacts only
- Affected systems: architecture, product sequencing, service boundaries, implementation roadmap
- Dependencies: Nextcloud server, Nextcloud desktop/iOS references, aiNAS control-plane service, future Postgres/Redis-backed product metadata
- APIs: establishes the intended aiNAS-owned API and adapter boundaries at a high level before implementation
- Dependencies: Nextcloud server, Nextcloud desktop/iOS references, betternas control-plane service, future Postgres/Redis-backed product metadata
- APIs: establishes the intended betternas-owned API and adapter boundaries at a high level before implementation