vibe-coded/gallery-organizer-web
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

init

Browse Source
This commit is contained in:
Danilo Reyes
2026-02-07 06:01:29 -06:00
parent 0f5e76ddc9
commit 070a3633d8
13 changed files with 1302 additions and 36 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
.specify/templates/plan-template.md
View File

@@ -31,7 +31,14 @@
*GATE: Must pass before Phase 0 research. Re-check after Phase 1 design.*
[Gates determined based on constitution file]
- Whitelisted directories remain protected from any directory-level delete
- All destructive actions include dry-run preview, explicit confirmation, and audit log
- Read-only mode disables all mutations while allowing browsing
- Destructive operations are single-writer and never concurrent
- Operations are bounded to configured roots; destructive ops never follow symlinks
- Default deletion is two-stage (trash/staging); hard delete is explicit + confirmed
- List-file edits are previewed, optional, atomic; exact-match removal by default
- UI surfaces directory state and recent audit activity for verification
## Project Structure

10
.specify/templates/spec-template.md
View File

@@ -95,6 +95,16 @@
- **FR-006**: System MUST authenticate users via [NEEDS CLARIFICATION: auth method not specified - email/password, SSO, OAuth?]
- **FR-007**: System MUST retain user data for [NEEDS CLARIFICATION: retention period not specified]
### Safety & Data Preservation Requirements *(mandatory for destructive actions)*
- **SR-001**: System MUST provide a dry-run preview for destructive actions
- **SR-002**: System MUST require explicit confirmation before destructive actions
- **SR-003**: System MUST append an audit record for every mutation
- **SR-004**: System MUST refuse to act outside configured root paths
- **SR-005**: System MUST NOT follow symlinks for destructive actions
- **SR-006**: System MUST provide a global read-only mode that disables mutations
- **SR-007**: System MUST default to two-stage deletion (trash/staging) unless explicitly configured
### Key Entities *(include if feature involves data)*
- **[Entity 1]**: [What it represents, key attributes without implementation]

18
.specify/templates/tasks-template.md
View File

@@ -73,6 +73,24 @@ Examples of foundational tasks (adjust based on your project):
---
## Phase 2.5: Safety & Compliance (Mandatory for destructive operations)
**Purpose**: Enforce constitution safety guarantees before any deletion work
- [ ] T009A Implement global read-only mode that blocks all mutations
- [ ] T009B Enforce root-path boundaries for all filesystem operations
- [ ] T009C Implement single-writer guard for destructive operations
- [ ] T009D Implement dry-run preview + explicit confirmation flow for deletion
- [ ] T009E Implement two-stage deletion (trash/staging) as default behavior
- [ ] T009F Enforce symlink-safe deletion (do not follow symlinks)
- [ ] T009G Append-only audit log with required fields for every mutation
- [ ] T009H Enforce whitelist protection for directory-level actions
- [ ] T009I Implement list-file edit preview + atomic write (exact-match default)
**Checkpoint**: Safety guarantees verified - destructive workflows can now begin
---
## Phase 3: User Story 1 - [Title] (Priority: P1) 🎯 MVP
**Goal**: [Brief description of what this story delivers]