Skip to Content
Last modified by Robert Schaub on 2025/12/22 14:38
Hide last authors
Robert Schaub 1.1 1 {{mermaid}}
2 graph LR V1[Version 1] -->|Edit| V2[Version 2] V2 -->|Edit| V3[Version 3] V3 -->|Edit| VN[Version N] V2 --> EDIT1[Edit Record] V3 --> EDIT2[Edit Record] VN --> EDITN[Edit Record] EDIT1 -->|Stores| BEFORE[Before State] EDIT1 -->|Stores| AFTER[After State] EDIT1 -->|Stores| WHO[Who + Why] REVERT[Revert to V2] -.->|Creates| VN1[New Version = V2] style VN fill:#99ff99 style REVERT fill:#ffff99
3 {{/mermaid}} == Explanation ==
4 **Linear Versioning Only**:
5 * Each edit creates a new version (V1 → V2 → V3 → ... → VN)
6 * No branching, no parallel versions
7 * Simple sequential numbering
8 **Edit Records**:
9 * Every version change stored in EDIT table
10 * Contains: before_state (JSON), after_state (JSON), user_id, reason, timestamp
11 * Full audit trail preserved forever
12 **Revert Mechanism**:
13 * "Revert to V2" doesn't delete V3-VN
14 * Instead, creates new version VN+1 with V2's content
15 * History never deleted, only moved forward
16 **What Gets Versioned**:
17 * Claims: assertion text, domain, status, scores
18 * Evidence: excerpt, relevance, support type
19 * Scenarios: description, assumptions, confidence
20 **Not Versioned** (current state only):
21 * Source track records (continuously updated)
22 * Quality metrics (time-series data)
23 * User reputation (accumulated score)
24 **Access**:
25 * Current version: Default view
26 * Version history: Click "History" tab
27 * Diff between versions: Compare any two versions
28 * Revert: Select version → "Revert to this version" → Creates new version
29 **Storage**:
30 * Current state: In entity table (CLAIM, EVIDENCE, SCENARIO)
31 * Historical states: In EDIT table (before_state, after_state JSON)
32 * Hot storage: Last 3 months of edits
33 * Cold storage: Older edits archived to S3