Prior results

Reuse compatible evidence from earlier executions without treating old output files as truth.

Relifold retains compatible semantic evidence from earlier work in a Prior Store. When a later session encounters the same value or relationship under the same task meaning, it may reuse that evidence instead of paying for the same decision again.

What determines compatibility

Compatibility depends on the operation, the semantic criterion, the relevant prompt binding, the values being compared or transformed, and the declared task settings. Renaming a session or moving a dataset does not by itself invalidate evidence. Changing what “same,” “better,” or “belongs” means should.

Incremental refresh

An incremental task combines established compatible evidence with decisions required by new data, then emits a complete result for the current session. It does not read an earlier output Space as unquestionable truth. This matters when the physical input and output paths change every run.

Corrections and review

Reviewed human decisions can correct earlier evidence. A correction is additive evidence tied to the reviewed proposition; it does not mutate a historical session. Future compatible work sees the corrected result.

What you can observe

Sessions report cached calls, skipped work, savings, and which tasks used incremental refresh. The Prior Store itself is managed by Relifold: applications do not import or edit its physical records.