Source systems
Operational records
Authority, recommendation, human decision, and execution records remain distinct.
Security & deployment
Independent assurance, outside the live decision path.
QAi connects the records needed to verify a consequential action. SIMBA resolves the authority in force, assesses evidence completeness, and reconciles the finding with the outcome that actually executed. The institution’s systems continue to govern and act.
Out-of-path operation · findings, not commands · independent verification
EVIDENCE FLOWSOURCE → ASSESS → VERIFY
Controlled integration
Bounded intake
Agreed read-only interfaces or controlled extracts define what QAi can observe.
SIMBA assessment engine
Deterministic assessment
Versioned authority, evidence completeness, and declared controls are evaluated in a fixed order.
Independent review
Verified outcome
The finding is reconciled with what executed and supported by portable evidence.
Operational boundaryThe live workflow remains independent of QAi availability.
Operating boundary
Two layers · one responsibility model
What QAi fixes by design. What the institution configures.
The assurance method stays consistent. The production operating model is agreed for the institution’s environment and supported by the relevant implementation evidence.
Fixed architectural commitments
These define the product boundary across deployment models.
- 01Out-of-path operation with findings, not commands
- 02Distinct authority, recommendation, attributable human decision, and execution records
- 03Versioned, deterministic assessment through SIMBA
- 04Observation completeness and reconciliation with the executed outcome
Institutional configuration
These controls are made explicit before representative records are connected.
- 01Source access and the evidence QAi may receive
- 02Hosting, identity, encryption, and key ownership
- 03Residency, retention, deletion, and workload isolation
- 04Support access, incident responsibilities, audit, and exit controls
Evidence that can leave the platform
Review the evidence without trusting the interface.
An exported evidence pack carries the records, declared gaps, canonicalisation method, member digests, manifest digest, and recomputation steps.
Precise assurance boundary. Integrity verification establishes whether the exported objects still match the captured pack. Source completeness, accuracy, lawful basis, and legal sufficiency remain separate questions.
01Canonical recordsDeclared serialisation rules travel with the pack.
02Member digestsSHA-256 digest for each included record.
03Ordered manifestOne pack digest covers the ordered member set.
04Offline verificationPublished steps support independent recomputation.
Start with one consequential workflow
Examine its evidence boundary and deployment requirements.
We will identify the source records, expected population, operational responsibilities, and review outputs required for the action.