Supplied
A source, result or declaration entered by the user. Its presence does not establish authenticity or permission.
Method and boundaries
The file makes evidence inspectable.
The institution decides whether the supplied sources, tests and result are sufficient. The preparation method keeps the record and the unanswered question visible.
The four review questions.
| Review | What the method prepares | What the reviewer decides |
|---|---|---|
| Vendor renewal | Entered USD terms under common activity; quote differences and notice questions. | Are the actual terms correct, sufficiently complete and acceptable? |
| AI pilot | Required cases, supplied results, failures, exclusions and matched effort where supported. | Are answer quality, source sufficiency and the use boundary acceptable? |
| Procedure | Supplied source versions, literal evidence lines and separately supplied answer-review records. | Which version controls and which proposed answers may staff use? |
| Core change | Supplied before and proposed files, exact changes and candidate filename references. | What actual behavior and interfaces must be tested before release? |
Three states that must stay separate.
Prepared
The method produced its current report from explicit inputs. That report may contain failures, gaps and blocked work.
Reviewed
A named human records a supplied review decision. The institution still determines that person's authority and whether the evidence is sufficient.
Fingerprints compare supplied records.
A source fingerprint lets you compare the bytes or values supplied to a method. It is not an identity credential, source-origin proof, signature or proof that a person reviewed the file.
Missing cases remain missing. Unknown terms stay unknown. Literal references are candidates. A provider's Pass stays separate from human acceptance. Preparation and output checks do not turn any of those statements into institutional approval.
Work the public methods actually perform.
The browser tools use explicitly entered text, metadata, CSV or JSON. Accepted formats and bounds are shown inside each tool. Sources and exported reports can contain the full supplied input, so inspect the complete file before sharing it.
Local command and assistant-source packages reuse bounded preparation methods. Downloading a package, installing it, invoking a model and receiving a directory listing are separate outcomes.
Inspect a working method Read schemas, exports and source limits Check current assistant package status
Limits that travel with the file.
These methods do not connect to a core, compile or execute institution changes, take a financial action, verify identity, certify compliance, give a legal opinion or establish achieved savings. Source-use declarations and human review records are not independently authenticated.
The credit-union source methods identify Symitar and PowerOn as source environments. LLM Squared is independent of Jack Henry and is not endorsed by it. Bank change review concerns the bank's own permitted reports, scripts and file handoffs.
There is no production remote MCP endpoint here. Grok web and remote connectors are unavailable. No account, cloud history, comparison database, monitoring or scheduled reminders is provided by these public methods.
Change the evidence. Review the decision again.
Save the original file and version references. When a source, term, case or use boundary changes, identify the affected review questions and ask the responsible reviewer to inspect them. A previous acceptance must not quietly become a new one.
Inspect the local review-refresh method Read processing and sharing boundaries
Start with the decision already on your calendar.
Bring the decision, deadline and accountable owner in general business terms. We agree the workflow, permitted sources, review responsibilities and exclusions before work begins.
Scope and fee are fixed in writing after one working session.
Prepare a scope request or email info@llmsquared.com. Do not attach confidential sources to an ordinary inquiry.