A model, component, or configuration change can invalidate the basis of an earlier result. Use a follow-on Assessment to make the changed basis and reopened work explicit.
New evidence and a decision for the changed version
Try this with the assistant
Add the relevant saved records to your chat, then adapt this request to your work.
Help me prepare a follow-on Assessment for this changed product version. Summarize what changed, which facts and requirements can carry over, and which evidence depends on the earlier configuration. Propose the work to reopen and explain each reason.
Identify the actual change
Describe the components or configuration that changed. If the configuration is the same and only the review objective differs, create another case for the existing version instead.
Inspect what carries over
Use Re-assess for a new version and review the carry-over list. Earlier facts, standards, plan, links, and reviews retain their context; version-dependent evidence starts open.
Re-establish the affected claims
Review carried requirements, prepare the necessary Runs, and inspect new results. A reference to earlier evidence remains useful only with an explanation of its applicability.
Make the next decision
Record the new scope, evidence, conditions, and gaps. Keep the earlier decision available so another reviewer can understand the progression.
