Gates, not recommendations
Every Mechanus IQ finding becomes a permanent gate inside the dealership workflow. Three levels cover the full distance from “block this action” to “flag this for the next close review.” No policy manual. No training video. The enforcement sits inside the tool the operator already uses.
Blocks the action entirely. Cannot be completed without a logged override. Override requires a reason code, an authorized actor, and a permanent audit event.
Does not block. Pages the relevant operator in real time and logs the event. Used where the right call depends on context the system does not have.
Quiet by design. Flags events into a review queue for the next monthly close. Used where pattern review is the right cadence, not real-time response.
Action demo
The demo below is entirely client-side. Nothing is sent anywhere. The deal, the actors, the hashes, and the timestamps are fabricated for illustration. The UX matches the production gate surface, including the DP-override form and the permanent audit event entry.
Deal #2026-04188
2024 used truck, term 72 months, Lender B
No events yet. Submit the demo deal to the left to see the gate fire and the audit event get hashed and timestamped.
Gate lifecycle
Every gate is a first-class configuration artifact. Gate governance lives under the Mechanus IQ governance corpus alongside the lifecycle spec. Nothing about a gate is ad hoc.
01
A finding is converted into a gate spec. Spec includes the trigger condition, the level (hard / soft / audit), the actor paged or blocked, and the evidence schema.
02
Gate is compiled into the workflow engine. Deployment is audited; gates never get silently enabled or disabled.
03
Gate activity is tracked in the dashboard: events, overrides, false positive rate, time-to-resolve. Drift triggers review.
04
Hard gates can be manually overridden only by a configured authority, with a reason code and an actor identity. Every override is a permanent audit event.
05
Each event enters the hash chain and is TSA-attested. RFC 3161 trusted timestamping plus Hyperledger Fabric private-rail commit for institutional attestation.
06
When a gate has held the pattern steady for a configured window, it can be retired with owner sign-off. Retirements are audited too.
Next
Every gate event, every override, every anomaly becomes part of a hash chain anchored by RFC 3161 trusted timestamps. The evidence chain page walks through the architecture with a live in-page SHA-256 demo.
