Version Control
Raptor provides Git-like version control for documents, tracking changes over time and enabling comparisons, rollbacks, and lineage visualization.Hierarchy
Raptor uses a three-level hierarchy:Document
The logical entity representing a conceptual document:- Unique ID: Persistent identifier across all versions
- Latest Version: Points to the current version
- Lineage: Links to related documents (parent/children)
Version
A content snapshot of the document at a point in time:- Version Number: Auto-incremented (1, 2, 3…)
- Version Label: Human-readable label (“v1.0”, “draft”, “final”)
- Content Hash: SHA-256 hash of file content
- Parent Version: Link to previous version
Variant
A processing configuration applied to a version:- Config Hash: SHA-256 hash of processing parameters
- Status: pending, processing, completed, failed
- Primary Flag: Whether this is the default variant
- Deduplication Stats: Reuse metrics
Creating Versions
Auto-Linking (Recommended)
Let Raptor detect versions automatically:Manual Linking
Explicitly specify the parent:Retroactive Linking
Link documents after upload:Listing Versions
Get all versions of a document:Managing Versions
Set Default Version
Change which version is considered “current”:Update Version Label
Add or change version labels:Delete Version
Remove a version (soft delete with auto-promotion):Revert to Previous Version
Create a new version from an old one:Version Comparison
Compare two versions to see changes:Lineage
View Lineage
Get the complete version history:Lineage Tree
Visualize parent-child relationships:Lineage Stats
Get statistics about the lineage:Lineage Changelog
Generate a changelog across all versions:Unlinking
Remove a document from its lineage:Multi-Variant Processing
Process the same version with different configurations:Create Variants
Get Variant
Retrieve specific variant details:Get Variant Chunks
Retrieve chunks from a specific variant:Delete Variant
Remove a variant (auto-promotes if primary):Use Cases
Use Case 1: Policy Document Timeline
Use Case 2: A/B Testing Chunking Strategies
Use Case 3: Draft → Final Workflow
Best Practices
Use version labels
Use version labels
Always add descriptive version labels:
Keep chunking consistent
Keep chunking consistent
Use the same chunking config across versions for better deduplication:
Monitor lineage depth
Monitor lineage depth
Long lineages (>10 versions) may slow processing:
Clean up variants
Clean up variants
Delete unused variants to reduce storage: