Checklist / AIGIS resources

A checklist for reviewing Salesforce AI governance before model exposure.

The strongest first AIGIS review starts with Salesforce because it is the production proof path. Use this checklist to decide whether a workflow is ready for a governed AI review.

Talk to the founder More resources

Executive read

The short version, before the deep dive.

Start with one real Salesforce workflow that has permission-sensitive data.

Confirm object, field, and live record access before prompt construction.

Require evidence of stripped fields and denied records.

Use ServiceNow and SAP only as disclosed design-partner co-development scope.

Analysis

What matters

What to inspect first

List the Salesforce objects, fields, and records the workflow needs. Then mark which fields are sensitive, role-dependent, or audit-relevant.

AIGIS is strongest when the review can show what the model received, what was excluded, and which permission checks shaped the answer.

What makes a strong proof workflow

The workflow should be narrow, valuable, and permission-sensitive. A good example is an account, case, or opportunity question where different users have different record or field visibility.

If the workflow needs ServiceNow or SAP, describe that as co-development scope with asymmetric enforcement rather than parity with Salesforce.

Resource packet

Turn this into a review worksheet.

Evidence packet

Permission-Provenance Evidence Packet

Capture user context, system of record, enforcement tier, stripped fields, model route, response, hash marker, and fallback notes.

Salesforce is the production proof path. ServiceNow and SAP are design-partner co-development paths with asymmetric enforcement that must be disclosed in diligence.

Get the packet

Keep reading

Related resources.

Use case