Clarify validation behavior when chains are replaced

This commit is contained in:
2026-11-22 09:32:32 +00:00
parent 581229cd1f
commit 8ea96dc7a4
5 changed files with 20 additions and 7 deletions

View File

@@ -502,7 +502,9 @@ Stage 27 adds cache selection to this same helper, not a parallel executor.
execution options, and operation-scoped assessors. The runner consumes native
helper outcomes without outer retries or revalidation; deterministic modules
produce once and are assessed directly, with an optional module-owned fallback
function. Final codec/source checks remain mandatory. Fallback eligibility follows
function. Final codec checks remain mandatory; ordinary artifact citation checks
depend on configured validators. Necessary source parsing/materialization and
module/fallback/cache construction checks remain. Fallback eligibility follows
chunk ancestry, lane results, and actual generated-reference consumers without
tainting unrelated work; emitting operations contribute once to fallback_count.
Removed superseded attempt/correction hooks and their debug/policy projections.

View File

@@ -91,6 +91,10 @@ impact is smaller than the document/cache indexing findings below.
## Finding 2: Narrow The Documented Empty-Validator-Chain Guarantee
**Status: Complete.** Architecture, configuration, pipeline internals, and the
active plan now distinguish intrinsic checks from configurable citation checks.
Documentation links and whitespace were checked; runtime behavior is unchanged.
Priority: P2. Relevant stages: 11, 38, 39, and 42.
### Evidence And Impact