Versioning
Also: Dataset versions · Versions
Named, immutable snapshots of a dataset's bundle at a point in time. Let you return to exactly that state later.
Last updated
A version in Archēglyph is a named, immutable snapshot of a dataset’s bundle at a point in time. Save a version after a successful analysis run and you can always come back to exactly that state, even after re-running the pipeline with different models. Versions are tracked via an object-storage manifest; the bundle bytes themselves are immutable once published.
Why it matters for your research. Reproducibility. An article that cites Archēglyph results without a version pin is citing a moving target. Versioning also supports non-destructive exploration: try a different embedding model, keep the old version for comparison, archive either, revert if needed.
In Archēglyph. Every dataset exposes a versions panel; each version has its own viewable URL and its own bundle snapshot. See Why we snapshot per dataset.
Not to be confused with.
- Git commits — those operate on source code, not on derived indices.
- Database backups — those are operational and not semantic save- points; they don’t name why you saved.
- Exports — an export is a copy that leaves the system. A version is the live object the system keeps.