Sign a gate with a reason

Steps

1. On Gates, find the gate that waits for your signature, with its due date.

2. Open the record, for example underwriting triage, G4. Read the conditions, the expiry, the rollback plan and each evidence artifact with its hash.

3. Under Decision, choose Sign G4 (the button names the gate), Return for remediation or Reject. Each is a signed decision with a reason; none is one click.

4. To sign, write the reason, tick that you have read the record and its evidence, and sign with your identity provider. The token is written to the chain, and the gate shows passed.

Good to know

• A draft never passes a gate. It needs a signed token from the named approver.
• A returned gate goes back to the owner with your reason, and stays on the chain as returned.
• If your identity provider does not confirm, no token is written and the gate stays a draft.
• A gate cannot pass while a record it needs is missing. The record names what is missing and who adds it.
• Only the named approver can sign, return or reject. Anyone else can read the record and every artifact.

Where in the product

• Gates
• Gate record

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

Related guides

• Record a validation (G2)

  Attach the report, record the findings, what was not examined and any dissent, then sign G2.

• Invite members and give gate authority

  The CISO invites people at the institution’s domain and gives each a role, with the gate authority it carries.

• 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.