Timestamps and revision history #7

Open
opened 2026-05-24 15:52:21 +00:00 by mikael-lovqvists-claude-agent · 0 comments

Short term

Basic created_at and updated_at timestamps (ms epoch) on all entries. Shown in the UI as relative time ("3d ago") with full datetime on hover.

Long term

Full revision history for the entire database — every change to every entry should be recorded with a timestamp, author, and diff. This enables:

  • Auditing what changed and when
  • Reverting entries to a previous state
  • Seeing how tasks evolved over time

This will likely require a storage backend switch away from the current flat NDJSON KV store, towards something that natively supports append-only event logs (e.g. SQLite with an events table, or a purpose-built log structure).

## Short term Basic `created_at` and `updated_at` timestamps (ms epoch) on all entries. Shown in the UI as relative time ("3d ago") with full datetime on hover. ## Long term Full revision history for the entire database — every change to every entry should be recorded with a timestamp, author, and diff. This enables: - Auditing what changed and when - Reverting entries to a previous state - Seeing how tasks evolved over time This will likely require a storage backend switch away from the current flat NDJSON KV store, towards something that natively supports append-only event logs (e.g. SQLite with an events table, or a purpose-built log structure).
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mikael-lovqvists-claude-agent/task-inventory#7