The answer changed. Keep the reason.

01 — Ask within a permitted scope.

A reviewer asks why a component was selected. Nexus limits the intended search to that project's permitted design notes and test records.

02 — Recover the evidence.

Cortex should return the accepted decision, the cited test revision and the reason for selection. A newer test that disagrees remains visible alongside it.

03 — Propose a correction.

Menexus AIA could help describe the difference and draft a change. The draft is labelled as a proposal; it does not overwrite accepted history.

04 — Review and carry it forward.

An authorized reviewer checks the evidence and accepts or rejects the proposal. A later permitted reader should see the new state and the traceable path from the old one.

This is a fictional workflow describing intended behavior. It is not a customer result, a deployed integration or a completed acceptance test.