Problem: isq syncs the latest state, overwriting previous state. You can't answer "what did this issue look like last week?" or "when was this label added?" History is valuable for debugging, auditing, and AI agents that need temporal context.
Goal: Explore storing issue history for time-travel queries.
Success criteria (research phase):
- Design schema for temporal data (append-only? snapshot per sync?)
- Estimate storage cost for typical repos
- Prototype: `isq issue show 54 --at 2024-01-15`
- Evaluate: is the complexity worth the capability?
Context (Rich Hickey's Datomic): All data is immutable; time is a first-class concept. You can query as-of any point in time. This is powerful for systems that need to reason about change.
Why later: Significant architectural change. Needs clear use case to justify complexity. "Infrastructure layer" ambition makes this worth exploring eventually.
Problem: isq syncs the latest state, overwriting previous state. You can't answer "what did this issue look like last week?" or "when was this label added?" History is valuable for debugging, auditing, and AI agents that need temporal context.
Goal: Explore storing issue history for time-travel queries.
Success criteria (research phase):
Context (Rich Hickey's Datomic): All data is immutable; time is a first-class concept. You can query as-of any point in time. This is powerful for systems that need to reason about change.
Why later: Significant architectural change. Needs clear use case to justify complexity. "Infrastructure layer" ambition makes this worth exploring eventually.