Every batch job submitted to an IBM mainframe carried a JOB statement: submitter name, billing account, job class, log routing, completion notification destination. The machine didn't trust your presence. It trusted the record. You declared who you were, who paid, and where the evidence went before anything ran.
Then GUIs put a human body in the loop, and the formal record quietly atrophied. Why mandate a billing identity when someone's visibly sitting at the keyboard? Why route completion logs when the person who clicked is right there to notice failure? The body became the audit trail. Nobody decided this explicitly. It just happened, the way institutional memory always erodes: one shortcut at a time, each one perfectly reasonable in isolation.
This worked until automation went unattended again. When RPA vendors built robots that ran overnight with no one watching, they had to re-derive what batch shops had enforced decades earlier: dedicated robot accounts, credential vaults, queue schemas, exception reviewers, retention policies. They didn't get there by reading old JCL manuals. They got there because unattended work surfaces the same questions every time, and a warm body in a chair was never actually an answer to any of them.
What batch required at submission (JCL JOB statement):
- Submitter identity (programmer name)
- Billing account (department or person charged for resources)
- Job class and processing priority
- Log routing and message level
- Completion notification back to submitter
What RPA re-derived for unattended robots:
- Dedicated robot accounts (not personal logins)
- Credential vaults (CyberArk, HashiCorp, Azure Key Vault)
- Queue schemas validating work item structure
- Transaction lifecycle tracking per item
- Reviewer assignment for failed or abandoned items
- Audit logs retained 6–24 months
The pattern: When a human is present, organizations let the body absorb accountability informally. When the human leaves, every system rebuilds the same formal apparatus: declared identity, scoped authority, structured evidence, assigned review. Batch had all of this. GUIs let it atrophy. RPA spent years painfully reconstructing it.