Chapter 12: Open, Then Closed
Issue Seventeen existed for nine days, and then someone changed one word without closing the facts beneath it. The register labeled it administrative closure.
The Audit Committee secretary delivered D04 to Dana's secure portal at nine Tuesday morning.
Dana matched its request number to yesterday's receipt.
A redacted register export and generation statement sat behind the manifest.
The secretary had produced only our authorized status and timestamp fields.
Names, narratives, titles, addresses, and attachments were absent.
Jonah's covered note had never entered the upload.
I wanted the status first; Dana kept the register closed until the custodian account, export time, and checksum matched the portal manifest before us.
Only then did she release the trackpad.
The clean match denied me an excuse to distrust the export before reading it.
She opened the register.
Issue 17 entered the system on January 11, 2024.
Its first status was OPEN.
Nine days later, at 9:23 a.m., the status became ADMINISTRATIVELY CLOSED.
The export contained no closing reason.
It contained no approver field.
It contained no reference to a completed review.
“So they buried it,” I said.
Dana left her hand on the trackpad. “The record does not say that.”
She made me replace my accusation with the fields we actually possessed.
“It was registered, remained open for nine days, and changed to administratively closed without a reason or approver in this export. That is all we know.”
“That is supportable.”
Grant's response letter waited beneath the manifest, already copied to the committee chair and WMG board secretary.
He argued that an issue could enter an intake register without becoming a formal complaint under WMG policy, but did not attach the governing rule.
On the definition alone, WMG had won a narrow procedural point in front of its own board record.
D04 did not establish that Issue 17 ever received the classification WMG called a formal complaint.
It did establish that the public phrase never became formal omitted an open entry, nine days of registered status, and the administrative closure that followed.
The distinction cost me the clean public contradiction I had expected to carry out of Dana's office that morning alone.
It also gave us a more important question than rhetoric.
Who had authority to close an open Audit Committee issue, what record should that decision have created, and why had the visible explanation vanished when the status changed?
“Request the native version history and the closing authorization,” I said.
Dana opened one follow-up under D04's matter number.
She requested the native status event, authorizing role, basis, and any routing record under the same issue number and dates.
The same identity exclusions carried forward.
No accusation appeared in the request.
A loaded verb would have given Grant a cleaner defense than the timestamp did.
Dana attached D04's generation statement and the limited follow-up.
I signed as reviewing client.
The portal routed a second receipt to the committee chair.
That routing placed the unanswered status change on a board-controlled docket Grant could not recast as a family disagreement.
I placed L03's delivery line beside D04's closure line.
Jonah's reply reached every specified mailbox at 9:06 a.m.
Andrew's executive-office account opened it at the same time.
D03 changed to refused to cooperate at 9:18.
D04 changed Issue 17 to administratively closed at 9:23.
Seventeen minutes separated delivery from closure; five minutes separated the draft change from the register change inside the same morning sequence we had already preserved.
The timing did not identify an actor or motive, but it made routine deletion schedules newly dangerous.
Dana turned from the portal to a blank preservation notice.
“Now,” she said, “we give every relevant custodian a reason not to lose the history before someone with authority can preserve it and inspect it.”