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

ADR-0002: Define date semantics #2

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 spec requires the catalog-added date to stay distinct from filesystem timestamps and leaves the
existence of a user-facing "creation date" open.

Decision

  • models.added_at records the catalog event and is authoritative.
  • File-level mtime and size are captured at import as descriptive file metadata.
  • No separate user-facing "creation date" field in MVP.

Consequences

  • Filesystem timestamps are descriptive only and never drive sorting defaults.
  • A creation-date concept can be added later through a separately scoped future change.

Acceptance criteria

  • Decision recorded in this issue and mirrored in ignored notes/decisions; no tracked ADR required
  • Date fields reflected in the schema issues
## Context The spec requires the catalog-added date to stay distinct from filesystem timestamps and leaves the existence of a user-facing "creation date" open. ## Decision - `models.added_at` records the catalog event and is authoritative. - File-level `mtime` and `size` are captured at import as descriptive file metadata. - No separate user-facing "creation date" field in MVP. ## Consequences - Filesystem timestamps are descriptive only and never drive sorting defaults. - A creation-date concept can be added later through a separately scoped future change. ## Acceptance criteria - [ ] Decision recorded in this issue and mirrored in ignored notes/decisions; no tracked ADR required - [ ] Date fields reflected in the schema issues
keith added this to the M0 - Foundations & Decisions milestone 2026-10-10 22:17:11 +00:00
keith added the area:dbpriority:mediumtype:decision labels 2026-10-10 22:17:11 +00:00
keith commented 2026-10-10 23:10:36 +00:00
Author
Owner
Copy link
Copy source

M0 decision verified: added_at and file mtime/size are distinct; no creation-date field. Confirmed downstream schema issues #14 and #15 carry these fields. Local ADR and specification retain the decision.

M0 decision verified: added_at and file mtime/size are distinct; no creation-date field. Confirmed downstream schema issues #14 and #15 carry these fields. Local ADR and specification retain the decision.
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:db priority:medium 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#2