Chapter 70: The Approval in Two Columns
Judith opened the approval ledger and traced two initials from an unusual service description to a paid invoice.
I watched from the observation side of KRR's interview room Tuesday morning.
Judith Vale sat with her independent attorney and Samuel at the recorded table.
She had supervised accounts-payable processing, not executive strategy or vendor field operations.
Her evidence could explain procurement steps, approval roles, and invoice handling.
It could not reveal Vivian's or Andrew's complete intent, private understanding, or any unrecorded conversation between their offices.
The procurement custodian had delivered the native contract, scope changes, purchase order, and approval ledger directly.
KRR held controlled copies with source receipts, hashes, and access history that identified every authorized viewing session.
Bank account numbers, tax identifiers, personal contact fields, and unrelated vendor transactions were redacted.
No invoice amount appeared on the observation screen or public-scope worksheet.
Judith explained the ordinary public-relations purchase path first.
A department requested a standard service category, described its intended work, and identified an approved budget owner and procurement path.
Procurement checked vendor status, contract scope, and the required approval level.
Accounts payable later compared invoice fields with the purchase order and recorded service acceptance.
Payment closed the accounting step without proving why management wanted the work or what every approver understood about later execution.
The Grayfield service description did not fit the ordinary monitoring category cleanly.
It combined reputation monitoring with reference and relationship stabilization involving outside contacts.
That description triggered a higher approval path under the procurement rules then in effect because it extended beyond passive public monitoring.
Judith opened the native ledger row and identified two role columns.
One column belonged to the strategy office.
The other belonged to the chair office.
Each column contained an approving user's initials and a recorded approval time.
Judith could explain that both fields were required before procurement activated the scope change. She could not authenticate the approvers' mental states.
She could not testify that either approver read every task script later used by Grayfield.
She could not infer personal motive from an accounting control.
Samuel placed those limits beside the ledger before continuing.
The first approval allowed procurement to process the unusual service description.
The second satisfied the chair-office requirement attached to the scope category.
The purchase order then moved into active status through the ordinary system.
Accounts payable matched later invoices to that active order and service-acceptance entries.
The ledger proved process, roles, description, and recorded approvals.
It did not prove that every later call was separately reviewed by both offices.
It did not prove a single complete intent shared by every person in the chain.
Grant's written response preserved the company's ordinary reputation-management explanation.
KRR preserved the direct-contact language that made the description unusual.
Both positions would be tested against service logs, scope changes, and witness accounts.
I asked Dana whether the paid status could be described publicly.
She said only at the process level KRR eventually authorized.
The amount, banking details, and tax fields added heat without establishing responsibility.
I signed a participant acknowledgment that I would not publish or estimate them.
Judith then authenticated her own role in the historic workflow.
She had checked completeness and routing, not approved strategy or field language.
Her former position gave her access to the ledger but no authority over KRR's copy now.
The procurement custodian retained the source; KRR retained the controlled evidence set.
Samuel closed the amount field and left the two approval columns visible.
The initials created a route for further interviews and identity verification, not a shortcut around either requirement.
They did not replace those interviews.
The final scope-change row carried a dual-approval rule in plain text.
Strategy office approval alone could not activate it.
Chair office approval alone could not activate it either.
The Grayfield scope required both before the work could proceed.