Inspect the work before sharing a source
Read the evidence, corrections and limits. The examples below are fictional worked scenarios, not clients, testimonials or measured engagement results.
Fictional scenario / Renewal
Trigger: A renewal includes an AI feature. The original sources leave terms and review ownership open.
File: Same-activity fee calculation, source mappings, notice record, a fictional reviewer determination and retained AI failures.
Decision: Narrow the question. Bring the bounded account-service model to institution consideration while keeping the AI feature outside approval.
Fictional scenario / AI pilot
Trigger: A test export appears to support a pilot. The required-case register tells a different story.
File: Six retained rows and four required cases. Failed/later Pass, Error, Invalid, an excluded row, an unresolved row and missing case004 remain.
Decision: Keep institution acceptance pending. Assign the unanswered cases and retain the original attempts.
Fictional engagement archetype / Procedure
A COO brings two versions of a procedure and the questions staff ask. The review records the supplied versions, which source the institution declares controlling, conflicting answers and the named reviewer. Missing authority remains an open issue.
This describes the intended file. It is not an account of work for a customer.
Fictional engagement archetype / Core change
An engineer brings supplied versions of a change and its candidate dependents. The review keeps the before and after, literal file matches, owners and retest questions. Credit unions may use Symitar files; banks use their own reports, scripts and file transfers.
This describes the intended file. It is not a compiled release or a customer result. LLM Squared is independent of Jack Henry; no endorsement is implied.
| Method | Recorded version | What the record establishes |
|---|---|---|
| Vendor quote and renewal calculations | 1.2.0-rc.1 | The second fictional chapter was replayed with the retained deterministic engine. Its inputs and complete outputs are downloadable. |
| Pilot evidence preparation | 0.1.0 | The original six-row fictional export and required-case register remain retained with pending institution acceptance. |
| Evidence Desk | 0.6.0 | The current local package is described on the assistants page. Download, native invocation and directory listing remain separate. |
Read the tool changelog Inspect versions and installation checks
Calculation and retained-input checks establish the bounded method behavior. They do not establish authentic sources, customer acceptance, certification, achieved savings, identity verification or production core execution.
The first working session agrees the workflow, allowed sources, review responsibilities and exclusions. Scope and fee are fixed in writing after one working session.
