Whatever the program has, in any state of disorder, feeds the scan: charters, slide decks, requirements documents, schedules, meeting notes, rosters. Shanta sorts what it is given, shows the evidence behind every call it makes, and once it has seen enough, assembles a clickable picture of how the program actually runs, showing where the program's own record contradicts its stated process.
Any-artifact intakeThe scan meets the program where it is: no data call, no template, no prerequisite hygiene. Disorder is the expected input.
Evidence-backed classificationEvery call the AI makes shows its evidence, and a person can reverse any of them.
Redesign, not just diagnosisThe diagnosis is the midpoint. A redesign module generates the to-be workflow: the operating cast in general language, the program-specific changes to artifacts, actors, and events, and the technology stack that supports them.
An analyst you can interrogateA built-in analyst chat lets the program question both diagnosis and redesign, with attachments feeding back into the scan.
Files stay localFiles are read locally, so nothing leaves the machine the scan runs on.
Whatever the program has goes in. An evidence-backed read of how it actually runs comes out. Notional.
The four planes it reads
Execution spineHOW WORK MOVES
Governance loopHOW DECISIONS CLOSE
Record topologyWHERE THE TRUTH LIVES
Measurement loopWHAT GETS COUNTED
Run across a portfolio of program offices, the scan becomes a standing, evidence-based read on execution waste; run on one program, it shows that program where it should be going next.
The pair · Diagnose, then reorient
The diagnosis is the midpoint, not the product.
Shanta shows a program where it actually is and where it should be going. Outcome Studio is the turnaround that follows, moving the program from tracking effort to delivering results. Each works on its own or paired with the other.