keith/MeshVault
1
0 Fork 0
Code Issues 44 Pull Requests Actions Packages Projects Releases Wiki Activity

ADR-0001: Adopt managed storage for MVP import #1

New Issue
Closed
opened 2026-10-10 22:17:11 +00:00 by keith · 1 comment
keith commented 2026-10-10 22:17:11 +00:00
Owner
Copy link
Copy source

Context

The project spec left the MVP storage approach open: index-in-place versus managed storage.

Decision

MeshVault uses managed storage. Import copies files from a user-supplied source path into a
dedicated library directory (MESHVAULT_LIBRARY_DIR). The browsable folder hierarchy mirrors the
managed library directory on disk.

Consequences

  • Original source files are never modified, moved, or deleted.
  • Source directories may be read-only; only the library directory requires write access.
  • Physical folder operations are safe because MeshVault owns the managed tree.
  • Import is a copy and must account for disk space, verification, and name collisions.
  • Backup is pg_dump plus a filesystem copy of the library directory.
  • Disk usage is duplicated relative to the source collection; this is accepted for MVP.

Acceptance criteria

  • Decision recorded in this issue and mirrored in ignored notes/decisions; no tracked ADR required
  • Local specification decision cross-reference retained in ignored notes; tracking remains in issues
## Context The project spec left the MVP storage approach open: index-in-place versus managed storage. ## Decision MeshVault uses **managed storage**. Import copies files from a user-supplied source path into a dedicated library directory (`MESHVAULT_LIBRARY_DIR`). The browsable folder hierarchy mirrors the managed library directory on disk. ## Consequences - Original source files are never modified, moved, or deleted. - Source directories may be read-only; only the library directory requires write access. - Physical folder operations are safe because MeshVault owns the managed tree. - Import is a copy and must account for disk space, verification, and name collisions. - Backup is `pg_dump` plus a filesystem copy of the library directory. - Disk usage is duplicated relative to the source collection; this is accepted for MVP. ## Acceptance criteria - [ ] Decision recorded in this issue and mirrored in ignored notes/decisions; no tracked ADR required - [ ] Local specification decision cross-reference retained in ignored notes; tracking remains in issues
keith added this to the M0 - Foundations & Decisions milestone 2026-10-10 22:17:11 +00:00
keith added the type:decisionarea:backendpriority:high labels 2026-10-10 22:17:11 +00:00
keith commented 2026-10-10 23:10:35 +00:00
Author
Owner
Copy link
Copy source

M0 decision verified: managed-copy semantics and read-only sources are documented in the local specification and ignored ADR copy. Local specification now cross-references issue #1. No tracked ADR required.

M0 decision verified: managed-copy semantics and read-only sources are documented in the local specification and ignored ADR copy. Local specification now cross-references issue #1. No tracked ADR required.
keith closed this issue 2026-10-10 23:10:39 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
area:backend
PHP application logic
 area:db
PostgreSQL schema and migrations
 area:frontend
PHP views, Tailwind, browser JS
 area:indexer
Scanning, hashing, import pipeline
 area:infra
Docker, CI, deployment
 priority:high
Blocking or critical path
 priority:low
Nice to have
 priority:medium
Normal priority
 type:bug
Defect
 type:chore
Tooling, scaffolding, maintenance
 type:decision
Architecture decision record
 type:docs
Documentation
 type:feature
New user-facing capability
No labels area:backend priority:high type:decision
Milestone
No items
No Milestone M0 - Foundations & Decisions
Projects
Clear projects
No projects
Assignees
Clear assignees
keith (Keith Solomon)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: keith/MeshVault#1