External acceptance records
An acceptance record says who reportedly accepted which evidence or bundle, for which purpose, under which policy version. It is cited, not made by NovusLens, and it does not certify independence.
Example. An internal audit reviewer downloads the assurance bundle for Grid Operations, checks its manifestRelease manifestThe file recording the exact software versions and fingerprints used for a NovusLens release candidate. Installation checks compare files against it. hashHashA fixed-length fingerprint calculated from content. Comparing fingerprints helps detect changes and match records., and records in their own system that the bundle satisfies control 7.2 of the firm’s policy, version 3. Their exporter sends that decision as an acceptance record. The panel then shows: accepted by the internal audit function for control 7.2 under policy v3, referencing bundle a1b2… — beside the findingFindingA difference in the records that needs a decision. It includes its sources and can describe a slow handoff, disputed fact or missing owner., not as part of it. If the observation behind the finding is later corrected, the acceptance line reads requires review: a referenced record changed.
What to inspect. Who accepted, under which policy version, and whether every referenced record is still current. Ask the accepting function whether a changed reference changes their decision; NovusLens does not decide that for them.
It sits beside the current support assessment, never inside it. When later evidence changes the support behind an accepted result, the acceptance is not erased: it is shown as requiring review, with its references marked changed or unavailable.