What you will build
A controlled change record showing which outputs were affected, rerun and approved after a source update.
Inputs and ownership
- Versioned source
- Retained claim trail
- Review owner
Blueprint
This illustrates the governed fields to define during onboarding; it is not a public production API contract.
{
"source_change": "policy.refunds.eu@v4 -> v5",
"impact_query": "dependent_claims",
"action": "rerun",
"retain_comparison": true
}Build it step by step
- 01
Publish the new source version
Keep the previous version identifiable while the replacement enters review.
- 02
Locate dependent claims
Use retained claim bases to find outputs shaped by the old version.
- 03
Rerun the governed path
Recompose affected answers under the same intent and boundary conditions.
- 04
Approve the change set
Review differences, record the owner and retire the superseded source.
Prove the governed path
- The permitted path produces an answer from approved evidence.
- An unsupported request returns an explicit governed outcome.
- Every material claim resolves to a known knowledge unit.
- The decision can be rerun after a source version changes.