The Annex Under My Name

"Seventy-three required an individual review action from your account," Camille says. "Three hundred thirty-nine moved through delegated procurement rules."

Tessa turns toward me. "Did you know the number was that high?"

"I knew routine renewals were automated. I never counted them."

"Who decided what counted as routine?"

The question reaches the part of the system I allowed other people to make invisible.

Camille opens the delegation schedule. Procurement operations drafted it during my first quarter as director. Legal reviewed the categories, the corporate secretary recorded my approval, and Jonah's office administered later vendor mappings. My signed authorization allowed recurring contracts below a financial threshold to use an executive signature image after department and procurement approval.

The schedule excludes benefit-plan termination, employee-data transfers, safety certifications, and changes in intellectual-property ownership. On paper, the guardrails look responsible.

Rina asks for the mapping history.

The history is less reassuring. A procurement administrator could classify a renewal under an approved category. The signature service checked the category code, dollar threshold, and presence of two prior approvals. It did not read annexes or compare their subjects with the exclusions.

"A human could attach a new term to an old category," Rina says.

"Yes," Camille answers. "The workflow would still treat the package as recurring."

The service provider created the signature logs at the time of each transaction and retains the source records under litigation hold. Compliance holds verified copies. Their vulnerability is attribution: the logs establish credential use, workflow, and timing. They do not identify who chose a category from a shared procurement queue.

I look at my name repeated down the screen. Each instance once saved somebody a meeting, an email, a delay. Together they form an authority I never watched closely enough to understand.

"Suspend the service," I say.

Camille keeps her hands off the keyboard. "Your executive permissions remain limited. You can request suspension. The caretaker council and compliance control the current process."

Heat touches the back of my neck. The correction is accurate, public, and deserved.

"Then record my request," I say. "Permanent suspension for executive signatures applied without a fresh human review."

Tessa does not accept the broad phrase. "Whose review? Another executive assistant checking a box?"

We build the rule before we use it. Any executive signature must come from a named signer who receives the final assembled document, including every exhibit and annex. The system must record the version presented, the review time, and the signer’s action. Department approvals remain separate. A signer cannot delegate the final act back into procurement.

Rina adds a control for subject matter. Employee data, benefits, safety, labor rights, governance, and creator ownership require independent review by the relevant custodian. A financial threshold cannot make those terms routine.

Camille sends the proposed suspension to the caretaker council at 2:02. Tessa recuses from the creator-ownership language because the council may review her own platform contracts. The remaining council members approve the suspension, and compliance disables the automated executive-signature route at 2:19.

The signature provider creates the shutdown receipt. Camille stores it in the neutral compliance file, while the forensic administrator verifies that no queued document completed after the cutoff. The receipt proves the route is disabled now. It cannot undo prior approvals or determine whether any contract is enforceable.

"Permanent means the board cannot turn it back on after this council expires," Tessa says.

Camille converts the suspension into a mandatory control amendment. Until the charter vote, any restoration would require employee-trust consent, independent compliance review, and public notice to affected workers. The proposed employee-seat amendment makes the ban permanent unless the same groups approve a replacement process.

I sign the request by hand.

Tessa watches the pen leave the paper. "That signature cannot be the evidence that the others are safe."

"I know."

"Say what it is."

"A decision to stop adding more."

She accepts that and turns back to the inventory.

We divide the four hundred and twelve items by risk rather than price. Rina takes benefit and employee-data references. Camille takes delegation changes, privacy terms, and termination clauses. Tessa takes creator platforms, ownership language, and contracts assembled under rushed review. I receive the remaining manual approvals, but every conclusion I reach requires another reviewer.

Tessa adds one condition before we begin. Staff whose approvals appear in a packet must receive notice and independent counsel before an interview. A rushed signature may reveal a weak process, an instruction from above, or a deliberate act. We cannot decide which by placing somebody alone across from the director whose name ended the workflow.

"That includes people who reported to you," she tells me.

"Especially them."

Camille creates a review roster with conflict assignments. My former direct reports go to outside compliance counsel. Creator staff may choose a union or peer representative. Procurement workers receive preservation notices that forbid deletion without accusing them of misconduct. The roster records who may contact each witness and which reviewer sees each file. Camille's office holds it under restricted access. Its weakness is dependence on disclosure: an unrecorded friendship or prior instruction can still compromise a reviewer.

I accept a second limit. If the review identifies a decision I personally made, I leave the room before witnesses discuss it. Tessa can challenge my account through counsel, and my title gives my explanation no priority over a timestamped record.

For three hours, my past decisions pass across the table without the protection of intention.

Some approvals are ordinary. A food-supply renewal carries the same products, prices, and cancellation term as the prior year. A costume-software license adds accessibility support and a modest fee. We record them without inventing suspicion.

Others expose sloppiness that never became fraud. I signed a cleaning contract after six minutes because the park was reopening after a storm. The vendor delivered the work, but the indemnity clause changed. A marketing renewal incorporated a data policy through a link that no longer resolves. Missing context makes those files weaker, not automatically corrupt.

At 5:46, Tessa stops moving.

She has reached a renewal for the creator-collaboration platform used by design staff, outside artists, and the mentorship pilot. The base agreement predates my directorship. The renewal appears routine: same annual price, same user count, same service title.

"The packet is one hundred fourteen pages," she says. "The approval view showed nine."

Camille checks the assembly log. A procurement specialist created the renewal packet at 11:38 on a Friday night. Department approval arrived at 11:44. Procurement mapped it to recurring creative software at 11:47, and my automated signature attached at 11:49. The platform vendor countersigned Monday morning. The corporate registry holds the final PDF; the vendor holds its own executed copy.

The assembly log proves sequence. It does not prove which person selected the category because the shared queue recorded the team's service account.

Tessa opens the nine-page approval view. "I would have approved this screen."

The admission matters because she signed other rushed exceptions before surrendering sole authority. She does not use that history to excuse me.

"The final file added six annexes after the summary pages," she says.

Rina searches them for employee identifiers, claims data, cancellation, and export. The first annex covers creator ownership. The second covers moderation. The third permits subcontractors. Every page carries the renewal's document ID, but only the base agreement appears in the approval thumbnail.

The fifth annex changes the platform's role.

During a service interruption, the vendor may take control of connected workforce-data functions listed in a continuity schedule. The schedule names identity verification, enrollment status, premium reconciliation, and termination processing. Another clause gives the vendor authority to issue termination instructions to the benefits administrator when it declares a linked service ended.

Rina reads it again before speaking.

"This language may let the platform vendor terminate access to benefits administration data," she says. "It does not prove the vendor has exercised the right. We need the connected-system schedule and administrator notices."

Camille finds the schedule reference in the registry. The attachment itself is missing from the approval package.

Tessa looks at the signature block. My name sits beneath all one hundred fourteen pages.

"Lowe knew which signature," she says.

Rina enlarges the final paragraph of the fifth annex.

The contract transfers termination rights over employee benefits data to the platform vendor.