Persistent volumes with TTL for container/worktree storage #893

Closed
opened 2026-10-27 13:38:11 +00:00 by sam · 0 comments
Owner

Phase 2 of docs/prds/archie-core-v2-architecture.md. Current worktree lifecycle is fresh-clone-per-task with status-driven cleanup, no TTL. Add persistent volume support with TTL-based expiry to avoid repeated full clones for repeated work on the same repo.

Acceptance Criteria

Container/worktree storage can persist across tasks for the same repo up to a configured TTL, with automatic cleanup after expiry.


Imported from beads archie-core-1786637499292-362-8b520db8 · GitHub #383 · type feature · priority P2 · created 2026-08-08 · closed 2026-08-08

Phase 2 of docs/prds/archie-core-v2-architecture.md. Current worktree lifecycle is fresh-clone-per-task with status-driven cleanup, no TTL. Add persistent volume support with TTL-based expiry to avoid repeated full clones for repeated work on the same repo. ### Acceptance Criteria Container/worktree storage can persist across tasks for the same repo up to a configured TTL, with automatic cleanup after expiry. --- _Imported from beads `archie-core-1786637499292-362-8b520db8` · GitHub #383 · type feature · priority P2 · created 2026-08-08 · closed 2026-08-08_
sam added the mediumfeature labels 2026-10-27 13:38:11 +00:00
sam self-assigned this 2026-10-27 13:38:11 +00:00
sam closed this issue 2026-10-27 13:38:11 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#893