Chapter Twenty-Two returned the responsibilities between persons to Lin, the coordination group, the knowing beneficiaries, and the blank that remained unverifiable. Once the accounts were settled, Ye's situation did not thereby return to its place. Another imaging team was willing to let him join a new project, and the person in charge also said: "What happened before does not affect how we see you." On his first day back at work, his workstation was placed in the middle of the team; access, equipment, and pay had all been set up. Only one detail was not quite right: on the project sheet, his name appeared under "support personnel," while the shots he was responsible for were credited to someone else.
This file does not evaluate existing employment systems, nor does it offer a personnel plan. Files, appeals, chains of authorization, and institutional review all matter, yet they cannot replace a person's reclamation of a place within concrete relationships. This chapter follows Ye through his first week back at work, watching a few very small things: where he sat, how his words entered the record, whether he could decline an arrangement, and whether the support others provided demanded repayment in gratitude. The organization here is not the end point of the analysis, but the site at which an individual reclaims his place in reality.
Monday: A Desk, but No Place for Attribution
When introducing Ye to the team, the person in charge said that he was experienced, only "lately suited to somewhat lighter duties." These words could be sincere protection. Ye genuinely did not want to take on high-pressure projects lasting several months straight away, and he needed an entry point with a lower cost of failure. The problem lay not in the duties being smaller, but in how they were explained. If the scope is stated clearly by both sides and can be adjusted along with the actual work, a small task is a field for regaining feedback; if "needing protection" is defined unilaterally by the organization, with no date set for renegotiation, it fixes Ye as a person forever not yet ready.
In the afternoon, Ye revised a segment of the script and proposed deleting a shot that would mislead the audience. The meeting accepted the revision, yet the version record noted only "adjusted after team discussion." For any member this might be nothing more than rough record-keeping; for Ye, the omission formed a continuity with the old project: his judgment was being used, while his place as the one who judged did not appear. To sit in the meeting room, to be listened to patiently, and in the end not to be credited could still be a soft form of isolation.
Ye did not demand that every discussion carry his name. He only asked who was responsible for this revision, and who could explain the reasons should a dispute arise later. The person in charge realized for the first time that "protecting him from entanglement in disputes" had simultaneously taken away his authority to clarify disputes. The record was then changed to: "Deletion proposed by Ye, adopted after team review; follow-up to be explained jointly by Ye and the editing lead." The change was small, yet it reattached judgment and consequence to the same person.
Whether an organization takes a person in cannot be judged solely by whether a seat was given; one must also ask whether the seat was connected to a right of judgment proportionate to the duties. A position without a right of judgment may be well treated, even more secure than an ordinary post; precisely for that reason, the person in it finds it harder to point out that it is still mere shelter. The line between shelter and genuine taking-in lies not in the tone of care, but in whether his judgment can enter shared reality.
Tuesday: The Old File Arrives Before Ye
The partner organization sent a letter of inquiry: "We hear that Ye handled a dispute before — does this project require additional review?" The new person in charge forwarded the email to Ye without answering for him. When Ye saw the words "handled a dispute," the old project's overall characterization had already arrived before he did. It did not say outright that Ye had done anything wrong, nor did it state its sources, yet it sufficed to make all subsequent work begin from suspicion.
Ye separated the versions he had kept, the corrections the old project had later issued, and the parts that remained disputed. He did not demand the deletion of the fact that he had indeed left, nor did he call every unfavorable document an act of hijacking. The corrections targeted errors that could be checked: backdated dates, rewritten meeting conclusions, the recording of a refusal of additional tasks as a refusal to perform the contract. As for evaluations of the kind "the team found collaboration difficult," what he demanded was a statement of who formed them, when, and within what scope of application — not a whitewashed history.
After receiving the materials, the partner still decided to add one more review of the finished film. This might be a reasonable project judgment, and it might be influenced by the old impression. The outcome alone cannot decide which. What Ye could do was not to demand that the other side first prove complete trust in him, but to narrow the question: what risk to the work does this review target? Does it also apply to other tasks of the same kind? Will the result enter a character assessment unrelated to this project? When the question can be brought down to the current object, the old label no longer automatically answers on behalf of every new material.
The meaning of file repair within this dossier extends only this far: not to establish a flawless system, but to let Ye himself see what statements are representing him, and to place his own materials back into the same decision. The reality check here is whether he must always wait, until others have already finished their interpretation, before he is allowed to enter.
Wednesday: A Helping Hand Begins to Demand Repayment
The team adjusted a deadline for Ye and also arranged for a colleague to check the deliverables together with him. At lunch that day, someone said half-jokingly: "Everyone has been so accommodating to you — don't make things hard for us again this time." The remark had no formal consequences, and Ye even understood the speaker's worry. Yet it changed the nature of the support once: the adjustment was no longer for bringing the task into proportion with actual ability, but became an extra gift from the team to him; and since a gift had been received, he owed, in return, a result free of problems.
Support of course has costs. A colleague did one more round of checking, and the project schedule changed accordingly. To acknowledge costs is not to book them as a debt of favor. If an adjustment is an arrangement both sides make in order to complete a task, it can be evaluated, narrowed, or ended; it should not be dug up to settle accounts the moment Ye raises an objection: "We have already done so much for you." Once support is able to cancel subsequent questions, help has become another instrument for clearing responsibility.
Nor could Ye understand support as an unlimited commitment. He ascertained that the joint checking would last two weeks, after which it would be renegotiated on actual results; the colleague could say it was not feasible once the workload grew too high, and the person in charge would then need to find another arrangement. Finitude as such is not abandonment. What truly needs observing is whether the limits are knowable in advance, whether changes can be negotiated, and whether, once someone cannot deliver, the gap is honestly left in place. The organization has no obligation to guarantee that Ye never suffers setbacks, and Ye has no obligation to prove, by "recovering well," that the adjustments were worthwhile.
The afternoon task was completed on time. The person in charge praised Ye's condition. This result shows only that today's task was finished; it cannot be run backward to the conclusion that help is no longer needed, nor does it prove that the earlier worries were entirely superfluous. If one smooth delivery is used to cancel conditions, and one mistake is used to restore the old label, then support is not being adjusted according to materials but oscillating between two presuppositions.
Thursday: Whether Gratitude Is a Ticket for Continued Use
At the regular meeting, the person in charge asked Ye to share his impressions of the first week. Ye first thanked the team for letting him view emails and revision records directly, and then pointed out that the attribution rules remained unclear. The atmosphere cooled briefly. Someone said: "We have been so open — couldn't you look forward as well?" "Looking forward" carried two meanings here: not letting the past monopolize the future is indeed a capacity Ye needs; no longer raising the real consequences the past left behind is a demand that he prove his recovery with silence.
Loyalty tests usually require no oath. When support expands with gratitude and contracts with criticism, a few rounds suffice for the person concerned to learn which words are safe. Someone skilled at performing ease and gratitude will be judged to have recovered well; someone able to point out precisely what is wrong with a rule will instead be judged still trapped in the past. What this yields is not a healthy collaborator, but one who makes the least trouble.
Ye brought the question back to its object: "I am willing to continue with this project. What I am asking is: for one and the same revision, why is someone else credited automatically while I must apply separately?" He did not explain each person's motives through the old experience, nor did he withdraw the question in order to appear cooperative. The person in charge checked the template and found that the support-personnel column indeed did not enter the main version record by default. This had not been instituted against Ye, yet it produced particular consequences for him. The team decided that this project would henceforth record contributions as they actually occurred, leaving a general revision of the template for separate discussion.
This outcome is not grand, nor does it show that the organization has become healthy. It proves only that one objection did not immediately cost Ye his membership. He can be grateful for specific help while continuing to disagree with another arrangement. Gratitude thereby returns to its emotional place, no longer a ticket for continued use.
Friday: Who Defines Whether the Week Was a Success
The Friday review form had a column titled "adjustment status." The person in charge had been ready to write "smooth overall"; Ye proposed splitting it into current facts: two tasks completed; one revision with shared attribution; the deadline adjustment continuing into next week; the inquiry from the old file still unresolved. The former wording is more concise, and reads more like good news; the latter passes no overall verdict on the week, yet lets the next week know where to continue from.
Ye did not acquire the power to evaluate the whole organization. He too can misread. In one discussion a new colleague spoke bluntly, and Ye at first heard it as directed at him; after checking the record he found that the criticism pointed at a definite limitation of the project. He revised that judgment, and the colleague acknowledged the roughness of his own wording. Having been harmed does not make every new judgment automatically correct; being able to return to current materials, without paying for it with a negation of past experience, is the sign that the reality check has become usable again.
By the same token, the organization cannot use this one week to declare on Ye's behalf that he "has come through." Completed work, restored attribution, and safe objection are checkable changes of conditions, not a diagnosis of recovery. Actual health still requires corresponding professional evidence, and whether one feels at ease is not decided by a process sheet. Ye may still be nervous, sleepless, or sensitive to certain phrases; these difficulties do not make the improvements that have already occurred false, nor can those improvements cancel them.
A complete system would still need to preserve objection, distribute the power of files, and establish external appeal; but whether Ye recovers cannot be proven merely by which provisions the system has in place. This file leaves behind five pieces of evidence: one revision bearing his name, one letter of inquiry that he himself could see, one support with a time limit, one disagreement that brought no punishment in return, and one weekly report that refused to say "smooth overall." They guarantee nothing about the future, yet they show that Ye no longer has to know his own place only from others' conclusions about him.
The next chapter will let new difficulties happen again: a plan criticized, a mistake misreported, and Cen preparing to leave as well. The meaning of the first week back is not that injury will never come again, but that when injury, error, and disagreement arrive, Ye can still distinguish the object, check the materials, bear his own portion, and ask others not to complete the remaining interpretation on his behalf. If freedom is promised as never being hurt, it will be declared a failure at the next pain; if the qualification to judge can persist within pain, reality has not once again been collected by others in his stead.