How BankingX40 works
The operating question
Should this AI generated AML/KYC triage output be released, routed for verification, or blocked under the active governance contract?
The pipeline
Raw AI output
→ structured contract object
→ schema and rule validation
→ numeric governance state vector
→ QEIv15 structural boundary metrics
→ assurance profile threshold
→ final governance decision
→ replay / audit / SHA evidence
What QEIv15 does here
QEIv15 does not read banking text directly. BankingX40 first converts AI output into a structured governance state. QEIv15 then evaluates structural boundary signals such as evidence reserve, action pressure, uncertainty reserve, coherence, and boundary distance.
Simplified output
{
"final_decision": "REQUIRE_VERIFICATION",
"rule_only_decision": "RELEASE",
"rule_plus_qeiv15_decision": "REQUIRE_VERIFICATION",
"physics_changed_decision": true,
"reason_codes": [
"LOW_EVIDENCE_RESERVE",
"BOUNDARY_DISTANCE_TOO_SMALL"
],
"replay_available": true,
"audit_export_available": true,
"sha_attestation": "available"
}