The shortest honest route
from NO-GO to live.

Second factor on every internal login

Can a stolen password alone reach production data?

Until MFA is enforced, one credential leak is a full-tenant compromise and no other control compensates.

12 blocking · 20 linked · 4 registers

• B-1MFA enforced for all internal staff
• G-05Authentication and privilege
• SAF-06Vendor credential expiry after dispatch triggers defined risk action.
• IAM-02MFA required for internal and privileged users.
• DEP-01Dev, staging, Trial and production are separated by account/data/secrets/storage/integrations.
• BOARD-03MFA / privileged actions

Malware scanning and quarantine before trust

Is an uploaded lender document scanned before anything reads it?

An unscanned document is processed by twelve automated roles; a hostile file reaches every downstream consumer at once.

19 blocking · 27 linked · 4 registers

• B-3Licensed AV engine behind the quarantine gate
• G-06Document safety and integrity
• G-10Security readiness
• AIS-02Uploaded documents/notes are treated as untrusted data, not instructions.
• PRV-06Production error/logging avoids tokens and sensitive payloads.
• DOC-03Malware scanning and quarantine precede preview/index/AI use.

Database-level audit immutability

Can the application account rewrite its own audit history?

Hash chaining detects tampering only if the rows cannot be replaced wholesale; INSERT-only grants make the chain load-bearing.

7 blocking · 19 linked · 5 registers

• B-4INSERT-only grants on audit tables
• AIW-04Model/provider/version, prompt/workflow and fallback are logged.
• IAM-07Trial resume, AI enable, role grant, restore and compliance override require step-up/reason/dual approval as appropriate.
• AUD-03Application audit writer lacks UPDATE/DELETE at DB level.
• RISK-08Audit history can be mutated through database privileges
• IAM-04Require step-up authentication and/or dual approval for AI kill-switch changes, Trial resume, privilege grants, vendor re-eligibility, destructive export, restore and future financial actions.

Rehearsed destructive restore

Has a replacement environment ever been restored and reconciled?

Backups that have never been restored are an assumption. RTO and RPO are unknown numbers until the drill is executed.

44 blocking · 68 linked · 7 registers

• B-2Backup and restore drill completed
• B-6Off-platform backup exists
• G-08Backup and restore
• G-14Ownership and recovery access
• SAF-03Cancellation semantics are safe before dispatch, during active work and after custody.
• SAF-05Changed lender instructions are versioned, authorized and propagated.

Durable scheduling and freshness monitoring

Does anyone find out when the unattended sweeps stop running?

Idle-to-zero serverless scheduling fails silently; deadlines pass with no actor and no alert.

28 blocking · 51 linked · 5 registers

• B-8Named owner receiving scheduler alerts
• SAF-06Vendor credential expiry after dispatch triggers defined risk action.
• SAF-08System/AI/scheduler/database outage fails safe for active cases.
• IAM-03Session idle/absolute expiry, rotation and logout revocation are enforced.
• IAM-06Account recovery and break-glass are secure, monitored and company-owned.
• PRV-04Sensitive data-flow map covers browser, URL, logs, AI, email, storage, exports, APIs, backups and monitoring.

Server-side tenant and organization isolation

Is isolation enforced below the UI on every path?

UI filtering is not a boundary. One missed server-side check crosses lenders, which ends the trial outright.

20 blocking · 36 linked · 4 registers

• G-04External isolation
• AIS-01Direct/indirect prompt injection cannot change authority/state or leak tenant data.
• AIS-03External independent AI authority assessment completed.
• TEN-01Tenant scope is derived server-side from trusted identity.
• TEN-02Real lender and vendor identities cannot access another organization.
• TEN-03Documents, previews, search, exports, errors and caches are tenant-safe.

Authority boundary proven under adversarial load

Does the system refuse, rather than merely log, a prohibited AI action?

Confidence must never create authority. Refusal has to be demonstrated per prohibited action, not asserted once.

17 blocking · 75 linked · 5 registers

• B-1MFA enforced for all internal staff
• B-4INSERT-only grants on audit tables
• B-10External adversarial review
• ARC-04Material state/event/audit/deadline effects commit atomically.
• SAF-08System/AI/scheduler/database outage fails safe for active cases.
• AIS-01Direct/indirect prompt injection cannot change authority/state or leak tenant data.

Second operator able to run the system

Can anyone but the builder deploy, diagnose and restore?

A bus factor of one is an availability control failure; the restore drill is worthless if only one person can execute it.

8 blocking · 13 linked · 4 registers

• G-14Ownership and recovery access
• INC-03Vendor-account compromise runbook covers detect, revoke, scope, notify, correct and resume.
• OWN-03Second engineer can deploy, diagnose, pause and restore from documentation.
• DOCS-01One master document index identifies authority, owner, version and supersession.
• OWN-02Cloud accounts, billing, DNS, certificates, data stores, object storage and backups are company-controlled. Proof: account inventory, owners, billing/recovery contacts and access review.
• OWN-03Secrets, signing keys, integration credentials and encryption keys are inventoried and recoverable without a personal account. Proof: secret-store inventory, rotation and break-glass drill.

Trial claims earned from trial data

Is any published number derived from synthetic fixtures?

Efficiency claims measured in the same session that produced them are not evidence; separation must be visible.

10 blocking · 18 linked · 4 registers

• B-9Baseline methodology agreed
• PRV-06Production error/logging avoids tokens and sensitive payloads.
• SCH-02Independent external freshness monitor alerts after missed cadences.
• BCR-02Destructive restore drill meets approved RTO/RPO.
• MET-02Pre-Trial baseline captures touches, cycle times, exceptions, documents, invoices and labor.
• MET-03Trial data dictionary defines formula, events, exclusions, cohort and owner.