Protect transcript refinement resume semantics

This commit is contained in:
2026-08-30 13:03:13 +00:00
parent 4d6086fefb
commit 7ee637803d
12 changed files with 512 additions and 16 deletions

View File

@@ -99,14 +99,20 @@ Execution rules:
repeated self-skip with the same reason and no outputs is stable and does not
perpetually rerun dependent work.
Prepare, transcribe, and merge currently provide semantic-configuration
evidence. Changing prepare selection semantics reruns all fixed descendants;
changing WhisperX language/service identity reuses prepare; and changing a
Seriatim merge transformation reuses prepare and transcribe. Operational
timeouts, retry/concurrency tuning, executable paths, workspace/cache/spool
placement, reports, diagnostics, and secret values are excluded. Configuration,
models, prompts, modules, or resources loaded privately inside external tools
remain unobservable to Narratio and require an explicit `--force` after change.
Prepare through render currently provide semantic-configuration evidence.
Changing prepare selection semantics reruns all fixed descendants; changing
WhisperX language/service identity reuses prepare; changing a Seriatim merge
transformation reuses prepare and transcribe; and changing an Audita model
reuses prepare, transcribe, and merge while rebuilding transcript refinement.
A trim change invalidates both render and extract through the fixed dependency
relation, while a render-only change preserves the extract sibling.
Operational timeouts, retry/concurrency tuning, executable paths,
workspace/cache/spool placement, reports, diagnostics, and secret values are
excluded. Configuration, models, prompts, modules, or resources loaded
privately inside external tools remain unobservable to Narratio. If their
contents change behind the same configured identifier, explicitly force the
affected stage.
An explicit self-skip is a durable `skipped` stage outcome that later runs
reconsider. It differs from successful no-output execution: disabled `render`