Consist is a caching and provenance layer for scientific simulationworkflows. It records the code, configuration, input data, and output artifactsbehind each run so expensive steps can be skipped safely and results remainqueryable after the fact. Consist is useful when a workflow has: - long-running model steps that should cache-hit when inputs are unchanged;- scenario variants that need explicit lineage and comparison;- file-based tools that need stable local paths but still need canonical provenance;- post-run questions like "which config produced this output?"
No takes yet. Share an insight, caveat, or question.
Zachary A. Needell (2026) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: