Record a validation (G2)

Steps

1. Open the G2 record, for example customer assistant, G2 re-validation. It holds the report, the findings, the unexamined set, scope limits and dissent, each as a record.

2. Under Attach the re-validation report on the open G2, choose the file and Attach and hash. The file is hashed and timed when you attach it.

3. Record each finding with its severity on the open G2. The owner responds, and a finding closes only with its evidence.

4. Under What this validation did not examine, list each item and why. An item leaves the set only with how it was examined since.

5. Under Decision, sign G2, return it, or record dissent. To sign, confirm you examined what the report says you examined, and that the unexamined set is complete.

Good to know

• Only the Validator signs G2, closes findings or records dissent. The owner responds to findings; the CRO decides at G4.
• Dissent is its own record, with an escalation route that does not run through the approver, for example to Internal audit.
• Findings are never resolved away before closure. Each stays on the record with the owner’s response.

Where in the product

• G2 gate record
• Gates

These open the prototype, on fictional institutions. People are shown as roles.

Related guides

• Sign a gate with a reason

  Read the gate record and its evidence, then sign, return or reject it with a reason, as the named approver.

• Re-assert evidence before it lapses

  As the model owner, confirm an entry is still true, say what that rests on, and sign before the interval runs out.

• What GovernanceOS records, and what a gate is

  The record of each AI decision: five gates, one named approver at each, and evidence hashed as the gate passes.