Independent of Jack Henry.
Map the reach of a supplied core change.
A release description can leave the affected work unclear. Prepare the supplied files, candidate dependents and retest questions for the institution's engineer to review before release.
The review question and the inputs.
For an engineering or operations owner with a core-adjacent change on the release calendar.
- Permitted before and proposed source text
- The filenames and selected release boundary
- Declared calls, file relationships and candidate dependents
- The change owner, engineering reviewer and supplied retest requirements
The file your team keeps.
A six-column file of the supplied change, evidence and open questions A before-and-proposed file register with owner roles
Six columns: Use, Where it runs, Data it can touch, Owner, Evidence on hand, Question still open. The institution fills the decision line.
How the core-change reach works.
Fix the supplied release boundary
List the before and proposed files and the release question. Separate supplied text from files the institution has not included.
Compare the supplied text
Prepare the changed instructions and stated file relationships. Keep source versions and filenames beside the comparison.
Queue candidate dependents
List heuristic candidate relationships for the engineer to check. Put a retest question beside each relationship whose effect remains open.
Accept the release questions
The institution's engineer accepts or rejects the candidate relationships and confirms the retest plan. The change owner records the institution's release decision.
Read a short evidence row.
Illustrative inputs, not a client.
| Use | Where it runs | Data it can touch | Owner | Evidence on hand | Question still open |
|---|---|---|---|---|---|
| Review of a supplied core-adjacent change | The declared environment; supplied files reviewed as text | Permitted source text, with restricted data excluded | Institution change owner and engineering reviewer | Before and proposed files; candidate dependents and retest questions | Which candidate relationships will the engineer accept before release? |
Decision: ________________________
Who signs off on the file.
The institution's engineering reviewer accepts the dependency and retest scope; its accountable change owner records the release decision.
Two to four weeks. Timing starts when the agreed inputs and review owner are available.
The method and scope.
Fee fixed in writing after one working session.
A review prepares a file. It does not certify compliance, give a legal opinion or connect to a core.
Start with the AI review on the calendar.
Bring the review question, deadline and accountable role. We reply to business inquiries within one business day.
Request a call Email info@llmsquared.com