UNPKG

shipdeck

Version:

Ship MVPs in 48 hours. Fix bugs in 30 seconds. The command deck for developers who ship.

shipdeck.ai

shipdeckai/shipdeck

87 lines (64 loc) • 2.41 kB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
# Task 004: State Persistence Layer ## 1. Task Overview ### Task Title **Title:** Implement durable state persistence for 48-hour workflows ### Goal Statement **Goal:** Create a robust state management system that can persist workflow progress, enabling resume capability after crashes or interruptions. Critical for the 48-hour guarantee. --- ## 2. Strategic Analysis ### Problem Context 48-hour workflows are long-running processes that must survive crashes, network issues, and system restarts. We need durable state persistence to ensure no work is lost. ### Recommendation Implement a dual-layer persistence: local filesystem for speed, Supabase for durability and multi-instance coordination. --- ## 3. Technical Requirements ### Functional Requirements - Persist workflow state after each node completion - Store node inputs, outputs, and status - Support atomic state updates - Enable workflow resume from any checkpoint - Track partial progress within nodes - Store cost/token usage data ### Non-Functional Requirements - **Durability:** Zero data loss on crash - **Performance:** <50ms write latency - **Scalability:** Handle 10MB+ state per workflow - **Consistency:** No corrupted state on concurrent updates --- ## 4. Implementation Plan ### Phase 1: State Schema Design - [ ] Define workflow state structure - [ ] Create state versioning system - [ ] Design checkpoint format - [ ] Plan migration strategy ### Phase 2: Local Persistence - [ ] Implement filesystem-based storage - [ ] Add atomic write operations - [ ] Create state compression - [ ] Implement cleanup policies ### Phase 3: Supabase Integration - [ ] Set up Supabase tables for workflows - [ ] Implement state sync to cloud - [ ] Add conflict resolution - [ ] Create state recovery mechanisms ### Phase 4: Resume Capability - [ ] Implement workflow resume logic - [ ] Add partial node recovery - [ ] Create rollback mechanisms - [ ] Test crash recovery scenarios --- ## 5. Success Criteria - [ ] Workflow state persists after each node - [ ] Can resume workflow after process crash - [ ] State is consistent across restarts - [ ] No data loss in any failure scenario - [ ] Resume adds <1 second overhead --- ## 6. Dependencies - Task 002 (DAG Engine) completed - Supabase account and database setup --- ## 7. Estimated Effort **Priority:** P0 (Critical - Week 1) **Complexity:** High **Duration:** 2-3 days