Review proposed by local AI
Ask a reviewer to compare source observation timestamps and clock settings.
Bolt · Internal research · 11 October 2026
A small technical proof built around fictional order-management, warehouse and carrier records. Real local-model inference chooses a restricted next review step; independent code checks prevent ungrounded event references from being accepted.
Traceable example results
The model is Qwen 2.5 1.5B, run locally with Ollama. The rule engine detected three conditions, then the model selected a permitted reviewer step for each. A fourth order needed no model review.
Ask a reviewer to compare source observation timestamps and clock settings.
Ask a reviewer to compare source observation timestamps and clock settings.
No predefined exception rule matched this fictional order; no model call was needed.
No automated actionAsk a reviewer to compare source observation timestamps and clock settings.
What these results do — and do not — show
The local language model makes an advisory choice among predefined review steps, and the program validates its event citations against the triggering rule. The first unconstrained response in development referred to an irrelevant event ID and was rejected. The final three successful responses all suggested comparing timestamps, so this is not yet evidence of sophisticated differentiated AI diagnosis.
Independent customer measurements, production data connections, operator authentication, protected audit storage and commercial ROI remain unverified. The tests measure only the behavior of the supplied examples. The separate proprietary Bolt macOS application is not published as part of this illustration.
Evaluation proposals begin with a written description of a bounded operational problem and synthetic/non-sensitive examples. No production records, account access or confidential documents are needed for an initial enquiry.
Omar Baró · Unfire · Spain · Initial communication by email only.