Defensible AI Library
51 governance documents that fill themselves from your records. Choose one and sign up; once your access is approved, it opens ready to fill.
E-23 Studio, 9 documents
OSFI Guideline E-23
Where the client stands against OSFI E-23, the gaps, and each requirement traced to an artifact.
E-23 twelve-question checkWhere the client stands on six themes, as a position.
- Used by
- Compliance lead, CRO
- Fills from
- Register
Scope self-checkWhich systems E-23 reaches.
- Used by
- Compliance lead, CRO
- Fills from
- Register
Gate record, G1 to G5One record per gate, one named approver.
- Used by
- Compliance lead, CRO
- Fills from
- Gate states
BOE DeclarationThe declaration made for each system in scope.
- Used by
- Compliance lead, CRO
- Fills from
- Register
Engineering review questions PEVG and PARAThe review questions asked of each system.
- Used by
- Compliance lead, CRO
- Fills from
- Register
Vendor assessmentThe AVRF questionnaire, set to E-23.
- Used by
- Compliance lead, CRO
- Signed by
- CRO, at the institution
- Fills from
- Vendor records
Trigger registerEvents that re-open a system before its date.
- Used by
- Compliance lead, CRO
- Fills from
- Register, incidents
Gap planFrom the check's gaps to owners and dates.
- Used by
- Compliance lead, CRO
- Signed by
- Compliance lead, at the institution
- Fills from
- The twelve-question check
Traceability binderEach E-23 requirement traced to this client's artifact.
- Used by
- Compliance lead, Internal audit
- Signed by
- Compliance lead, at the institution
- Fills from
- Every E-23 document
Set up the program, 9 documents
CADRE™, the AI Governance Operating Model
The charter, who decides what, the meeting records and the escalation paths.
Governance charter and decision rights CADREMandate, scope, one accountable person per decision type.
- Used by
- CRO, Compliance lead
- Signed by
- CRO, at the institution
- Fills from
- Register owners
Operating rhythm recordsWeekly operations, monthly risk, quarterly board, annual refresh.
- Used by
- CRO, Compliance lead
- Fills from
- Meeting records
Escalation pathsIncidents, human-review tiers and gate disputes.
- Used by
- CRO, Compliance lead
- Signed by
- CRO, at the institution
- Fills from
- Charter
AI acceptable use policyWhat staff may and may not do with AI tools.
- Used by
- CRO, Compliance lead, CISO
- Fills from
- Your answers
Role descriptionsThe office's named roles.
- Used by
- CRO, Compliance lead
- Fills from
- Your answers
Office launch checklistStanding the office up.
- Used by
- CRO, Compliance lead
- Fills from
- Your answers
First 90 days planThe first quarter's milestones.
- Used by
- CRO, Compliance lead
- Fills from
- Your answers
Exception request and registerTime-boxed relief from a policy clause, with its controls.
- Used by
- CRO, Compliance lead
- Fills from
- Your answers
Committee charters and agendasEthics committee, validation forum and their agendas.
- Used by
- CRO, Compliance lead
- Fills from
- Your answers
Assess a system, 8 documents
AI Data Governance Framework™ and MESA MRM Framework™
Who a system affects and how, what it is built from, and where its data comes from.
AI impact assessmentWho is affected, how, and what controls it.
- Used by
- Model owner, Data lead, Compliance lead
- Signed by
- Model owner, at the institution
- Fills from
- Register
Data governance viewData classes, lineage and residency, by system.
- Used by
- Data lead
- Signed by
- Data lead, at the institution
- Fills from
- Register
Model cardWhat a model is for, and not for.
- Used by
- Model owner, Data lead, Compliance lead
- Fills from
- Register
AI bill of materialsModels, adapters, knowledge sources and tools.
- Used by
- Model owner, Data lead, Compliance lead
- Fills from
- Register, vendor records
Data protection impact assessmentPersonal information in the system.
- Used by
- Model owner, Data lead, Compliance lead
- Fills from
- Your answers
Data lineageWhere each input comes from.
- Used by
- Model owner, Data lead, Compliance lead
- Fills from
- Your answers
Data catalog specificationWhat each dataset holds.
- Used by
- Model owner, Data lead, Compliance lead
- Fills from
- Your answers
Policies: development, data, retention, anonymizationThe policies a system is built under.
- Used by
- Model owner, Data lead, Compliance lead
- Fills from
- Your answers
Pass a gate, 5 documents
Five-Gate Deployment Model™ and MESA MRM Framework™
Everything a gate needs, in one pack, and the validation behind it.
Deployment gate review pack Five-GateThe gate's checklist, artifacts and record draft.
- Used by
- Model owner, Validator, CRO
- Signed by
- Model owner, at the institution
- Fills from
- Register, files
Validation reportValidation, its unexamined set and dissent.
- Used by
- Validator, Model owner
- Signed by
- Validator, at the institution
- Fills from
- Register
Bias audit reportTests by group, before the gate.
- Used by
- Validator, Model owner
- Fills from
- Your answers
Drift monitoring configurationWhat is watched after release, and the thresholds.
- Used by
- Model owner, Validator, CRO
- Fills from
- Your answers
Model retirement checklistClosing a system down.
- Used by
- Model owner, Validator, CRO
- Fills from
- Register
Assess a vendor, 7 documents
AVRF™ and Cross-Border AI Architecture Patterns™
The questionnaire out, the answers in, findings, conditions and a named decision.
AI vendor assessment AVRFIssue, collect, findings and a named decision.
- Used by
- Procurement lead, CISO, Compliance lead
- Signed by
- CRO, at the institution
- Fills from
- Vendor records
Vendor due diligence questionnaireA ten-section questionnaire for AI vendors.
- Used by
- Procurement lead, CISO, Compliance lead
- Fills from
- Your answers
RFP for AI vendorsAsking vendors the right questions up front.
- Used by
- Procurement lead, CISO, Compliance lead
- Fills from
- Your answers
AI contract clausesThe clauses AI contracts need.
- Used by
- Procurement lead, CISO, Compliance lead
- Fills from
- Your answers
Vendor comparisonVendors side by side, in words.
- Used by
- Procurement lead, CISO, Compliance lead
- Fills from
- Vendor records
Vendor management policyHow vendors are chosen and kept.
- Used by
- Procurement lead, CISO, Compliance lead
- Fills from
- Your answers
Transfer risk registerData that crosses a border, and on what basis.
- Used by
- Procurement lead, CISO, Compliance lead
- Fills from
- Your answers
Handle an incident, 5 documents
AIRP™, the AI Incident Response Protocol
From the first signal to the review, with every notice drafted.
AI incident pack AIRPTimeline, reconstruction and the review.
- Used by
- CISO, CRO
- Signed by
- CRO, at the institution
- Fills from
- Incident log
Severity classification guide, P0 to P4How bad, and how fast.
- Used by
- CISO, CRO
- Fills from
- Your answers
Runbook: bias detected in productionThe first hours, step by step.
- Used by
- CISO, CRO
- Fills from
- Your answers
Post-incident reviewWhat happened, why, and what changes.
- Used by
- CISO, CRO
- Fills from
- Incident log
Notices: internal, regulator, customer, mediaEvery notice an incident may need.
Sharia review, 3 documents
SACF™, the Sharia AI Compliance Framework
Technical validation and Sharia review, run as two tracks and closed together.
Sharia dual validation SACFBoth tracks, prepared for the bank's own sign-off.
- Used by
- Sharia board liaison, Validator
- Signed by
- Sharia board liaison, at the institution
- Fills from
- Register
Halal data certification checklistData sourcing checked against Sharia principles.
- Used by
- Sharia board liaison, Validator
- Fills from
- Your answers
Sharia data review checklistThe Sharia board's review of data use.
- Used by
- Sharia board liaison, Validator
- Fills from
- Your answers
Prove it, 5 documents
MESA Framework™
The position, the board's quarterly briefing, the mapping and the audit trail.
Maturity position report MESAWhere the client stands on four altitudes, in words.
- Used by
- CRO, Compliance lead, Internal audit
- Signed by
- CRO, at the institution
- Fills from
- Readiness
Board briefingCounts, what changed, the decisions asked.
- Used by
- CRO
- Signed by
- CRO, at the institution
- Fills from
- Register, incidents
Regulatory mapping matrixEach control against the rows it answers.
- Used by
- CRO, Compliance lead, Internal audit
- Fills from
- Regulation rows
Audit evidence checklistWhat an auditor will ask to see, and where it is.
- Used by
- Internal audit
- Fills from
- Register, files
Examiner binderThe traceability binder, ready for an examiner.
- Used by
- Compliance lead, Internal audit
- Signed by
- Compliance lead, at the institution
- Fills from
- Every kit
Try fewer words, or another role.
Before you sign up
- See where you are: four questions, a position on four altitudes, never a score
- Regulation rows: each instrument, its regulator, its status and the date it was checked
- Plain words: the terms the documents use
- Learn: one short path per role
- Verify a pack: for examiners, with a read-only key the institution issues
Learn more about the library
Each document opens filled from your records. Every field says whether it was typed or produced, and what is missing says so.
Practitioners open every document. The roles shown are the institution’s people who use or sign each one.
The E-23 Studio is built for OSFI Guideline E-23. Every other kit fills from your regime profile: Quebec AMF, US federal and state, and six GCC central banks.
Sign-up asks for your work email, a six-digit code, then your name, role and country. A work address needs no card.
Your documents are stored in Canada. Exports are your filled documents, with your name and the date.
Signing up does not create an account for your institution. Its workspace is claimed by its own administrator, through its own sign-in.

