Decide propagation behavior on mapping version updates: forward-only with explicit re-run, lazy re-derivation, or auto-re-run with diff preview.
Why this matters
When a Mapping Workshop entry is updated to a new version, downstream behavior on existing triples is currently undefined. Three options:
(a) Forward-only — existing triples untouched until manual re-run via the Re-run Console. Safest, makes intent explicit. (b) Auto-mark stale — affected triples flagged, re-derived lazily on next read. (c) Auto-re-run on commit with diff preview — most aggressive, requires confidence in the preview.
Recommend (a) as default. Decision needed before Studio v1 ships.