gateIntegrity is the forensic integrity layer between gate logic and sealing. It is not a single gate, but a layer of helper functions every sector gate must import and call, closing four forensic vulnerabilities identified after the sector gates were deployed. Not a standalone customer gate, which is why it lives under Architecture, not in a sector dropdown.
Every row is a hard boolean check, not probabilistic scoring. A critical failure leads to block, a high severity failure to warn, everything else to pass.
| Reference | Checks | Severity |
|---|---|---|
| Trust-via-Caller-Boolean | verifySanctionsLive checks live against OFAC/EU/UN instead of trusting a boolean caller flag | critical |
| Bi-temporaler Override-Missbrauch | enforceSixEyesApprovalForOverride requires an approved SuspensionOverrideRequest with two independent approvals before any override takes effect | critical |
| Single Point of Trust und Zeitanker | markReceiptPendingAsyncTrustAnchors sets tsa_status and shamir_cosign_status until the RFC 3161 timestamp and 3-of-5 Shamir cosign complete asynchronously | high |
| Hardcodierter Schwellwertdrift | fetchDynamicThreshold reads the current, enforceable threshold from the rule history instead of using a stale constant | high |