Ask your mainframe
anything.
Sessions, runbooks and COBOL become one retrievable memory. Every answer arrives with its sources attached.
NSB.SETTLE skips to the recovery step and flags the batch for manual review.1 It does not retry automatically: the retry flag is owned by CARDHOLD, not the settlement job.2,3
The people who know how it works are leaving.
Knowledge lives in people
The engineer who knows why the settlement job retries twice is one retirement away from gone.
Documentation drifts
Runbooks describe the system as it was designed. Production has moved on without them.
Search doesn’t help
Grep finds the string. It won’t tell you what breaks three jobs downstream.
Four steps from tribal knowledge to a cited answer.
Capture
Expert sessions, runbooks, specs and code go in. Chunked, cleaned, embedded.
Connect
Relationships between programs, jobs and datasets become an explicit graph.
Retrieve
Top-k search, then graph hops. Only the evidence the question actually needs.
Answer
With its chunks and graph facts attached, or an honest “not in scope.”
Retrieve the evidence, not the estate.
Both figures are real Bedrock input-token counts on a synthetic MVP corpus. A reduction in context sent, not a cost claim.
Nothing to take on faith.
Each answer carries the chunks and graph facts it was built from. When the evidence isn’t there, Ayori says so instead of guessing.
Deployed per client
Runs against your estate, not a shared multi-tenant service.
Every answer sourced
Chunks and graph facts travel with the answer, fully auditable.
Refuses when unsure
No evidence, no answer. Ayori tells you what it doesn’t have.
Questions we get.
Does Ayori need our source code?
Only what you point it at: sessions, runbooks, specs and the COBOL/JCL in scope. Nothing leaves the deployment.
Where does it run?
Packaged and deployed per client, against your estate. Not a shared service.
What happens when it doesn’t know?
It refuses. Answers are constructed from retrieved evidence only, so a gap in the corpus shows up as a gap in the answer, not a guess.
Are the numbers on this page from production?
No. They come from a synthetic MVP corpus: fictional test data measured by a reproducible harness. Cost figures are calculated token-level Bedrock costs, subject to AWS invoice verification.
What do you need from us to start?
A scoped estate, a few expert sessions to capture, and someone who can say which systems matter most.