Artefact
Our internal library that owns every bundle read and write. Every pipeline step that changes a dataset goes through it.
Last updated
artefact/ is the library in our codebase that owns all
bundle reads and writes. Every pipeline step that
changes a dataset goes through artefact; every read is served from a
cached hydrated bundle.
Why it matters for your research. As a user you don’t interact with artefact directly, but it is the reason two concurrent analysis runs on the same dataset don’t corrupt the bundle. The writer lock is Redis-backed; readers operate on hydrated snapshots. The guarantees that make versioning meaningful are implemented here.
In Archēglyph. The implementation detail behind every mention of “bundle” or “versioning”. Reproducibility lives here.
Not to be confused with. The generic British-English noun “artefact” meaning a made thing — we use it in both senses deliberately.