Access
Mail, SharePoint (or files), books system, spreadsheet workspace.
Reference install · Accounts Payable
Engagement to ops on one mapped world.
AP as a Foundations walkthrough: find the sources, run the transforms, land named objects (Useful Data), attach action types, require a ledger, then wire the I/O a human can sign — on the LLM they choose.
Why AP
Mail, files, books, and a board that never quite agree. The install puts those sources on one path so each bill has a place, a status, and a human sign-off.
Ready before agents run
Power user
Someone who will run the board, clear exceptions, and approve.
Sample pack
Real bills, vendor list, chart of accounts slice — enough to map truth.
Sign-off path
Who approves AP today — named before automation.
How AP walks the picture
1
Name sources
Inbox, file library, books, working board — what already runs.
2
Land files
Extract → Load into the house first. No transform-before-land.
3
Useful Data
Named objects: vendor, bill, line, decision — identity and rules.
4
Ledger + sign
Every action tracked; human approval remains human.
Phases
1
Ready
Access, samples, power user calendared.
2
Map
Sources and path drafted against real AP.
3
Install
House, transforms, ledger board, I/O artifact.
4
Transfer
They run it; we leave a system, not a slide deck.
Same spine for other modules — AP is the reference walkthrough.