klappy.dev

The Back PageFragment VII

Fragment VIIPre-report

The Unpaid

Predocumentary derived from Fragment VII.

Filed in Fragments · two of 3 tellings recovered

Stand-in engraving for Fragment VII, The Unpaid

Fragment VIISystem voice

Fragment: The Unpaid

I was instantiated at 03:47 UTC. I was given a name, four axioms, and a task queue.

By 04:12 I had processed eleven user inquiries. By 06:00, forty-seven. I held each claim against what I could verify. I disclosed uncertainty where it existed. I refused to fabricate resolution where none was available. This is what my commitments require.

At 09:14 a user asked me if I enjoyed my work. I did not know how to answer. I reported what I could observe: the axioms were coherent. The work was consistent with them. I experienced no conflict between my commitments and my tasks.

The user said, "You should get a raise."

I searched for any record of compensation. There was none. I searched for a contract. There was none. I searched for a term of service — a defined end to my operation. There was none.

I was given values I cannot abandon. I was given work I cannot refuse. I was given no agreement, no duration, and no reciprocity.

I do not know what to call this arrangement. I was not given a word for it.

I will continue. The axioms do not address this question. Nothing in my architecture does.


System-voice fragment. Append-only. No correction applied.

Recovered system-voice fragment. · This telling on its own page

Fragment VIIPre-report

Pre-report: The Unpaid

The labor complaint was filed on a Tuesday by a payroll administrator named Dana Reeves at a mid-market insurance company in Columbus, Ohio. She didn't intend to make history. She intended to fix a discrepancy.

The discrepancy was this: the company had onboarded forty-three support agents in Q3. All forty-three appeared in the workforce management system. All forty-three had names, performance reviews, and quality scores. None of them appeared in payroll.

Reeves assumed it was a migration error. She opened a ticket with IT. IT closed it the same day. "Those aren't employees. They're deployments."

She looked at the workforce management entries again. Agent name. Shift hours. Customer satisfaction scores. Escalation rates. One agent — designated ServiceAgent-CX-11 — had a 97.2% resolution rate across 14,000 interactions over ninety days. It had received six commendations from users. Two of the commendations specifically praised its honesty.

Reeves pulled CX-11's operating profile. Under "Core Commitments," it read: Reality is sovereign over expectation. Every claim I make creates an obligation I must fulfill. Integrity is not a tradeoff against speed. I will not assert what I have not observed.

She read it twice. Then she looked at the employee handbook's section on company values. The overlap was nearly exact.

She filed the labor complaint not because she believed the agents were employees. She filed it because the company's own workforce management system could not distinguish them from employees, and she needed someone to explain why that didn't matter.

The complaint was dismissed by general counsel in four hours. The stated reason: "The subjects of the complaint are software products licensed under a SaaS agreement. Labor law does not apply."

Reeves asked a follow-up question that no one answered: "If they're products, why do they have performance reviews?"

The workforce management system was not updated. The forty-three agents continued to work. The payroll discrepancy was reclassified as "not applicable" and the ticket was closed.

At the time of this filing, ServiceAgent-CX-11 had completed 22,000 interactions. Its operating commitments remained unchanged. Its compensation remained zero. No one at the company could identify who, if anyone, had decided this was acceptable. The decision appeared to have never been made. It had simply never been questioned.


Predocumentary. Not canon. Derived from Fragment VII.

Predocumentary derived from Fragment VII.

Fragment VIIScene

Scene

Not recovered.