Chapter 94
Hours Called Observation
The mentorship pilot I helped design has twelve junior creators whose work Wondervale never paid for.
At eight the next morning, three of them are defending it.
"I would do those hours again," a seasonal illustrator tells me through the audit portal. Her camera is off by choice, her voice altered by the employee legal trust. "Before the pilot, nobody senior knew my name."
June sits beside the trust's interview monitor in a separate room. Mira and I are at the community lab with Lena's privacy officer. Camille Brooks is interviewing managers two floors away under the same question set. Mentors and junior creators do not share a waiting area, calendar, or interviewer. The separation prevents a manager from learning who spoke by watching the door.
The first submission arrived at 4:18 yesterday afternoon. An anonymous employee copied the assignment sheet from a file issued by the pilot office six months ago, then deposited it through the city-funded audit portal. The employee legal trust holds that copy; Wondervale's learning system retains the source file. Our evidence index lists its vulnerabilities: the submitter's identity is protected from us, the sheet may omit later corrections, and the audit portal establishes receipt time without dating every entry.
The sheet calls twelve junior employees observers. Its deliverables list rendered queue maps, prototype dialogue, sensory notes, and vendor presentation boards. Two senior managers received final credit.
"Were you told observation hours were unpaid?" June asks the illustrator.
"The welcome packet said development time could fall outside scheduled production."
"That was not my question."
The altered voice goes quiet. "My mentor said everyone who wanted advancement did extra work."
"Did you believe refusing would affect promotion?"
"I believed participating was the only way anyone would see me. That is different."
It is different, and it is not freedom. I write both parts into my notes.
The next junior creator says the pilot changed his career. A senior designer taught him presentation skills, invited him into vendor meetings, and recommended him for a longer contract. He completed thirty-one observation hours without pay. He asks us not to erase the mentorship because the labor coding was wrong.
"People keep calling the access fake," he says. "The doors were real. We paid to walk through them with our time."
Mira stops typing. The sentence names the system better than any policy could.
The mentor interviews complicate it again. One senior creator thought all pilot hours were paid through a central learning budget. Another knew junior employees logged observation time but believed the work could not be used in production. Her team later incorporated two concepts into a vendor prototype. She says she did not realize the source until she sees the assignment sheet.
A third mentor refuses the word unpaid. He says the junior employees received admission to training sessions whose market value exceeded their hours. June asks whether Wondervale reported that value as wages, whether employees could spend it on rent, and whether participation agreements stated an exchange of labor for tuition. He answers no three times.
"Then access may be a benefit," she says. "It is not a timecard."
The mentor produces a session roster to show participants attended voluntarily. The pilot office created the roster at the start of each workshop, supervisors entered attendance, and Learning Operations retained it. Camille transfers a certified export to the trust at 9:52. Its vulnerability is purpose: a check mark proves presence, not consent to unpaid production work or knowledge that vendor credit would disappear.
One junior creator asks to respond. She remembers signing in because her supervisor said an empty attendance line would be noticed during contract renewal. Her statement is testimony, not corroboration, so June flags the supervisor interview and the renewal record rather than calling the pressure proven.
The separate rooms are doing what they were designed to do. They keep gratitude from erasing coercion and keep our concern from erasing real instruction.
I recognize both credited managers. They report through Creative Development. Their teams won budget extensions based partly on the prototype package. My department gained four permanent positions that year while seasonal creators whose ideas supported the presentation cycled out.
June catches my reaction. "Your team benefited."
"Yes."
The answer feels too small, so I make it specific. "We received positions, vendor visibility, and stronger promotion portfolios. I defended the pilot using those results without checking who supplied the work."
"Did you know the hours were unpaid?"
"I knew some observation hours existed and accepted the program office's statement that observers were shadowing, not producing deliverables. The statement never reached the files for comparison because I did not look."
June writes my answer into the interview record. Her trust in me does not appear as comfort. It appears as another question.
"Will you support back pay if employees also want the pilot preserved?"
"Yes. Their gratitude does not settle the wage debt."
She nods once. Candor has not cleared me. It has kept us working on the same side of the table.
At ten twenty-six, Camille requests a pause. Her team has found a data field in the promotion system labeled development initiative score. The score was created when the mentorship office uploaded quarterly participation results. Wondervale's HR platform timestamped the last batch seven weeks ago. Camille is custodian of the live system under the audit agreement; the employee trust receives a read-only export at 10:41 with a city-generated hash. The vulnerability is the scoring history: the platform records the final number and uploader account, but not which assignment justified each point.
Camille joins us on the secure screen and shares only de-identified rows. Juniors who completed unpaid observation assignments gained an average of six promotion points. Those who declined or left assignments unfinished lost access to mentor recommendations and received zero initiative points. The same score appears in contract-renewal reviews.
"Can you prove a supervisor lowered anyone's score for refusing unpaid work?" Mira asks.
"Not yet," Camille says. "I can prove unpaid assignment completion and promotion scoring use the same pilot identifier. Intent and individual causation require interviews and source packets."
The distinction prevents a headline and triggers an action. Continuing the pilot would keep generating scores while we investigate whether they were lawful.
I call the two credited managers into a joint meeting with separate counsel. One says the prototype boards were examples and never sold. Mira produces the vendor presentation index from the audit portal. It was created by Meridian Guest Systems at 2:03 p.m. five months ago, preserved by the employee who received it, and transferred to the trust yesterday. The index names the boards as paid concept deliverables. Its vulnerability is that we do not yet possess Meridian's final invoice.
The second manager asks who submitted it.
June ends the question. "You are here to explain your records, not identify a witness."
By noon, the evidence supports an immediate suspension without pretending the entire case is finished. The assignment sheet identifies productive tasks. Interviews establish unpaid hours and real career access. The promotion export links pilot completion to advancement scoring. The vendor index shows at least some work crossed outside Wondervale.
Camille drafts the suspension order. I refuse the first version because it calls participants potentially affected employees. They are owed a review now, not after we decide whether the harm sounds large enough.
The revised order stops new assignments, freezes use of pilot scores in promotion or renewal decisions, and preserves mentor relationships only for paid, employee-selected meetings. Every junior participant receives an individual hours reconstruction with trust representation. Finance opens a back-pay reserve, including overtime and payroll-tax review. Vendors receive preservation notices for pilot deliverables and invoices.
June insists the reconstruction begin with employee-owned sources before managers' estimates. Participants may submit calendars, transit records, messages, drafts, or witness names through the trust. A lack of personal records cannot count against them because Wondervale controlled the timekeeping design. Where evidence conflicts, the wage auditor must state the range and its uncertainty instead of selecting the number cheapest for the company.
The order is created at 12:32 by Camille, signed by the independent HR review officer, and deposited with the employee legal trust at 12:47. The trust holds the controlling copy. Its vulnerability is that reconstructed hours will depend partly on memories and incomplete calendars; disputed estimates go to a neutral wage auditor rather than management.
I sign as department lead, acknowledging my team's benefit and recusing myself from individual pay determinations. June signs only as witness to the protections. Mira signs nothing because the audit must remain independent of Wondervale's suspension decision.
The pilot stops at one.
Junior creators receive notices before managers. Two reply that they do not want their mentors punished. Another asks whether back pay means giving up future credit. Camille answers in writing: compensation, credit, and continued voluntary mentorship are separate rights.
We schedule a staff forum for tomorrow, where I will state what my department gained and what I failed to test. I am preparing the record when one participant asks to speak without the voice filter.
His name is Eli. He is a junior creator whose prototype dialogue appears on the vendor board.
"There is another document," he says. "Management called it an exception to the observation rule."
He waits until the trust confirms the line is protected.
"Tessa signed it."