The method
Not magic.
Machinery.
Five stations, in order, every time. The reason Palm’s output can face an auditor is that nothing in the line ever guesses.
Your code enters whole —
read where it lives.
Parsed and graphed —
structure, not statistics.
Out the other end:
verified rules, with addresses.
Ingest · parse · graph · extract · verify
Five stations, zero guesses
Ingest reads every artifact — programs, copybooks, JCL, screens — inside your perimeter. Parse builds a true syntax model of each dialect; there is no “probably” in a parser. Graph assembles the full dependency web Palm Key exposes.
Extract walks that structure to lift each business rule with its exact source span — 50,000+ lines held in a single deterministic pass. Verify replays the line: identical input, identical output, run after run. In benchmark this method lands around 95% extraction accuracy, with 100% lineage by construction.
AI assists where judgment helps — naming, summarizing, classifying — but it is bolted to the structure, never substituted for it. That’s the difference between an answer and an opinion.