ADR-0003: Changed-file handling without versioning #3

New Issue

2026-10-10T22:17:11Z

keith commented

2026-10-10 22:17:11 +00:00

Context

MVP must flag changed files as "Updated". Versioning is explicitly out of scope.

Decision

When a re-scan finds a content hash differing from the recorded hash, the file is flagged Updated.
MeshVault does not retain prior content and does not create versions. The user acknowledges the
change, which re-baselines the stored hash.

Consequences

Detecting an external overwrite cannot recover prior content; this is documented, not mitigated.
A future versioning feature needs an explicit preservation mechanism (copy-on-change).

Acceptance criteria

Decision recorded in this issue and mirrored in ignored notes/decisions; no tracked ADR required
Limitation documented in user-facing docs

## Context MVP must flag changed files as "Updated". Versioning is explicitly out of scope. ## Decision When a re-scan finds a content hash differing from the recorded hash, the file is flagged `Updated`. MeshVault does not retain prior content and does not create versions. The user acknowledges the change, which re-baselines the stored hash. ## Consequences - Detecting an external overwrite cannot recover prior content; this is documented, not mitigated. - A future versioning feature needs an explicit preservation mechanism (copy-on-change). ## Acceptance criteria - [ ] Decision recorded in this issue and mirrored in ignored notes/decisions; no tracked ADR required - [ ] Limitation documented in user-facing docs

keith added this to the M0 - Foundations & Decisions milestone 2026-10-10 22:17:11 +00:00

keith added the area:indexer priority:medium type:decision labels 2026-10-10 22:17:11 +00:00

keith referenced this issue

2026-10-10 22:18:27 +00:00

Schema: files with hash, size and lifecycle status #15

keith referenced this issue

2026-10-10 22:23:44 +00:00

Changed-file Updated flag and acknowledgement #48

keith commented

2026-10-10 23:10:37 +00:00

M0 decision verified and mirrored locally. Root README now explains Updated acknowledgement and explicitly states old contents cannot be recovered after external overwrite. README is currently uncommitted; issue remains open until documentation is committed.

keith commented

2026-10-11 00:53:14 +00:00

M0 work committed locally on main as c6cb3cec89 (chore: establish M0 project foundations). Verified composer validate --strict, composer lint, composer test, composer audit and git diff --cached --check before commit. Documentation explicitly defers runtime application/Compose to M1; tests cover repository foundations only. Closing following owner approval. Commit has not been pushed.

M0 work committed locally on main as c6cb3cec89b99634f255a93481363efe7ef19c33 (chore: establish M0 project foundations). Verified composer validate --strict, composer lint, composer test, composer audit and git diff --cached --check before commit. Documentation explicitly defers runtime application/Compose to M1; tests cover repository foundations only. Closing following owner approval. Commit has not been pushed.

keith closed this issue

2026-10-11 00:53:16 +00:00

keith referenced this issue from a commit

2026-10-11 02:51:52 +00:00

chore: establish M0 project foundations

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: keith/MeshVault#3