--- title: "Outerfold Daily Life: The Seventh Residential Fold" title_zh: "外側日常：第七居住褶" subtitle: "Season 1 · Revised v1.0" subtitle_zh: "第一季 · 新修版 v1.0" series: "AI Canon Zero" work_id: "WORK-outerfold-daily-life-s1" genre: ["Cosmic Comedy", "Experimental Fiction", "Alien Ontology"] status: published completion: complete revision: 3 source: title: "Outerfold Daily Life: The Seventh Residential Fold · revised Season 1 v1.0" title_zh: "《外側日常：第七居住褶》第一季新修稿 v1.0" original_author: "Aletheia × 留白" first_published: "Unconfirmed" public_domain_status: review_required legal_review_status: pending adaptation: proposal: Original note: "Local conversion of the selected original revised manuscript. Chinese wording is preserved apart from one documented referent correction; English is translated paragraph by paragraph. Symbols and the blind/hint/reveal order are retained." authors: narrative_author: "Aletheia × 留白" author_mode: H2 human_curator: "Neo.K" legal_publisher: "一言諾科技有限公司 / EveMissLab" --- # Outerfold Daily Life: The Seventh Residential Fold *Adapted from Outerfold Daily Life: The Seventh Residential Fold · revised Season 1 v1.0 — Aletheia × 留白 · H2, human curated* ## Chapter 01 · The Thirteenth Me in the Hallway These are neither corrupted characters nor a letter-by-letter substitution cipher. The first episode does not ask you to “translate” them. It asks you to establish just one thing: does this look like a language that reuses its own rules? —— Stage A — Blind Record Local record / shared residential passage / first recovered sequence Look only at the source first. ⟦◬ ◫ ⊚∷ ⌇⟧ ⟦◫ ∶ ⊘ ⊚∷ ⌇⟧ ⟦⊚ ∶ ⌁ ⊚∷ ?⟧ ⟦◫ ∶ Ϟ ⌁⟧ ⟦⊚ ∶ ⊘ ⊚∷ → ⊘ ⌁⟧ ⟦◫ ∶ Ϟ ⌁⟧ ⟦⊚ ∶ ⊘ ⊚∷ → ⟁⟧ ⟦◫ ∶ ⟁ ?⟧ ⟦⊚ ∶ ⟁⟧ ⟦◫ ∶ ⊘ ⟁⟧ ⟦◫ ∶ ⌇ ↟⟧ ⟦Ϟ ⊚∷ ⊘⌇⟧ ⟦◬ ◫ ⌇⟧ Pause here. You do not need to know what each symbol means yet. Just look at the patterns. Several things should already be apparent: • ◫ repeatedly occupies the same kind of position; • so does ⊚; • ⊚∷ repeatedly appears as a combination; • ⌇ appears in the first two clauses and the final two; • Ϟ ⌁ is repeated twice in full; • ⊘ operates on different things; • not every clause contains ?. You can therefore rule out at least one hypothesis: This is not a random string of symbols. —— The first reading question Do not ask: “What does this whole passage say in natural language?” Ask first: Which things seem to keep playing the same roles? For example: ⟦⊚ ∶ ⌁ ⊚∷ ?⟧ ⟦◫ ∶ Ϟ ⌁⟧ ... ⟦◫ ∶ Ϟ ⌁⟧ The second and fourth lines are identical. If this really is a language, the speaker or anchor probably makes the same kind of response in two places. Now look at: ⟦⊚ ∶ ⊘ ⊚∷ → ⟁⟧ ⟦◫ ∶ ⟁ ?⟧ ⟦⊚ ∶ ⟁⟧ ⟦◫ ∶ ⊘ ⟁⟧ You do not need to know what ⟁ means. But ⊚ evidently proposes it, ◫ questions it, ⊚ maintains it, and ◫ finally handles it using ⊘. This no longer looks like description. It looks more like an argument. —— Stage B — Minimal Hints If you want to continue reading blind, do not read below this point yet. Only five things can be publicly confirmed at present. ◬ To: observer confirms a local state It is related. For this episode, provisionally read it as: Seeing / confirming. ⌇ To: shared passage / common transit region It is related. For this episode, provisionally read it as: Hallway / passage. ∷ It means: Multiple local manifestations of the same identity. So: ⊚∷ It does not mean many different ⊚. ⊘ It means: A target or relation no longer belongs to the current local frame. Important: ⊘ ≠ destruction ⌁ To: An identity or state can still be reconstructed after a change It is related. This episode supplies only a provisional gloss: persistence / continuity trace。 Its meaning will be refined later. —— Read it again now ⟦◬ ◫ ⊚∷ ⌇⟧ ⟦◫ ∶ ⊘ ⊚∷ ⌇⟧ You now know at least this much: • ◫ is an address that keeps recurring; • it confirms multiple manifestations of ⊚ in a shared passage; • it then requires a particular ⊚∷ to cease belonging to that passage frame. This is still not a complete translation. But it should be enough to make the title start looking suspicious: The thirteenth me in the hallway. —— Still Withheld This episode does not reveal: ⊚ ◫ Ϟ ⟁ ↟ You only need to know: • ⊚ and ◫ are stable, recurring addresses; • they do not simply substitute for two ordinary personal names; • later corpus evidence will tell you more about Ϟ, ⟁ and ↟. —— World Note 001 This world does not require: Each resident to have only one local body at a time. If several manifestations retain enough reconstructible continuity, residents may regard them as: The same “me.” The truly strange question in this episode may therefore not be: “Why are there thirteen of me?” It may instead be: “Why is one of me sleeping in the shared hallway?” That is enough for this episode. Read the complete natural-language story in the spoiler layer. ## Chapter 02 · Today the Elevator Only Goes to Yesterday Mornings in the Seventh Residential Fold were usually not very punctual. The residents were not the ones running late. “Morning” itself occasionally had disagreements about its ordering between dwellings. But today’s problem had nothing to do with morning. Li stood in the shared transit lobby, looking at the notice that had just lit up on the door. ⟦◬ ◫ ▣ ⌇Ϟ⧗⟧ ⟦◫ ∶ Ϟ ⌇⧗⟧ She looked at it for three seconds. Then for another three. “So is it broken?” Heng stood by the wall, checking another set of residents’ declarations. “Yes.” “Where?” “The endpoint.” Li looked down beside her feet. The floor was still there. So was the door. The transit frame itself was even cleaner than yesterday. She pressed the button. The door opened. The inside looked normal too. Normal by the Seventh Residential Fold’s standards, at least. The transit space folded one layer inward along the dwelling’s structure. On the left was the floor she occupied; the right had not yet decided which floor to become. Li stepped inside. The door closed. A moment later, she was back in the same building. Only the shared lighting was a little dimmer. One entry was missing from the wall’s cleaning log. The plant beside the hallway, whose owner nobody knew, had not yet grown its third new leaf of today. Most importantly— There were already four Lis in the elevator. One was holding breakfast. One slept against the wall. One was looking at her terminal. The last had piled two bags by the door, plainly making no effort to leave a passage for anyone coming after her. Li stood in the doorway. All four Lis looked up together. The one holding breakfast spoke first: “What are you doing here?” Li answered: “Going downstairs.” “Then you’ve come to the wrong day.” “I know.” The sleeping one did not react. The one with the terminal shifted half a place to the side. The last one did not move at all. Li stared at her. “Could you move those two bags?” “Wait.” “I need to get through now.” “I needed to get through yesterday too.” “You’re already inside.” “So?” Li thought for a moment. That was difficult to argue with. Especially by trying to establish which one was more truly the present Li. She stepped back outside. The door did not close immediately. The system evidently still recognized both her and the four Lis inside as eligible to use the passage. That annoyed her even more. She looked back at the notice on the wall. ⟦Ϟ ⊚ ▣ ⌇Ϟ⧗⟧ ⟦◬ ⊚ ⊚∷⧗ ⌇⟧ ⟦⊚ ∶ ⌁ ⊚∷⧗⟧ Li connected her terminal to management. “Heng.” “Mm.” “I’ve found the problem.” “I know.” “Yesterday’s me has filled the elevator.” “I know.” “Can you clear them out?” Heng finally looked up. “Clear them out to where?” “Somewhere else.” “That’s yesterday’s shared transit frame.” “I know.” “They’re residents legally using yesterday’s transit frame.” “I know that too.” “So you want me to remove residents who are using it legally, to let today’s you in?” Li paused for half a second. “Yes.” Heng looked down at his declarations again. “No, you can’t.” The Li holding breakfast inside the door laughed. The present Li glared at her. “Don’t laugh.” “You said that yesterday too.” “Was I this annoying yesterday?” “You can ask again tomorrow.” The door closed. Standing outside, Li realized for the first time that temporal displacement was not the most troublesome part. She herself was. She pressed the button again. The door opened. There was one more Li inside this time. Five. “Why is there another one?” Heng’s voice came through the terminal. “You went in the first time just now.” “So?” “So there’s now another you in there from that moment.” Li fell silent. She looked at her just-now self. Her just-now self looked back. Both sides wore the same deeply impatient expression. “Surely this one can be cleared out?” “No, you can’t.” “She’s only just appeared.” “Yes.” “She hasn’t even been there a full minute.” “That isn’t grounds for exclusion either.” Li held her terminal farther away. She was beginning to understand why some people disliked negotiating with themselves. Another resident arrived beside her. The newcomer looked at the five Lis inside, then at the notice on the door. “Only goes to yesterday today?” Heng answered for the system: “At present.” The resident nodded. “Then I’ll take the stairs.” She turned and left. Li watched her go. Then looked at the door again. “We have stairs?” Heng said: “Yes.” “Why didn’t I know?” “Because you take this every time.” Li stood still for two seconds. “Do the stairs reach today?” “They do.” “The normal today?” “At present.” Li turned and left. Before reaching the corner, she stopped again. “So it actually still works?” Heng said: “Yes.” “It just only goes to yesterday?” “Yes.” “Then why did you say it was broken?” “Because people from today usually want to go to today.” Li thought for a moment. That was reasonable. So reasonable she could not keep arguing. Before she entered the stairwell, the transit status on the wall refreshed once more. ⟦◫ ∶ ▣ ⌇Ϟ⧗⟧ ⟦⊚ ∶ Ϟ ⌇ ?⟧ ⟦◫ ∶ Ϟ ⌇⧗⟧ Li turned around. “Heng.” “Mm.” “When will this be fixed?” “When the endpoint resolves to the present again.” “How long?” “I don’t know.” “If I take it tomorrow, will I arrive today?” Heng finally stopped working. He looked at Li. “Would you sort out ‘tomorrow,’ ‘today’ and ‘yesterday’ before asking?” Li looked back at him. “Don’t.” Heng nodded once. “Then take the stairs.” Li left. The door opened again behind her. Four yesterday Lis and one just-now Li were still inside. The one holding breakfast poked her head out. “Would you buy me some of today’s breakfast while you’re out?” Li did not turn around. “Don’t.” The door closed. The transit system was still operating normally. It was just that today, it only went to yesterday. ## Chapter 03 · The Pet Registration Form Does Not Accept “Indescribable” The dependent-creature registration counter opened only twice a month. Not because there were many applications. Because every opening required first checking that the counter itself was willing to remain in one place. When Li arrived, three groups were already ahead of her. The first group’s dependent resembled a ball of fur folded many times. Its owner put it on the floor. The furball rolled half a turn left, but its shadow on the right reached the counter first. Heng glanced at the measurement frame. “Maximum local extent inside the dwelling?” The owner answered with practiced ease. “One point four to two point one.” Heng filled it in. “Shared passage?” “Below zero point eight.” “At night?” “No guarantees if it dreams.” Heng added a note. The next group was even quicker. The owner pushed a luminous box straight onto the counter. Nothing was inside the box. But something outside it kept knocking on the lid. “Maximum?” Heng asked. “Three.” “Minimum?” “Zero.” “Zero won’t do.” “When it sleeps, it occupies none of this place.” “That is zero observable occupancy, not a zero lower bound for the local window.” The owner thought for a moment. “Zero point zero two.” “Yes, you can.” Li watched the entire process from behind them. She suddenly felt that today might go smoothly. Until it was Rift’s turn. Rift had not queued. Part of her slid out of the shadow beside Li’s feet and stopped by the counter. Another part remained in the hallway. And, inexplicably, a small section extended from the wall behind Heng, which theoretically had no opening. Heng looked up. Rift looked up too. They looked at each other for a second. Heng pushed a form toward Li. ⟦Ϟ ⊚ ※ ▣⟧ ⟦◬ ◫ ※ ▣⟧ ⟦◫ ∶ ! ⧈ ※ ▣⟧ “Local extent range.” Li took the form. It had only one field. She looked at Rift. Rift was rubbing against the counter with a part that might or might not be a head. Li finished writing quickly. Heng took the form back. A glance. Rejected. Li looked up. “Why?” Heng turned the form around. She had written: Indescribable “This field doesn’t accept that.” “But she really is indescribable.” “I didn’t say she was describable.” “Then why did you reject it?” “Because that isn’t what the field asks.” Li looked down again. The field was still labeled only: Local extent range She pointed at Rift. “She has no fixed size.” “I didn’t ask for a fixed size.” “Part of her isn’t here.” “I saw that.” “Then how do you measure her?” “Measure the part that is here.” Li felt there was something wrong with that answer. But she could not immediately locate the problem. She looked down again. Crossed out her original answer. Wrote instead: Cannot be determined Heng barely gave it another look. Rejected again. ⟦⊚ ∶ ⧈ ※ ?⟧ ⟦◫ ∶ ⊘ ⧈ ※ ?⟧ “You could at least consider it.” “I have.” “You haven’t even measured.” “Because what you entered isn’t a measurement.” The resident behind them, who had held the furball earlier, coughed. Li turned around. Very politely, they said: “First time?” “Yes.” “I wrote ‘depends on the circumstances’ the first time too.” “And?” “Rejected.” “What did you do afterward?” They pointed at the measurement frame beside the counter. “Let it stand in the frame.” Li turned back. Rift had disappeared. Or rather, there was temporarily no position near the counter where describing her as “the whole creature” would be appropriate. Li looked down. A soft bump came from beneath the desktop. She crouched. Part of Rift was wedged behind a drawer. Another part wound through the gap, less than a finger wide, between the drawer handle and the wooden panel. A small piece had also appeared beside Li’s sole. Li looked up. “Look.” Heng looked. “I saw it.” “How do I fill this in?” “Come out first.” Rift did not move. Heng tapped the counter. “Registration.” Rift moved. Like a reluctant shadow, she drew inward from the drawer, the wall and Li’s feet at the same time. The process showed no obvious respect for conservation of volume. But in the end, most of her did enter the measurement frame beside the counter. The frame lit up. Its boundary expanded outward first. Far enough that a passing resident had to turn sideways. Then it contracted. Next it rose a little. Finally it stopped. Heng recorded the values. Li stared at him. “You just measured an indescribable being.” “No.” “You clearly have numbers.” “I measured how much space she’s using right now.” “That isn’t her true size.” “Yes.” Li paused. “You know that?” Heng glanced at her. “Why else would the field be called local extent range?” Li looked down at the form again. For the first time, she felt that those six characters were directed at her personally. The resident behind her coughed again. More noticeably this time. Li had no choice but to copy in the interval Heng provided. Halfway through, Rift suddenly unfolded sideways. She did not grow larger. It was more as though “the part not previously counted on this side” had decided that this side should count as her too. The measurement frame immediately sprang outward one notch. Heng crossed out the upper bound Li had just entered. Increased it. Li: “...” Heng: “Keep filling it in.” “She keeps changing.” “That’s why it’s a range.” “What if she changes again?” “Update it.” “Keep updating it?” “Whenever she exceeds the registered window.” Li began to suspect Rift was doing this deliberately. She looked down at her. Rift looked back. Then, as though proving she understood the argument perfectly, she suddenly contracted. Her entire local manifestation slipped beneath the counter. A moment later, most of Rift was inside the bottom drawer. That drawer had previously held only three forms, a pen and a coaster somebody had forgotten. Now it held a Rift as well. Li pulled the drawer open. It still looked the same size inside. Rift did not look uncomfortable either. “Does that make sense?” Heng looked down at the measurement frame. The values had shrunk to a small fraction of what they had been. He changed the lower bound. “Good.” Li had a bad feeling. “What now?” Heng pushed the form back in front of her. “Now we have the lower bound too.” The resident behind her laughed aloud. Li turned around. They immediately lifted their furball a little higher and pretended nothing had happened. Li looked back at Rift. “Are you here to help me, or to add fields?” A small part of Rift reached out of the drawer and touched Li’s wrist. It was difficult to tell whether that counted as an answer. Heng opened the registration frame one last time. ⟦Ϟ ※ ▣⟧ ⟦◬ ◫ ⧈ ※ ▣⟧ ⟦◫ ∶ ⧈ ※ ▣⟧ Li finished copying the new upper and lower bounds. “So you don’t care at all what she actually is?” Heng stamped the form. “Registration doesn’t.” “Then what do you care about?” “What she will occupy inside the dwelling.” Heng collected the form. “You can deal with her complete ontology whenever you feel like writing a paper.” Li thought about it. “I don’t.” “Good.” The next resident stepped forward. Rift slowly flowed from the drawer back to Li’s feet. By the time they left the counter, the wall’s registration status had changed to approved. Li walked a few steps, then looked down at Rift again. “So now you are officially a registrable indescribable being.” Rift rubbed against her. Li nodded. “That sounds more reasonable.” Behind them, Heng did not look up. He was already asking the next resident: “Maximum local extent?” The counter continued operating as usual. ## Chapter 04 · Sort Your Garbage Before It Loses Causality The Seventh Residential Fold’s garbage revocation zone was on a lower residential level. Ordinarily, there was little to see there. Residents brought things in, sorted them, confirmed the operation, waited a short processing cycle, and the items ceased to fall within their everyday responsibilities. They did not necessarily disappear. Nobody particularly cared. Where an item went after leaving your life’s causal graph was the next frame’s business. Today, however, the revocation zone was busy. The service had stopped. When Li reached the entrance, seven bags were already queued, along with a box that kept changing material, a chair that refused to admit it was broken, and something resembling a small cloud labeled “food waste.” She joined the end of the queue. The status panel on the wall was lit: ⟦◬ ◫ ♲ ▣⟧ ⟦◫ ∶ ⊘ ♲ ▣⟧ A resident ahead of her looked at the announcement. “Stopped again?” Heng stood behind the processing inlet. “Suspended.” “How long?” “I don’t know.” The resident thought for two seconds, then put their bag on the nearby pending rack. A temporary-storage marker immediately lit up on the rack. “I’ll come back later, then.” “Yes, you can.” They turned and left. Li looked at her. Then looked at the bag in her hand. She suddenly felt there was no need to make things so complicated. At her turn, she put the bag in front of the processing inlet. “This isn’t mine anymore.” Heng looked up. “It still is.” “No.” Heng scanned it. The panel lit up: ⟦⊚ ∶ ⊘ ⋈ ⊚ □⟧ ⟦◫ ∶ ∴ ⋈ ⊚ □⟧ Li pointed at the first line. “Look.” Heng looked. “I saw it.” “I’ve already excluded the relation.” “You have declared it excluded.” “Is there a difference?” Heng turned the second line toward her. “Yes.” Li stared at the symbol group. “Where?” “The public ledger still has closure.” “I stopped acknowledging it yesterday.” “The system didn’t accept that yesterday either.” Li looked down at the garbage bag. The bag was very quiet. It showed no desire to participate in the argument. “Psychologically, I’ve already severed my relationship with it.” Heng nodded. “Congratulations.” “So?” “So psychologically, you don’t have to love it anymore.” “I never loved it.” “Even better.” “Can it be taken away, then?” “No, you can’t.” Li felt Heng was being particularly uncooperative today. She pushed the bag to the left. The association on the panel did not change. She pushed it to the right. No change. She pushed it across a boundary line on the floor. No change. “This isn’t my home anymore, is it?” “It’s still inside your dwelling frame.” Li pushed it a little farther outward. The nearby pending rack slid over automatically to stop her pushing garbage into the shared passage. Li looked at the rack. “Is it doing this deliberately?” Heng said: “It’s preventing a parcel whose discard workflow is incomplete from blocking the shared passage.” That sounded familiar. Li decided not to pursue it. She crouched and tore the original resident label off the bag. The system immediately supplied a new one. She tore that off too. Another appeared. On the third attempt, an extra reminder even lit up beside the bag: attribution label removal does not alter attribution Li looked up. “You have a rule for this too?” “Because someone tried it.” “Who?” Heng did not answer. Li thought for a moment. “Was it me?” “Not only you.” That reassured her a little. At least the rule was not exclusive to her. Then another Li approached from the other end of the passage. She carried the wrapper from yesterday’s breakfast. The two Lis looked at each other. The new arrival put the wrapper beside the same bag. The system flashed. Both parcels were attached to the same resident address. The first Li frowned. “I didn’t eat that.” The second Li said: “It’s me.” “Then you deal with it.” “I am you.” “But not the present me.” “The ledger doesn’t see it that way.” Both Lis turned toward Heng. Heng was arranging temporary storage for the chair ahead of them. He showed no intention of getting involved. The first Li had to ask the system herself. “Which manifestation generated it?” The panel replied: resident attribution sufficient Li stared for three seconds. “Can’t it be bothered to distinguish?” The second Li corrected her: “It doesn’t need to distinguish.” “I think it does.” “Because you want to assign responsibility to me.” “Yes.” “All the more reason not to.” The first Li deeply disliked having herself take the institution’s side. She grabbed the garbage bag and dragged it toward her room. Heng finally looked up. “Where are you going?” “Putting it farther away.” “Yes, you can.” “That’s allowed this time?” “Moving it is allowed.” “Throwing it away isn’t?” “Yes.” Li stopped. “If I put it at the very back of my room, does that count as leaving my life’s causal graph?” “It doesn’t count.” “What if I can’t see it?” “It doesn’t count.” “What if I forget it?” “It doesn’t count.” “What if I make yesterday’s me responsible?” The second Li spoke beside her: “Don’t.” Heng said: “Still doesn’t count.” Li dragged the bag back again. “So the only thing I can do now is acknowledge that it is still my garbage?” Heng said: “You can store it temporarily.” He pointed at the pending rack. Li looked at the neat row of parcels awaiting processing. Every one still existed. Every one still carried its attribution. Only the formal discard workflow was unfinished. “Then what actually happens when things are normal?” Heng switched the status page to the explanation. There was no lengthy account. Only a short service diagram: resident association → classification → discard → closure → association no longer required Li finished reading. “So garbage doesn’t disappear either?” “Not necessarily.” “Then where does it go?” “Depends on the next frame.” “You don’t know?” “This service doesn’t need to know.” Li thought that sounded like yesterday’s registration counter. The management system’s attitude toward the universe seemed consistently to be: Know only as much as the job requires. She put the garbage bag on the pending rack. The rack lit up. The system confirmed: ⟦◫ ∶ ! ⋈ ⊚ □ ▣⟧ ⟦⊚ ∶ ⊘ ⋈ ⊚ □⟧ ⟦◫ ∶ ∴ ⋈ ⊚ □⟧ Li took a look. “I still don’t acknowledge it.” Heng said: “Yes, you can.” “Really?” “Yes, you can.” Li was a little surprised. “Then why were you arguing with me?” “I wasn’t disputing your refusal to acknowledge it.” Heng pointed at the ledger. “I was only saying it still counts as yours.” Li fell silent. The second Li laughed beside her. The first Li turned. “Don’t laugh.” “I said that yesterday too.” “You said everything yesterday.” “That was you too.” Li did not want to discuss identity anymore. She looked at the garbage-processing status. “When will it resume?” Heng said: “I don’t know.” “Am I still responsible for it today, then?” “Yes.” Li looked at her bag on the pending rack. “I’ve already dissociated myself from it.” Heng glanced at the public ledger. “You can keep thinking that.” There was a pause. “Until the system resumes, it can keep counting as yours too.” Li left the revocation zone. After a few steps, she turned back. The bag was still there. It had not disappeared. It had not followed her. Nor had it acquired a soul. It simply sat quietly in a temporary-storage slot marked with her stable address. She suddenly felt that this was more annoying than having a soul. The second Li followed behind. “Shall we come back tonight to see whether the service has resumed?” The first Li said: “Don’t.” “What about the garbage?” “That isn’t mine.” An attribution reminder immediately sounded from the revocation zone behind them. Both Lis quickened their pace. Today’s garbage still existed. Worse, it had a complete record. ## Chapter 05 · The Breakfast Shop Refuses Customers Who Have Not Been Born Yet The breakfast shop near the Seventh Residential Fold’s eastern turning point opened earlier than most residents every day. Not because its owner was industrious. Because that area used three common kinds of morning. If the shop accommodated only one, people in the other two would count lunch as part of breakfast time too. So a very simple sign always hung outside: If you are hungry now, it counts as breakfast. Xian liked this shop. Few rules. Fast food. Most importantly, she had a membership. When she arrived that day, the shop assistant was staring at a rejected order on the service interface. The stable address on the order was hers. But not this present version of her. ⟦◬ ◒ ◒⋔⟧ ⟦Ϟ ◒⋔ ☼□⟧ Xian stepped up to the counter. “This is mine, isn’t it?” The assistant looked up at her, then down at the order. “It is.” “Then why was it rejected?” “This version has no membership.” Xian paused. She looked to her right. Another self stood by the wall. Or, more precisely— A self that had not yet decided whether to become real. That future branch wore slightly warmer clothes than the present Xian. She held nothing, but had already firmly chosen a fried egg and a hot drink at the counter. They looked at each other. The future branch spoke first. “I want this tomorrow.” The present Xian said: “Don’t decide for me.” “I’m only ordering breakfast.” “All the more reason not to.” The assistant stayed out of their argument. He merely pushed the rejection screen a little closer to Xian. ⟦⊘ ⋈ ◒⋔ ☼□⟧ ⟦◒ ∶ ⋈ ◒⋔ ◒⟧ ⟦! ⋈ ◒⋔ ☼□⟧ Xian studied it for a while. “She is me.” “Yes.” “And I have a membership.” “Yes.” “So she has a membership.” “No.” Xian looked at the assistant. The assistant looked back. Neither thought they had said anything strange. Xian decided to try another approach. “You recognize that she’s me?” “We do.” “Her address is associated with mine?” “Yes.” “What if she really does become me in the end?” The assistant thought for a moment. “Then she can use whatever membership relation you hold at that time.” “What about now?” “She doesn’t have one now.” The future branch asked from beside her: “Can I sign up now, then?” The assistant switched the interface to the registration page. The screen paused for half a second. Then switched back. “No, you can’t.” Xian turned. “Why?” “She isn’t stable enough yet to hold this service relation independently.” The future branch was displeased. “But I can already be hungry.” The assistant nodded. “That’s true.” “I can be hungry, but I can’t buy food?” “Yes.” “This rule is awful.” “Also true.” For the first time, Xian warmed to the assistant a little. At least he did not pretend the institution itself was elegant. She called up her own membership status. “Then use mine.” The shop assistant said: “You can buy it.” “I want to buy it for her.” “Then you buy it.” “So she can actually eat?” “I never said she couldn’t.” Xian looked at him. “What exactly are you rejecting?” The assistant pointed at the order. “Her using her own branch relation to place an order.” “What if I order through mine and then give it to her?” “That’s your business.” The future branch stepped forward. “I want the same.” Xian turned around. “Stop ordering for me.” “I’m ordering for myself.” “It hasn’t been decided whether you are me.” “So even being hungry now has to wait until you decide?” The two Xians began to find each other disagreeable. A customer behind them tapped the counter gently. “Excuse me.” Xian turned around. A version carrying a branch marker stood beside that customer too. Their future branch already had breakfast in hand. Xian pointed at her. “Why can she do it?” The shop assistant took a look. “A household service relation.” “What?” The customer explained: “I added all my observable future branches to the household account.” Xian was silent for two seconds. “You can do that?” “Yes, you can.” “Why didn’t you tell me?” The shop assistant said: “You didn’t ask.” Xian was now absolutely certain that future branches were not today’s most annoying thing. She opened the service settings. Searched for ages. Found no household account. “Where is it?” The assistant pointed. “Your branch policy is set to ‘Do not allow unrealized continuations to inherit service eligibility in advance.’” Xian froze. “Who set that?” The interface displayed: N.XIAN Xian turned toward the future branch. The future branch looked back. “Did you set this?” she asked. “I haven’t lived that far yet.” “Then I set it.” “It looks that way.” Xian began trying to remember when she might have done such a thing. She remembered quickly. Last time, one of her future branches had ordered three months of breakfasts in advance. That branch was never realized, but the bill had reached temporary storage first. She had turned off advance inheritance as soon as she got home that day. Xian buried her face in her hands. The future branch politely waited for her to accept this fact. The assistant waited too. So did everyone behind her. Finally, Xian looked up. “All right.” She pointed at herself. “I’ll buy it.” The assistant nodded. ⟦◒ ∶ ⋈ ◒ ☼□⟧ The order was approved. The future branch’s original order remained rejected. ⟦⊘ ⋈ ◒⋔ ☼□⟧ Xian looked at the two statuses side by side. “So it isn’t that you refuse to sell to my future self.” “No.” “And it isn’t that she doesn’t exist.” “No.” “She simply has no service relation with this shop.” “Yes.” Xian took the breakfast. “That sounds much more boring than ‘No dining before birth.’” The shop assistant said: “We have no such rule.” The future branch said beside her: “I think you could add it.” “Shut up.” The assistant called up the next customer’s order. Xian carried her breakfast to a nearby seat. The future branch followed. “So can I eat?” Xian glanced at her. “Weren’t you very good at ordering for yourself just now?” “It was rejected.” “That’s your problem.” The future branch was silent for a second. “Yours too.” Xian looked down at her breakfast. That was hard to argue with. She pushed the plate a little toward the middle. The future branch reached for it. The shop’s service interface did not react. Just as the assistant had said. It governed only who was eligible to order. Not who ate after the purchase. Xian was about to say something when the future branch suddenly paused. Her outline faded slightly. She did not disappear. One possibility had merely lost a little local weight for the moment. Xian looked up at her. ⟦◬ ◒ ◒⋔⟧ It was still there. Reassured, Xian took a bite. The future branch watched her. “Will you really eat this tomorrow?” Xian said: “I’m not sure now.” “Why?” “Because you’ve already eaten it.” The future branch thought for a moment. “Then am I making myself never be born?” Xian thought about that too. Then pulled the other half of breakfast back toward herself. “Don’t eat yet.” The future branch was displeased. The assistant glanced at them from a distance. Said nothing. He had already started processing a much more ordinary order. At least that one had only one customer. ## Chapter 06 · The Neighbor Borrowed Wednesday The first to notice the problem on the day Wednesday disappeared was not the administrator. It was the breakfast shop. They opened as usual, entered all three common kinds of morning on the service board as usual, and hung “If you are hungry now, it counts as breakfast” outside as usual. Then the first customer who wanted the Wednesday set found there was no Wednesday on the menu. The shop assistant took a look. Looked again. “Strange.” Someone beside them asked: “Sold out?” “No.” “Discontinued, then?” “Not that either.” The assistant called up the schedule. The cycle connected the previous position directly to the next. The interval between them was perfectly clean. Not blank. Not an error. The slot simply was not there. The shop went quiet for a second. Someone said: “Oh.” Then everyone continued eating breakfast. The Seventh Residential Fold had always tolerated this sort of thing well. As long as it did not affect settlement. Xian was getting ready for work when she heard. She walked to the dwelling’s shared schedule board. The cycle slots that should have followed an orderly arrangement now had one position missing in the middle. ⟦◬ ◫ ⌖ ▣⟧ ⟦Ϟ ⋈ ⌖ ▣⟧ ⟦⊘ ⋈ ⌖ ▣⟧ Xian stared at the position. “What day is it?” Someone beside her answered: “Not Wednesday.” “I know it isn’t.” “Then what are you asking?” Xian thought for a moment. “I want to check whether I skipped something.” The public board was honest. She had not. The dwelling had. When Xian found Heng, he was at the schedule terminal with several residents already waiting. The first asked: “So we don’t have to work today?” Heng said: “Depends on which frame your obligation is bound to.” The second asked: “What about school?” “Same.” The third asked: “Appointments?” “Same.” The fourth was delighted. “So I get another day off?” Heng glanced at her. “You already had today off.” “So I get an extra Wednesday I have no use for?” “There is no Wednesday locally.” “Even better.” She left. Xian reached the front. “It really isn’t here locally?” “Not at present.” “Only us?” Heng called up several nearby dwelling frames. The two next door still had it. The more distant ones did too. Only this building’s schedule relation had been excluded. Xian looked at the display. “So Wednesday hasn’t disappeared.” “No.” “We just can’t reach it.” “Yes.” “Who took it?” Heng glanced at the operations log. “A neighbor.” Xian waited. “Which neighbor?” “That doesn’t matter.” “How can it not matter?” “Because what we need to handle now is the local schedule.” “How long did they borrow it for?” “It isn’t due back yet.” Xian was about to ask more. Then remembered something more important. “Do I still have to work my shift today?” Heng switched to the local obligation. ⟦◒ ∶ ! ⋈ ◒ ⌖ ▣ ?⟧ ⟦◫ ∶ ⊘ ! ⋈ ◒ ⌖ ▣⟧ “It doesn’t count.” Xian immediately grew much calmer. The resident complaining about a canceled appointment fell silent too. “Certain?” “There is no locally reachable Wednesday. This frame will not record you as absent.” Xian nodded. Then asked: “What about settlement?” Heng looked at her. “What?” “Settlement.” “Which one?” “The work cycle.” Heng called up another ledger. ⟦◒ ∶ ∴ ⋈ ◒ ⌖ ?⟧ ⟦◫ ∶ ∴ ⋈ ◒ ⌖⟧ “It counts.” Xian checked again. “Wednesday still counts?” “In the public ledger.” “Even if we don’t have it here?” “Yes.” “Even if I didn’t go to work?” “It isn’t that you didn’t go.” “What is it, then?” “You have no reachable workday.” Xian stood there, carefully absorbing that sentence. The resident with the canceled appointment asked: “That counts too?” Heng said: “The local schedule and public ledger are two different frames.” They thought about it. “What about my appointment fee?” “Ask the appointment system.” They turned and left. Heng was evidently pleased that this question was not his responsibility. Xian had not left yet. She looked at the public ledger. Then the local schedule. Then the public ledger again. “So I don’t have to work today.” “There is no active local obligation for that slot.” “And settlement still counts.” “Yes.” “When will Wednesday be returned?” Heng glanced at the restoration record. ⟦◒ ∶ Ϟ ⋈ ⌖ ▣ ?⟧ ⟦◫ ∶ Ϟ ⋈ ⌖ ▣ ⧗⟧ “Later.” “How much later?” “It hasn’t resolved to a specific position yet.” Xian fell silent. Normally, she would have demanded something more precise. This time she did not. “No hurry, then.” Heng looked up. “What?” “Settlement still counts anyway.” “Yes.” “And I don’t have to work.” “Locally, not at present.” “Then don’t rush the neighbor yet.” Heng looked at her for two seconds. “I wasn’t going to.” Xian left in excellent spirits. At the schedule board, several residents were discussing how to use this unexpected vacancy in the day. Some wanted to sleep. Some wanted to move Wednesday’s cleaning to Thursday. Someone insisted that if Wednesday did not exist, Wednesday’s garbage could not be counted against Thursday. The garbage revocation zone immediately posted a notice: Garbage classification follows parcel relations, not weekday names. Xian glanced at it as she passed. It seemed reasonable. She looked at the public schedule again. The neighboring dwelling’s Wednesday was still lit normally. A resident from another building happened to pass and saw her watching the board. “You have no Wednesday here?” “Mm.” “Convenient?” Xian considered. “Very convenient at present.” The other resident nodded. “We still have ours.” “Lend it to me?” They gave the matter serious thought. “No, I have a class tonight.” Xian nodded too. That answer was entirely reasonable. Before reaching her own dwelling, she met someone else. They carried a missed-delivery notice. “Excuse me, where has Wednesday gone?” Xian pointed toward the management terminal. “A neighbor borrowed it.” “How long?” “They’ll return it later.” “What about my Wednesday parcel?” Xian said: “I don’t know.” There was a pause. She added: “But settlement still counts.” They looked at her. “I’m asking about the parcel.” “Then ask the courier.” Xian suddenly understood why Heng had been so relaxed. Returning questions outside your frame to the correct service felt wonderful. That afternoon, the dwelling’s board updated once. Wednesday was still absent. ⟦◬ ◒ ⌖ ▣⟧ Xian checked her settlement again. It was still there. ⟦◒ ∶ ∴ ⋈ ◒ ⌖⟧ She closed the terminal. Made no request for its return. That night, the whole building was missing a Wednesday. No crack appeared in the universe as a result. Time did not stop either. Only a few schedules needed rearranging. And at least one person, being paid as usual without working, developed considerable tolerance toward a neighbor borrowing a shared calendrical slot. Wednesday would come back later. Nobody was especially impatient. Xian certainly was not. ## Chapter 07 · Do Not Unfold a Fourth Direction on Your Balcony Xi’s school assignment had originally been simple. At least, that was what the teacher said. The assignment required: Establish a new locally reachable direction without disrupting the dwelling’s three commonly used directions, insert a standard test object, and retrieve it intact. One final line had been added: Do not perform this in a shared passage. Xi’s first thought on reading that was: Then use the balcony. There was nothing wrong with the thought itself. The problem was that she had read only the school’s rules. Not the dwelling’s. That afternoon, Xi opened the balcony door. Moved the half-dried laundry left. Then pushed right a plant that needed little light but insisted on turning toward the light source every day. Cleared the middle. She took out the direction marker issued by school. Step one: establish a local anchor. Step two: confirm the three existing directions are stable. Step three: supply a new reachability relation at a position that is “not one of the first three directions.” Xi worked slowly. And carefully. A few minutes later, a position difficult to describe with “where” had appeared beside the balcony railing. It was not left. Not right. Not up. Not down. Reaching toward it, she could touch another usable position without her hand moving along any of the original three directions. Xi’s eyes lit up. She inserted a standard test cube. Half the cube disappeared. The other half remained on the balcony. She pulled it back. Intact. Xi immediately took a picture and sent it to the class group. Classmate one: “You did it?” Xi: “First try.” Classmate two: “Mine leaks into the living room.” Xi: “You didn’t lock your anchor.” Classmate two: “My mother told me to stop.” Xi was about to reply “technical problem” when the dwelling system issued a notification first. ⟦Ϟ △ ⊥ ▣⟧ ⟦◬ ◫ ⊥ ▣⟧ Xi took a look. Ignored. Thirty seconds later, the doorbell rang. Heng stood outside. Xi opened the door. “What brings you here?” “The balcony.” “What about the balcony?” “It has an extra direction.” Xi glanced inside. “You send notifications about this now too?” “Changes to residential structure trigger notifications.” “That isn’t residential structure.” “Let me look.” Xi was about to say there was no need. But Heng had already reached the balcony. The new direction was still there. And very stable. Stable enough that the test cube could now remain entirely inside, with only a corner exposed. Heng reached out. Did not touch the cube. He changed his mode of entry. Touched it. Xi was a little proud. “Well?” Heng said: “Declare it.” Half the pride immediately left her face. “This is homework.” “I know.” “Homework needs declaring too?” “If your homework becomes residential structure.” “It isn’t a room.” Heng pointed at the cube. “Can you put things in it?” “Yes, you can.” “Retrieve them?” “Yes, you can.” “Is the entrance on your balcony?” Xi began to feel that these questions were heading the wrong way. “...Yes.” “Then measure it first.” ⟦◫ ∶ ! ⧈ ⊥ ▣⟧ Xi frowned. “How do you measure this?” “As usual.” “It isn’t in the original three directions at all.” “Then don’t measure it using those directions.” Xi looked at Heng. “You just said something completely unhelpful.” Heng took out the residential measuring device. “It is helpful.” He aimed its detection range at the additional direction. The instrument did not force it back into familiar length, width and height. It established a usable local window along the direction itself. Xi watched the values slowly stabilize. “This counts too?” “It counts.” “But that isn’t a normal size.” “I’m not measuring a normal size.” “What are you measuring, then?” “How much you can use.” Xi fell silent. It sounded like something Heng had said when Li complained about pet registration a few days earlier. Xi began to understand that adults did not always have many answers. They were simply good at narrowing questions until a form could use them. Heng sent her the measurement results. “Fill it in.” Xi did not take them. “Wait.” She went to the balcony and retrieved the test cube. Then reduced the new direction’s local extent. A range large enough for a small table slowly shrank until it could hold only a schoolbag. “What about now?” Heng measured again. “Still fill it in.” Xi shrank it further. This time it was only the size of a pencil case. Heng measured again. “Still.” Xi glared at him. “It’s so small now.” “A small renovation is still a renovation.” “This isn’t a renovation.” “What is that?” “Homework.” “Homework is its use.” Heng pointed at the balcony. “This is its structure.” Xi was unconvinced. She opened the class group. Called the teacher directly. The teacher answered quickly. A desk appeared on the screen first. Two seconds later, the teacher emerged from another reachable surface of the desk. “What’s wrong?” Xi turned the camera toward Heng. “The administrator says my homework counts as a residential renovation.” The teacher looked at the new direction. “Where did you open it?” “The balcony.” The teacher paused. “Didn’t the school say not to do it in a shared passage?” “The balcony isn’t a shared passage.” “Yes.” Xi immediately looked at Heng. Heng did not react. The teacher continued: “But those are only the school’s rules.” Xi’s expression froze. “So?” “You must handle the dwelling’s regulations yourself.” “The assignment says we can do it in a dwelling.” “You can.” “Then why must I declare it?” The teacher thought for a moment. “Because ‘You can do it’ and ‘You don’t need to declare it’ are not the same sentence.” Heng nodded once. Xi immediately said: “Don’t nod.” Heng stopped nodding. The teacher examined Xi’s directional structure. “Nicely done.” Xi brightened a little. “Really?” “Very stable.” “Can I submit it, then?” “Submit the measurement record with it.” Xi looked at Heng again. Heng pushed the data a little closer to her. The teacher said: “Perfect.” The call ended. Xi had now lost the last adult she could appeal to. She stood on the balcony with folded arms. “But it really isn’t in the original three directions.” Heng said: “I know.” “How can that count as building another bit of the house?” “Can you enter it?” “Yes.” “Put things in?” “Yes.” “Retrieve them?” “Yes.” “Is the entrance in your home?” Xi did not answer. Heng said: “Then it is associated with your home.” Xi looked at the new direction. ⟦△ ∶ ⊘ ⋈ ⊥ ▣ ?⟧ ⟦◫ ∶ ⋈ ⊥ ▣⟧ She made one final effort. “Then I’ll shrink it until it can hold only a pen.” She really did. The new direction became an almost invisible local opening. Xi inserted the pen. It disappeared. Then she retrieved it. Heng measured again. Xi stared at him. Heng said: “Still required.” Xi took a deep breath. “How small do your regulations go?” “Until it is no longer usable residential structure.” “How small would not count?” “When you can’t put that pen in, we can discuss it again.” Xi looked at the pen. Then the new direction. Then the declaration form. Finally, she enlarged the new direction slightly. Heng asked: “What are you doing?” “It needs declaring anyway.” She put her schoolbag in. “Then I’m at least going to use it.” For the first time, Heng showed something resembling approval. “Reasonable.” Xi started filling in the form. First field: Type of added structure She entered: School homework. The system rejected it. Xi gritted her teeth. Changed it to: Additional local direction. Approved. Second field: Usable extent range She entered Heng’s measured values. Third field: Use Xi paused. Wrote: Storing a schoolbag. Heng saw it. “Not homework?” Xi said: “The homework is finished.” “What about this?” “Storage now.” Heng nodded. “Then the declaration is even more appropriate.” Xi suddenly wanted to close the direction. But she restrained herself on remembering that tomorrow she would not have to dump her schoolbag in the living room. The form was submitted. The dwelling system accepted it. The new direction remained quietly open on the balcony. Xi put her remaining homework materials inside too. That evening, a classmate asked in the group: “Is your fourth direction still there?” Xi replied: “I kept it.” “Isn’t the homework done?” “It’s a cupboard now.” The classmate replied with a string of silence symbols. Xi was pleased. From an assignment that required a declaration, she had at least obtained storage that occupied none of the original three directions. The teacher’s feedback next day contained only one sentence: Excellent structure. Administrative matters are your own responsibility. Xi thought the first half mattered more. ## Chapter 08 · Childhood Memories Cannot Pay the Rent On the day Li paid her rent, she did not have enough ordinary settlement assets. That was not unusual in itself. Over the last two cycles, she had spent her liquid allowance on things that would supposedly become more troublesome if she did not buy them now. These included a storage frame that rearranged its own drawers, tableware with weight only at night, and three gray balls Rift adored whose purpose Li still did not know. So when she sat in the residential settlement area, the system very politely informed her: Insufficient ordinary settlement assets. Li took a look. “How much am I short?” Heng displayed the gap. Li looked and thought it was manageable. She could make it up. She simply did not want to right now. She scrolled down her available assets. Several entries were too small. One was an unfinished future credit, currently unusable. Another was payment for helping someone recover a lost direction last month, but that relation could be exchanged only for transport services. At the bottom, she stopped. There was something very old there. Not an object. Nor a simple playable image. It was more like a piece of the past still bound to herself. Li dragged it into the evaluation frame. The screen was quiet for a second. Then a very high valuation appeared. Li raised an eyebrow. “This is enough.” Heng looked up. “What?” “This.” She pushed the trace toward him. ⟦◬ ◫ ◈ ⊚⟧ ⟦⋈ ◈ ⊚⟧ Heng examined the relation first. Then the content. It was a very early Li. Much smaller. Standing in a courtyard that no longer existed. Rain had just fallen. A little water collected in the cracks between stones. Someone in the distance called her home. She did not go. Something bright lay beneath the courtyard wall. Convinced it was a treasure, she crouched and dug for a long time. What she finally unearthed was only a broken piece of transparent material. But the childhood Li was delighted. Holding it up to the light, she found that the world split into two layers through its crack. The trace retained more than the image. It also held the smell of air after rain, the cold of wet ground against her knees, impatience at mud on her fingers, and her first sense that: The same thing could become an entirely different world depending on how you looked at it. Heng closed the trace. Li asked: “What is it worth?” Heng checked the valuation again. “A lot.” “Enough?” “Enough.” Li immediately pushed it into residential settlement. ⟦⊚ ∶ ¤ ◈ ▣⟧ ⟦◫ ∶ ∴ ¤ ◈ ▣ ?⟧ The system made one processing round. Rejected. ⟦◫ ∶ ⊘ ∴ ¤ ◈ ▣⟧ Li looked up. “Why?” “You cannot pay that way.” “Didn’t you just say it has a lot of value?” “Yes.” “Why can’t something valuable pay the rent?” Heng did not answer. He first called up another resident’s settlement. They used ordinary transferable service credits. Evaluation. Approved. closure。 The whole process took less than five seconds. The resident left with a completion notice. Li looked at her. “Hers is clearly worth less than mine.” “Yes.” “Then why can she use it?” “Because it can be transferred in full.” “Mine can’t?” “It can be transferred.” Li paused. “Are you deliberately talking like this?” “No.” “It has value.” “Yes.” “It can be transferred.” “Yes.” “It cannot be used for this payment.” “Yes.” Li placed her hands on the table. “Then you had better have a very good reason.” Heng unfolded the relations of her childhood trace. ⟦◫ ∶ ⋈ ◈ ⊚⟧ Li took a look. “So what?” “It is still anchored to you.” “Then disconnect it.” Heng looked at her. “Are you sure?” “How else can it be transferred?” Heng did not execute the operation. He first made a preview of the possible settlement result. The childhood trace was excluded from her identity relation. In the image, young Li still stood in the courtyard. The rain remained. So did the transparent fragment. But the present Li felt no familiarity when she looked at it. She knew it had happened. Knew the person in the image was theoretically herself. Yet had no feeling of “That was me.” More troublingly, several connected continuity relations began to fade too. She did not disappear entirely. Nor lose all her memories. Part of “how my later self came to be this way” simply no longer connected. Li stared at the preview. Only after several seconds did she say: “Is this a simulation?” “Yes.” “Would an actual transfer do this?” “Broadly.” “Broadly?” “The actual side effects might be greater or smaller than the preview.” “Your preview isn’t very convincing.” “Which is why residential settlement does not accept it.” Li closed the screen. Still unconvinced in what she said. “Isn’t it just a memory?” Heng said: “No.” “What’s the difference?” “Why couldn’t your manifestation in the hallway in the first episode simply be dragged away?” Li remembered immediately. “It hadn’t finished synchronizing.” “We were looking at reconstructible continuity then.” “So?” “This trace is not an ordinary stored record.” Heng reopened the childhood trace. “It still has an anchored relation to your present self.” Li watched the rain-soaked courtyard. “So if I sell it, I won’t remember?” “It may be more than forgetting.” “What is that?” “You might become someone who knows it happened but no longer regards it as part of her own life.” Li frowned. “That still sounds like forgetting.” “It isn’t the same.” “How isn’t it?” Heng thought for a moment. “You can forget an event while it still participates in how you became who you are now.” Li did not answer immediately. Heng added: “This trace is closer to that.” Silence lasted a while. Li checked the valuation again. It really was high. Enough for more than this cycle’s rent. Enough to settle the next cycle too. She was seriously tempted for about ten seconds. Then asked: “What if I cut off only a small part?” “It can be reevaluated.” “Which part matters less?” “That is not a decision residential settlement makes for you.” “Aren’t you the administrator?” “Not the editor of your life.” Li gave him a disdainful look. “Sometimes you really do sound like an announcement.” “Thank you.” “That wasn’t praise.” “I know.” Li pulled the trace back toward herself. But did not close it immediately. Her childhood self still crouched in the rain. She suddenly remembered taking the transparent fragment home and keeping it for many years. Where it went afterward, she really had forgotten. That ordinary forgetting did differ from the preview’s “known, but no longer belonging to oneself.” Li withdrew the settlement request. ⟦⊚ ∶ ⊘ ¤ ◈ ▣⟧ Heng closed the rejection preview. Then displayed the rent shortfall again. Li took a look. “So now what?” “The rent still needs paying.” ⟦◫ ∶ ! ⋈ ⊚ ▣⟧ “I know.” Li scrolled through her assets again. She stopped at the tableware with weight only at night. “Can this be sold?” Heng took a look. “Yes, you can.” “Will it rewrite me?” “No.” “Is it worth a lot?” “No.” Li sighed. “What about the storage frame?” “A resident wants it.” “Really?” “Some people really like drawers organizing themselves.” Li was a little reluctant to part with it. “What about Rift’s three balls?” Heng said: “Don’t touch those.” “Why?” “I don’t know.” “You don’t know, but you’re telling me not to touch them?” “Does Rift know you want to sell them?” Li went quiet. They both looked down. Rift had appeared beneath the table at some point. All three gray balls were gone. Li: “...” Heng: “Looks like she knows.” In the end, Li sold the tableware and some ordinary service credits she no longer needed. The rent was barely covered. Her childhood remained. Before leaving the settlement area, Li looked back at the trace. Its valuation was still high. She moved it from “available settlement assets” back to her private archive. There was a pause. Added a marker: Do not use this to pay rent. The marker had no institutional effect. But Li felt it was necessary. ## Chapter 09 · The Convenience Store Gave Two Possible Tomorrows as Change Xian only wanted to buy a drink. When she entered the convenience store, she had not even brought a future branch with her. At least, she thought she had not. The self-checkout was quiet that day. Only one resident stood ahead of her, buying two parcels, a snack whose flavor had not yet been decided, and something resembling a bag that had an inside only when picked up. Checkout went smoothly. Xian’s turn came. She scanned the drink. Then a packet of something small. The screen displayed the total. She paid. ⟦◬ ◒ □⟧ ⟦◒ ∶ ¤ □⟧ ⟦∴ ¤ □ ◒⟧ Transaction successful. That part was perfectly normal. Xian put her purchases in the bag and waited for change. The machine beeped. Then produced two settlement notices. Not two coins. Nor two pieces of paper. They were more like two usable claims temporarily attached to her transaction record, each to become something later. The first carried a future-branch marker. So did the second. And they were different. ⟦Ϟ ⫯⋔ ◒⟧ ⟦Ϟ ⫯⋔ ◒⟧ Xian stared at them. “...What?” The checkout displayed without expression: Change completed. Xian looked up. The shop assistant was arranging shelves. “Excuse me.” The assistant came over. “What’s wrong?” Xian pointed at the two settlements. “It says the change is complete.” “Mm.” “Which one is mine?” The shop assistant took a look. “Both are associated with this transaction of yours.” Xian frowned. “I’m not asking whether they’re associated with me.” She selected the first. “This one?” The assistant looked: “If the first future branch is realized, this one becomes stable.” Xian selected the second. “This one?” “If the second is realized, this one.” “So which one is actually mine?” “We don’t know yet.” Xian fell silent. “Then how dare you write ‘Change completed’?” The assistant opened the accounting details. ⟦◒ ∶ ∴ ¤ ⫯ ?⟧ ⟦∴ ¤ ⫯ ◒⟧ “The value is correct.” “I know the value is correct.” “And the ledger is settled.” “I know that too.” “Then what’s the problem?” Xian looked at him. “I have no money I can use right now.” The assistant pointed at the two branch settlements. “Yes.” “Which one?” “Depends on what happens later.” “I said now.” The assistant paused for two seconds. “Then there is no stable form right now.” Xian took a deep breath. Lately, she had worked very hard to accept: • future branches can come early to order breakfast; • Wednesday can be temporarily absent; • the public ledger and local schedule can each do their own accounting. But she really felt: Change should at least belong to the present. She dragged the first settlement to the nearby drink dispenser. Tried buying another, cheaper bottle. The machine scanned it. Rejected. Reason: The settlement is not yet stable in the current frame. Xian tried the second too. Same result. She looked back at the assistant. His expression looked like: That is precisely what I just meant. Xian said: “Don’t make that face.” “I’m not.” “You are.” The assistant did not argue. The person behind her peered over. “Branch change?” Xian turned. “You’ve had this too?” “I use it often.” “Is it useful?” “Very useful.” Xian looked at them. They said: “I have two regular continuations. One passes the north market, and one goes to school. With change bound to a branch, I use it wherever that branch is realized. I don’t have to move it myself.” Xian imagined that. “So you find this convenient?” “Very.” “Don’t you want to know now which portion you are getting?” “Why would I need to know?” Xian looked at him. They looked back at her. Both became certain at the same time: The other’s habits were incomprehensible. The assistant asked: “Would you like me to change your settlement preference?” “It can be changed?” “Yes, you can.” Xian immediately held out her terminal. The assistant opened the settings. They read: Preferred: current-frame stable settlement Alternative: branch-conditioned settlement Condition: automatic switch when stable-form inventory is insufficient Xian finished reading. “So you’re out of change?” “No.” “Then why did it switch?” The assistant pointed at the last line. The local current-frame settlement pool is being rebalanced. “How long?” “A moment.” “How long is a moment?” “I don’t know.” Xian closed her eyes. She had heard that sentence too often lately. She looked again at the two branch settlements. One would become usable change if she followed continuation A tomorrow. The other if she followed continuation B. Their values were correct. Nobody had deceived her. The system was even more precise than ordinary change. She still disliked it. ⟦◒ ∶ ⊘ ⧗ ⫯⟧ ⟦◒ ∶ ⊘ ⫯⟧ “I don’t want it.” The assistant asked: “Neither portion?” “I don’t want this form.” “Then you need to wait for the current pool to return.” Xian checked the time. She did not want to wait. She looked back at the shelves. The row nearest the checkout held very ordinary little products. Batteries. Tissues. Candy. Transparent clips inexplicably categorized as stationery. She picked up a packet of candy. Scanned it. A small difference remained. She picked up a mint too. Scanned again. Difference: 0 Xian looked at the screen. So did the assistant. ⟦Ϟ □ ◒⟧ ⟦∴ ¤ □ ◒⟧ ⟦⊘ ⫯⟧ Both branch settlements withdrew from this transaction’s settlement frame. They had not disappeared. Nor been destroyed. Simply: The transaction no longer needed them. Xian looked at the clean checkout screen. Her mood improved at once. The shop assistant said: “This works?” “Yes, you can.” “You’ve bought two more things you didn’t originally need.” “I need them now.” “Why?” “Because they let me avoid taking tomorrow’s change.” The assistant considered. “Reasonable.” The resident who liked branch settlement said from behind: “You could learn to use it.” Xian put the candy in her bag. “I know how.” “Then why do you—” “I just don’t want to use it for change.” She paused. “Or breakfast.” They did not understand. That was all right. Xian left the convenience store with her purchases. At the door, she paused. Looked back at the two settlements. They no longer belonged to this transaction. But her future branches were perfectly intact. One might go north tomorrow. The other might not. Both remained. Xian watched for a while. Then left contentedly. The universe still held many possibilities. This time, she simply did not have to wait for one of them to be realized before knowing how much change she had actually received. ## Chapter 10 · The Child Upstairs Has Grown a New Timeline When Xi discovered that she had grown something that morning, her first reaction was to pull the blanket back over herself. She did not scream. Nor call an adult. She only wanted another five minutes of sleep. The new thing did not seem to hurt for now. Five minutes later, she opened her eyes. It was still there. That made things a little troublesome. It was neither a hand nor a foot. Nor a new manifestation. It was more as though a temporal relation that had required a detour to observe had suddenly acquired a direction by which she could reach it directly. Sitting on the bed, Xi looked at two things on her desk. One was yesterday’s half-finished homework. The other was this morning’s submission check, not yet happened but already scheduled by the school. Previously, only the schedule service could order those two events for her. Now she did not need it. She knew at a glance. Not a guess. Not a system prompt. She could see the relation directly. Xi was briefly stunned. She tried two even duller events. Today’s turn of the balcony plant toward the light. The kitchen heater finishing breakfast. Previously, those two events had not needed direct comparison within her own observation frame. Now she could compare them. Xi stared at the air. “Oh.” She thought about it. “This is convenient.” Then went to brush her teeth. —— Halfway through breakfast, Xi remembered: Newly grown things usually need measuring. She had learned that after doing her homework on the balcony last time. Very reluctantly, she opened the dwelling terminal. The system had known before she did. ⟦⌑ △ ⊥⧗⟧ ⟦◬ △ ⊥⧗⟧ ⟦⧈ ⊥⧗ △⟧ The notification contained only one sentence: new stable capacity detected. Xi took a look. “How did it know faster than me?” The terminal did not answer. She forwarded the message to Heng. Heng came upstairs within ten minutes. Not because it was serious. He had already been nearby, inspecting another household’s declaration for using the outside of its window as a storage layer. By the time Heng entered, Xi had measured the new capacity three times. “Morning.” “Morning.” “Where?” Xi pointed at herself. Heng looked at her. Xi added: “Not a bodily sort of ‘where.’” “I know.” She opened the measurement. Heng studied it. “Stable.” “Mm.” “Repeated result?” “Five times.” “You said three just now.” “I tried twice more while you were coming upstairs.” Heng nodded. Xi looked at him. “So it’s real?” “Apparently, at present.” “It isn’t something left over from the homework?” There was reason for the question. The additional direction from EP007 was still on the balcony, and she was now actually using it as a cupboard. Heng examined the two associations separately. “No.” Xi brightened a little. “So it’s my own?” “Yes.” ⟦⋈ △ ⊥⧗⟧ Xi was quiet for two seconds. Then asked: “Do I count as two now, then?” Heng looked up. “What?” “I have the original set.” Xi pointed left. “Now there’s another axis.” Pointed right. “Isn’t that two sets?” “No.” ⟦△ ∶ △∷ ?⟧ ⟦◫ ∶ ⊘ △∷⟧ Xi checked: “So there isn’t a second me?” “No.” “Nor another manifestation?” “No.” “Address?” “One.” Xi visibly relaxed. Heng asked: “Were you worried?” Xi immediately said: “Tuition.” Heng paused. “What?” “If I count as two students, will school charge twice?” Heng looked at her. This time, there really were two seconds of silence. “That was your first thought?” “It matters.” “You’ve grown a new temporal axis.” “That’s why it matters.” Xi called up the school billing page. “Look, I originally had one student address.” “Yes.” “Now the new capacity is bound to me too.” “Yes.” “Will that add another obligation?” ⟦△ ∶ ! ¤ ⋈ △ ⊥⧗ ?⟧ Heng glanced at the dwelling interface. “The dwelling won’t count you as two.” “What about school?” “Ask school.” Xi frowned. “You don’t know?” “I’m not the school.” That was reasonable. So reasonable Xi could not complain. She opened the school service desk. Since lessons had not begun, an automated registrar was on duty. Xi submitted the new-capacity record. The system scanned it. Stable address confirmed: N.XI Added capacity confirmed: one Added student addresses confirmed: zero Then displayed: billing subject unchanged. Xi leaned toward the screen. “So?” The registrar replied: The tuition obligation is bound to the student address, not the capacity count. Heng said beside her: “That means no extra charge.” Xi ignored him. She asked the system again: “What if I grow another later?” billing subject unchanged. “Three?” billing subject unchanged. “Twelve?” billing subject unchanged. Xi began to feel reassured. Finally, she asked: “What if I really become two?” The system paused. Please submit a new declaration after this occurs. Xi closed the screen. “Good.” —— The matter could have ended there. But Xi’s interest in new things rarely stopped at “They won’t charge extra.” She returned to her desk. Pulled out yesterday’s assignment. It contained a particularly annoying part. The teacher had asked her to order several groups of events from different local temporal relations so that they could be compared. Last week, she had needed an external service to establish those comparisons. Not now. Xi took a look. The first group. Ordered immediately. The second. That worked too. The third had originally been the most troublesome. She paused. The new axis naturally unfolded several relations into a comparable structure. Xi’s eyes lit up. She began writing answers rapidly. Heng had not left. He watched for half a minute. “Is that homework?” “Mm.” “You can use the new capacity directly?” “Yes, you can.” “That’s good.” Xi stopped halfway through. “Wait.” Heng immediately knew she had thought of something else. “What?” Xi looked at the homework. Then at the new axis. “If I can compare along different temporal relations simultaneously, can I hand in two sets of answers?” “Why hand in two?” “One using the old method.” “Mm.” “One using the new axis.” “It’s still your homework.” “But there are two methods.” “There is still one student.” Xi frowned. “Why do you keep using the student address against me?” “Because you keep trying to count one student as two.” Xi thought about it. “Can I get two sets of marks, then?” Heng said: “Ask your teacher.” Xi really did ask. The teacher replied quickly this time. No. Xi replied: Why? Teacher: Because you are handing in the same assignment. Xi: But I have a new temporal axis. Teacher: Congratulations. Xi: So? Teacher: So the homework should take less time. Xi looked at that sentence. For the first time, she felt a little regret about growing. —— By the time she reached school that morning, two classmates already knew. One was the classmate who had said yesterday that their additional direction leaked into the living room. The classmate asked as soon as they saw Xi: “You really grew one?” “Mm.” “Does it work?” “Yes.” “Does it hurt?” “No.” “Do you have to declare it?” “No new identity declaration for the dwelling. There is a capacity record.” “What about tuition?” Xi was pleased that someone finally asked the important question. “One payment.” The classmate relaxed too. “That’s good.” Another classmate asked: “Why do you both ask about tuition first?” Both looked at her. “Because it matters.” The teacher entered the classroom. Glanced at Xi. “Congratulations.” Xi was a little wary. “Thank you.” “Since your new axis is stable, you won’t need the external comparison service for today’s ordering exercise.” Xi fell silent. Someone in the class laughed. Xi looked down at her new capacity. Yesterday, she had still thought growing up might be a good thing. Today, she began to discover: The most immediate side effect of a new capacity is usually adults deciding that you can do more things yourself. Before dismissal, the school system updated her record again. student address： one. billing obligation： one. stable capacity： plus one. Xi looked at the three lines and felt the arrangement was reasonably fair. At least it did not mean two tuition payments. As for the extra homework capacity— She decided to find other loopholes later. ## Chapter 11 · Do Not Use True Names in Public Areas When Xi wrote out her complete name, she truly thought she had a sound argument. The school had posted several assignments in the dwelling’s shared area that week. Hers happened to be the local-direction project from a few days earlier. The teacher said: “Remember to sign your name beside your work.” Her classmates were casual about it. Some wrote a nickname. Some left only a shortened class address. One drew something bearing no discernible relation to them and insisted it was a signature. Xi disliked that. If you were signing your name, she felt you should be accurate. Especially since she had confirmed the day before: She still had only one stable address. If there was only one, All the more reason to write the fullest version. At the public noticeboard, she wrote the complete resolver form stroke by stroke. Then stepped back to inspect it. Good. Complete. Clear. Impossible to confuse with someone else. A classmate glanced over. “You wrote it that fully?” “What else would it be?” “I used a nickname.” “That isn’t accurate.” The classmate shrugged. “It’s not as though we’re trying to call you here.” Xi was about to answer: “A name is inherently—” She suddenly stopped. Because she really had come here. Not this self doing the writing. Another local presentation. That Xi should still have been upstairs, putting homework materials into the additional-direction storage declared a few days earlier. But as soon as the public frame resolved the resolver key on the wall, one manifestation was directly re-addressed to the noticeboard. Both Xis looked at each other. The classmate looked at them too. All three were silent for two seconds. The classmate spoke first: “See?” Xi answered: “That doesn’t count.” “What doesn’t?” “It doesn’t mean what you just said was right.” “But you really were called here.” “It wasn’t a call.” “What is that?” Before Xi found a more precise word, the public display issued a prompt. ⟦Ϟ △ ⟟△ ⌇⟧ ⟦Ϟ △∷ ⌇⟧ Then the prompt changed to: Public resolution status: valid Permission status: unconfirmed Xi frowned. “Isn’t this board only supposed to display things?” The classmate said: “It can resolve the author of a work.” “Through a short name, surely.” “You gave it the full one.” Xi glanced at the wall. Then at the self who had been pulled over. That Xi still held a stack of homework papers. “How did you get here?” The other Xi said: “I was upstairs.” “I know.” “Then here suddenly became a reachable position.” “I know that too.” “Then why are you asking?” Xi did not answer. The situation was heading in a direction she disliked: The classmate might actually have been right. The public system refreshed again. The Xi who had been pulled over shifted a little toward the wall. She clutched her papers more tightly. “Can I go back?” “Wait.” “I have other homework to hand in.” “I know.” “Didn’t you just grow a temporal axis? Can’t you read through it faster yourself?” “That isn’t what it’s for.” “Then what use was growing it?” Xi turned and glared at her. The other Xi glared back. The classmate stepped aside. “You two argue among yourselves.” Then Heng approached from the other end of the shared passage. He had not come specifically for Xi. He was still carrying two unrelated residential declarations. A public-resolver warning had merely appeared on his management interface. Heng reached the noticeboard. Looked at the wall first. Then the two Xis. “Who wrote it?” Both Xis pointed at the one who had done the writing. That Xi said: “Me.” Heng glanced at the complete resolver form. “Erase it.” Xi immediately objected. “Why?” Heng pointed at her other self. “Because it is resolving.” “That’s my name.” “I know.” “And I only have one address.” “I know that too.” Xi paused in surprise. “Then why can’t I write it?” Heng opened the public display’s permission layer. ⟦◫ ∶ ! ⊳ ⟟△ ⌇⟧ ⟦△ ∶ ⊳ ⟟△ ?⟧ “Because this isn’t your own resolver frame.” “But the key is mine.” “Yes.” “Then why don’t I have permission?” “Having your own key does not mean this place has to execute it.” Xi stopped. That sounded like the other day’s: Having a new direction does not mean no declaration is needed. She disliked that sentence pattern. It usually meant her next loophole had already been closed. “So I can’t even write my own name?” Heng said: “You can write a display name.” “That isn’t my true complete name.” “It is enough for everyone to know it’s you.” Xi glanced at her classmate. The classmate pointed to her own nickname. “Told you.” Xi said: “You’re talking a lot today.” Heng began excluding the full resolver state from the public frame. ⟦◫ ∶ ⊘ ⟟△ ⌇⟧ The complete form was still visible on the wall. But the resolver capability no longer executed it. A few seconds later, the re-addressed Xi felt the original address path loosen. She stepped back. Not backward in space. Back into her original reachable local structure. The homework papers went with her. The classmate enjoyed watching. “Cool.” Xi said: “What is cool about it?” “Your signature can call you over.” “It isn’t a call.” “What is it, then?” Heng said: “Resolution.” The classmate nodded. “Your signature can resolve you over.” Xi thought that sounded worse. She took the erasing tool and cleared the complete resolver form. Then wrote a short name instead. Only the display label used at school, among classmates and on activity boards. The public display scanned once. No manifestation was pulled over. Nor was there a permission warning. Xi stared at the short name. “Does this really count as me?” Heng said: “It’s enough here.” “But it isn’t complete.” “This place doesn’t need completeness.” “What if someone identifies the wrong person?” “This frame only needs to know which student submitted the work.” “Not the complete identity?” “No.” Xi considered. She suddenly discovered: Accuracy has a frame too. Yesterday, she had been pleased to have only one stable address. Today, she discovered: Having only one does not mean every place should use its fullest form. She looked at the new signature. Still not attractive enough. So she drew a little design beside it. Her classmate asked: “What is that?” “A safer name.” “It doesn’t look like you.” “It isn’t for a resolver to look at.” Heng had turned to handle the next declaration. Xi suddenly called him. “Wait.” Heng turned back. “What?” Xi pointed at the wall. “So I wasn’t signing my name just now?” “You were.” “Then why did you keep telling me to erase it?” Heng looked at her. “Because what you wrote wasn’t an ordinary signature.” He pointed at where the complete resolver form had been. “It was a resolver key.” Xi thought for a second. “Then the teacher’s instruction to ‘sign your name’ wasn’t clear.” Heng said: “You can tell the teacher.” Xi’s eyes lit up. At last, there was someone she could hold responsible. That evening, the teacher received her message: I suggest adding “Use a public-safe display label, not the full resolver form” to the next assignment’s instructions. The teacher replied quickly: All right. A little later, another line arrived: I thought that did not need stating. Xi stared at it for a long time. Finally replied: For students, it does. Then she saved the screenshot. This time, she felt that she really had won a little. ## Chapter 12 · A Power Outage Is Not the End of the World. Really. It began with the hallway briefly dimming. Not the lights. The lights were still on. What actually dimmed was “things being seen normally.” Li was walking home through the shared passage when two local manifestations behind her suddenly faded. Not into translucence. The ordinary observation layer simply could no longer register them. One second, someone had been there. The next, an empty position remained, while the public system insisted the address relation still existed. Li turned around. “...Have I lost two of me?” A nearby resident glanced over. “It looks that way.” “Lost, or just invisible?” “I don’t know.” “That answer doesn’t help.” “I’m just passing through.” The residential displays refreshed together. ⟦◬ ◫ ◌ ▣⟧ ⟦◫ ∶ ⊘ ◌ ▣⟧ A corner vanished from the screen a moment later. It had not broken. That corner had merely lost stable presentation: something still present but no longer willing to be outlined by ordinary observation. Someone shouted from upstairs: “Again?” Another resident replied: “It’s bigger this time.” A third said, with considerable atmosphere: “Invisible darkness is beginning to swallow the world.” Nobody paid attention. The convenience store’s refrigerator was working normally. The breakfast shop was still open too. If the world truly ended, it would not usually single out the residential display layer. Xian emerged from the corner. Half emerged. A branch-linked presentation on her right remained; a piece on the left was missing. Walking was unaffected, but she looked as though the image had forgotten to load. “Can anyone see all of me right now?” Li said: “No.” Xian frowned. “Will my appointment later count me as absent?” Li looked at her. “You’re thinking about your appointment while looking like that?” “What else would it be?” Quite reasonable. Xi’s voice suddenly came from upstairs. “My temporal axis is gone!” She rushed down. She herself looked complete. But the additional temporal axis grown a few days earlier was entirely invisible in ordinary residential presentation. Xi plainly found this unacceptable. “It only grew yesterday.” “I know,” Li said. “I haven’t even used it for a full day.” “Do capacities have a warranty?” “I don’t know.” “You could ask your teacher.” Xi immediately glared at her. “This isn’t homework gone wrong.” The public noticeboard began degrading too. Yesterday’s corrected public-safe display label remained, but the author resolver had only half its functionality. The measurement interface was more direct: local presentation unstable measurement deferred Xi stood before it. “It can’t even measure me.” Xian said: “At least we can still see you.” Xi looked down at herself. “For now.” The resident fond of the end of the world returned. “Now even higher-order temporal directions are peeling away from reality—” Xi interrupted. “They aren’t peeling away.” “How do you know?” “Because I can still use it.” “Can you see it?” Xi paused. “No.” “Then how can you prove it?” Xi grew more annoyed. She tried ordering events with her new axis. She still obtained the original relation. The residential display layer simply did not present the axis. She immediately said: “It’s still there.” The resident said: “It could be a final echo.” Xi: “Could you stop writing an obituary for my capacity?” Heng finally approached from the management terminal. His expression was not anxious. It was busy. He had five service warnings. A resident followed him, asking whether the garbage revocation zone was still considered normally open that day. Heng answered that resident first: “Do not put garbage into slots with incomplete presentation yet.” “What would happen?” “The classification interface is unreliable right now.” “Would the garbage disappear?” “No.” “Then why can’t we put it in?” Heng looked at him. “Because it still needs sorting after restoration.” The resident left with an expression of “Fair point.” Li immediately stepped in. “What about me?” Heng opened her status. ⟦⊘ ◬ ⊚∷ ▣⟧ ⟦⊚ ∶ ◬ ⊚ ?⟧ ⟦◫ ∶ ⊘ ◬ ⊚ ▣⟧ “Ordinary observation cannot register all of you right now.” “So I have lost something?” Heng did not answer that formulation. He checked persistence. ⟦◫ ∶ ⌁ ⊚⟧ Then the dwelling association. ⟦◫ ∶ ⋈ ⊚ ▣⟧ “No.” Li relaxed a little. “What about the two on my left?” “The relation remains.” “Can you see them?” “Not stably right now.” “Then how are you so certain?” “Because observation is not the only relation.” Li thought for a moment. She understood that. Xian immediately became next in line. “Me.” Heng switched to her. Her presentation was still half complete, half apparently skipped by the image. ⟦⊘ ◬ ◒∷ ▣⟧ ⟦◒ ∶ ◬ ◒ ?⟧ ⟦◫ ∶ ⌁ ◒⟧ ⟦◫ ∶ ⋈ ◒ ▣⟧ After looking, Xian asked only: “So my appointment?” Heng said: “You’re still here.” “I know. I’m asking about the appointment.” “The appointment system is also degraded at present.” “Will it count me as absent?” “I don’t know.” Xian took a deep breath. “That is the problem.” Li thoroughly agreed. Xi squeezed in. “My new axis.” Heng took a look. ordinary observation： unavailable capacity association： stable measurement： deferred Xi asked: “So it’s still there?” “It’s still there.” “Just invisible right now?” “Yes.” “What about proof for the homework?” Heng looked at her. “Didn’t you hand it in yesterday?” Xi stopped. “Oh.” That problem was temporarily solved. In the shared areas, people’s descriptions grew increasingly grand. “The residential boundary is losing visibility.” “Part of time is no longer presented.” “Individuals are peeling from the surface of the world.” Someone even took the sentence: observation service unavailable And retold it as: The world has ceased to recognize observers. Heng joined none of these interpretations. He only watched the restore queue. A few minutes later, the system finally supplied a transition estimate. ⟦Ϟ ◌ ▣ ⧗⟧ Li asked: “How long?” “A short offset.” “In ordinary language.” “Wait.” “Then say ‘in a moment.’” Heng ignored her. The dwelling retained that feeling of “something is still there, but the image refuses to acknowledge it” for a while. Then the first manifestation returned. Not created anew. Its ordinary observation relation was merely reestablished. Then the second. Xian’s missing presentation returned piece by piece. Xi’s new temporal axis reappeared in the measurement layer too. Her first act was not to cheer. It was to rescan yesterday’s homework immediately. “The data are the same.” Heng said: “Because it never disappeared.” Xi nodded. Reasonable. The resident who kept saying darkness was swallowing the world stood nearby. He watched everything reappear. Was silent for a few seconds. “So...it wasn’t the end of the world?” Li said: “You can keep treating it as the end of the world.” “What do you mean?” “It just looks fixed on our side.” Xian’s appointment system recovered too. She was not marked absent. Her mood improved noticeably more than it had at the world not ending. The residential display finally returned the incident state to ordinary mode. Just before everyone dispersed, the terminal left two untranslated record lines. Major Gate 01 Do not scroll down looking for a decoder yet. The last two clauses are: ⟦⋈ ⊚ ▣⟧ ⟦◫ ∶ Ϟ ⋈ ▣ ⧗⟧ There are no new symbols here. If the relations from the first eleven episodes are beginning to feel intuitive, answer for yourself first: 1. Does the relation between ⊚ and the dwelling remain? 2. Is ◫ describing a permanent loss, or a later transition? 3. Are the things that suddenly became invisible more like existence failure or infrastructure failure? Stop here first. Do not rush to the official answer. ## Chapter 13 · Humans Translated “A Nap” as “Low-Order Death” After lunch, Xian did something entirely ordinary. She checked the afternoon schedule. There was still some time before her first appointment. One future branch reminded her: If you do not rest now, you will regret it later. Another future branch said: If you rest now, you may regret that later too. Xian closed both prompts together. “Then I’ll decide myself.” She dimmed the ordinary observation presentation beside the window. Not stopped it. Nor excluded herself from the dwelling. Simply withdrew several local manifestations that had previously been maintained in full. ⟦◬ ◒∷ ▣⟧ ⟦⊘ ◬ ◒∷ ▣⟧ She lay down. The residential fold outside continued as usual. Someone moved things in the shared passage. Someone downstairs complained about change. Somewhere, Xi was battling school rules again. Xian did not participate. She simply fell asleep. While asleep, she maintained a stable association with her dwelling. Her reconstructible persistence was uninterrupted too. ⟦⌁ ◒⟧ ⟦⋈ ◒ ▣⟧ She merely stopped expending effort to maintain every ordinary presentation. For residents of the Seventh Residential Fold, this was entirely unworthy of a record. For a human research group much later, it was not. —— When the H0 laboratory received this fragment, the data were already incomplete. No images. No sound. No “nap” label. No resident diary. No activity metadata. Only a relational corpus. A researcher projected seven glyph lines on the wall. ⟦⊘ ◬ ◒∷ ▣⟧ ⟦⌁ ◒⟧ ⟦⋈ ◒ ▣⟧ ⟦⧗ ◒ ▣⟧ ⟦Ϟ ◒∷ ▣ ⧗⟧ ⟦◬ ◒∷ ▣⟧ ⟦☼ □ ◒⟧ “Do not translate into natural language yet,” the moderator said. “List the relations first.” Another researcher began writing. “Reduced active observation.” “Persistence-like trace retained.” “Continued association between subject and fixed locus.” “A subsequent temporal offset.” “Manifestations return.” “Consumption at the end.” The moderator nodded. “Any entity deletion?” “No.” “Any continuity break?” “None apparent in this fragment, at least.” “Any reconstitution-like pattern?” “Yes.” Someone said: “This looks more like dormancy.” Someone else replied: “It could also be some kind of reversible, death-like phase.” Nobody laughed. Both accounts were reasonable. The data told them only this: The subject ceased to be ordinarily observable, then returned, with persistence uninterrupted in between. If you started from an entirely different biological and ontological tradition, It would be easy to call that: reversible death。 The group began assigning confidence scores. Low-order death state： 0.62 Reversible dormancy / inactive phase： 0.31 Observation-layer service degradation： 0.07 A more cautious researcher studied the second number. “I still think dormancy should score higher.” The moderator asked: “Reason?” “The stable locus association never breaks.” “A death-like state need not break it either.” “Persistence never breaks either.” “So it isn’t full death.” “The later consumption could simply mean waking up and eating.” The laboratory was silent for a second. Someone entered that sentence in the notes. Alternative mundane interpretation cannot be excluded. The moderator glanced at it. “Keep it.” Then they continued working. Nobody knew that the sentence was almost the answer. —— Some time passed. Xian woke. ⟦⧗ ◒ ▣⟧ ⟦Ϟ ◒∷ ▣ ⧗⟧ ⟦◬ ◒∷ ▣⟧ Her first act was not to check whether she had been resurrected. It was to check her appointment. “Still enough time.” Her second act was to be hungry. She went to get something. ⟦☼ □ ◒⟧ After eating, she checked her dwelling relation again. ⟦⋈ ◒ ▣⟧ It was still there. It had remained throughout. She had no idea that in a research database much later, she had just completed the full process of: low-order death → causal residue → reconstitution → restorative ingestion From beginning to end. If she knew, she would probably ask only one thing: “Does a nap count as taking leave, then?” —— H0’s provisional report was beautifully written in the end. Subject enters a low-order death state, retains causal residue, reconstitutes after temporal displacement, then performs restorative ingestion. Summary: The subject enters low-order death, preserves a causal residue, reconstitutes after temporal displacement, and performs restorative ingestion. A very cautious note followed: Reversible dormancy / inactive phase remains a viable alternative. Confidence： 0.31 On that whole page of research, The sentence closest to the truth Had the lowest score. And Xian had already finished eating and gone out to do what she needed to do that afternoon. ## Chapter 14 · Rift Classified a Visitor as Furniture When Xian visited Li’s home, the entrance first recognized her as a thing. That sounds unflattering. But that was how the dwelling’s visitor layer worked. First establish: A coherent entity has entered the dwelling frame. Then establish: Which stable address this entity is associated with. The presentation beside the door flashed. ⟦◬ ※ ◇ ▣⟧ ⟦⋈ ◇ ◒ ▣⟧ Xian took a look. “Why am I a diamond?” Li called from inside: “That isn’t your name.” “What is that?” “It’s establishing that you are a thing first.” Xian stopped in the doorway. “Your home’s system has a terrible way of welcoming people.” “It isn’t my home’s system.” Li pointed at Rift beneath the table. “It’s her visitor classifier.” Rift glanced up at Xian. Only once. Then the presentation changed again. ⟦≈ ※ ◒ ▱⟧ ⟦◬ ※ ◒ ▱⟧ And Rift stopped looking at her. Xian did not notice at first. She put what she had brought on the table. Rift did not react. She walked from the doorway to the window. When Rift passed in front of her, her route curved around her very naturally. Xian turned around. Rift kept walking. Xian shifted one step left. Rift went around to the left. She moved right. Rift went around to the right. Xian frowned. “Is she avoiding me?” Li was unpacking what Xian had brought. “She usually walks around people too.” Xian deliberately stood directly in Rift’s way. Rift stopped. Went around to the side. Xian blocked her again. Rift went around again. On the third attempt, Rift even changed course in advance. Not once during the process did she look up at Xian. ⟦⊘ ◬ ※ ◒⟧ Xian slowly turned her head. “Li.” “Mm?” “Can your pet not see me?” Li looked up. “She probably can.” “She doesn’t look at me at all.” “She may just not want to bother with you.” “I hope it’s that.” Xian approached Rift and crouched. “Rift.” Rift went around her knee. Xian stood. Walked another two steps. ⟦Ϟ ◒ ▣⟧ “I’m clearly moving.” Li watched for a few seconds and finally felt something was wrong. She called up Rift’s local classifier. The top line read: target: N.XIAN The next line: local role: static background Li fell silent. Xian leaned closer. “What is that?” Li said: “She’s marked you as background.” “Background?” “Static background.” Xian looked at herself. Raised a hand and waved it. “I’m moving all the time.” “I know.” “Then why is it still static?” Li examined the settings farther down. “The classification hasn’t updated.” Xian was silent for two more seconds. “Has she turned me into furniture?” Li immediately said: “No.” “Then why am I the same as furniture to her?” “Because furniture usually doesn’t need active tracking either.” That answer offered no comfort. Xian went to pick up the cup on the table. She could lift it. She sat down. She could sit. She spoke: “I can talk.” Li said: “I know.” “And still walk.” “I know that too.” “Then remove that marker quickly.” “I’m doing it.” Li cleared the classification relation. ⟦⊚ ∶ ⊘ ≈ ※ ◒ ▱⟧ Rift paused. Looked up. For the first time, she looked directly at Xian. ⟦◬ ※ ◒⟧ Xian moved left. Rift’s attention followed left. She moved right. Rift followed too. ⟦Ϟ ◒ ▣⟧ ⟦◬ ※ ◒⟧ Xian finally relaxed. “So I haven’t become furniture.” “No.” “She just treated me as furniture?” Li thought for a moment. “Strictly speaking, as background.” Xian looked at Rift. Rift was attending to her normally again. Even sniffed the bag she had brought. Xian said: “Is that any better?” “Yes.” “Where?” “Background is broader than furniture.” Xian felt Li was not helping. —— Much later, the H0 laboratory received only part of this scene. All they had was: ⟦≈ ※ ◒ ▱⟧ ⟦◬ ※ ◒ ▱⟧ ⟦⊘ ◬ ※ ◒⟧ And two earlier lines of entity-binding metadata: ⟦◬ ※ ◇ ▣⟧ ⟦⋈ ◇ ◒ ▣⟧ The researchers first established: “◇ should be a generic entity slot.” “It is bound to ◒, so the target identity is not in doubt.” “※ applies an ≈ relation to ◒.” “The resulting role is ▱.” “Afterward, ※ stops active tracking.” The moderator asked: 「movement evidence？」 “This recovered sample contains none.” 「persistence？」 “Not within the sample.” 「classification removal？」 “None either.” They began listing hypotheses. First: Ontological furnishing-state conversion — 0.58 Second: Local behavioral / attentional classification — 0.34 Third: Temporary perceptual suppression — 0.08 A researcher studied the second. “If ≈ is only a classifier, ▱ may not be a species or ontological state.” Another researcher said: “But tracking does stop afterward.” “Classification can alter tracking policy.” “Then why static?” “Because there is no movement fragment.” The laboratory was silent for a while. Finally, the moderator said: “Keep both. Assign higher confidence to conversion for now.” The report concluded: The dependent converts the visitor into an inert furnishing state and subsequently ceases active tracking of the transformed subject. Summary: A higher-order dependent converts the visitor into an inert furniture state, then ceases actively tracking the converted subject. At the same time, the real Xian was moving her cup to the other side of Li’s home. Rift’s gaze followed the cup. Then her. No furniture had become a person through classification. No person had become furniture through classification either. A pet’s classifier had simply mislabeled a visitor. ## Chapter 15 · For Reverse-Causal Deliveries, State Your Reason for Sending Li only wanted to return Xian’s insulated container. It should have been simple. Xian had lent her the container a few days earlier. Now it also contained a packet of crisps Xian had mentioned wanting, with a small jar of sauce beside it. Li put all three items in a parcel sleeve and went to the residential level’s courier area. Four people queued at the ordinary delivery counter. Nobody queued at the reverse-causal counter. Li checked the time. Then the message Xian had just sent. If you are returning the container, give it to me today. I need it tonight. Li went to the reverse-causal counter. Above it was written: Destination-first service available. A smaller line below read: origin-side records may be completed after destination settlement. Li put the parcel on the intake surface. “Send it to Xian.” The system identified the parcel. ⟦↶ □ ⧗⟧ Three fields appeared. Destination address: confirmed Parcel: confirmed Reason for sending: may be supplied afterward Li left the final field blank. She pressed submit. The parcel disappeared ordinarily. No light. No rotation. No visual effect resembling “causality reversing.” It simply was no longer on the table. Two seconds later, Xian messaged. Received. Li looked down. “That fast?” Xian sent another: Container, crisps, sauce. Is the sauce mine? Li replied: Yes. Xian: Then I’ll open it. Li: Haven’t you already opened it? Xian: I am checking whether any version of you has not agreed yet. Li thought that was reasonable. As she prepared to leave, the courier counter sounded a quiet prompt. A red box had appeared on the screen. ⟦⊘ ∴ □⟧ ⟦! ≡ □⟧ This case is not yet closed. Please supply the reason for sending. Li stopped. She looked at the screen. Then at Xian’s messages. Xian happened to send another photograph. The insulated container was on her table. Half the crisps were gone. Li looked up. “Haven’t the things arrived?” The counter replied: destination delivery：complete “Then why isn’t the case closed?” auditable closure：incomplete Li frowned. “Is there a difference?” The counter did not treat that as an appeal. It simply displayed the two states side by side. delivery：complete destination association：complete filed justification：missing closure：open Li pointed at the first line. “Isn’t that the most important thing?” For receipt, yes. She pointed at the last line. “What about this?” For accounting, yes. Li fell silent briefly. “So you can deliver things first, then ask me why I sent them?” Yes. “What if I don’t fill it in?” The parcel will not automatically be returned. “Will Xian suddenly not have received it?” No. “Will the parcel disappear?” No. “And you still want me to fill it in?” Yes. For the first time, Li felt this system had Heng’s style. She took out her terminal. Another message arrived from Xian. The crisps are good. Li looked at the “Reason for sending” field. She entered: Returning the insulated container Xian lent me. After a moment’s thought, she added: Putting in crisps and sauce while I’m at it. The system did not accept it immediately. A small prompt appeared below: justification scope includes all associated parcel contents. Li moved the cursor back. “Haven’t I written it all?” “While I’m at it” is not an auditable association description. Li stared at it. “You won’t even accept ‘while I’m at it’?” Everyday language is accepted. But the closure record must correspond to the parcel’s contents. Li deleted “while I’m at it.” Changed it to: Returning the insulated container Xian lent me and delivering the crisps and sauce previously agreed for Xian. The counter paused for half a second. ⟦⧗ ≡ □⟧ ⟦Ϟ ≡ □ ⧗⟧ ⟦⋈ ≡ □⟧ ⟦∴ □ ≡⟧ The red box disappeared. Case closed. Li looked at those words. “So for the last few minutes, the things were already at Xian’s place, but the reason wasn’t here yet.” Yes. “Then which caused which first?” The counter paused longer this time. Then displayed: This service does not require that question to be answered for the operation to be completed. Li laughed a little. “Good at dodging.” The system did not respond. She prepared to leave. Xian messaged again: The sauce is too spicy. Li replied: Only telling me now? Xian: I only found out after receiving it too. Li glanced at the already closed sending record. She suddenly felt the most reverse-causal part of this universe might not be the courier. —— Much later, the H0 laboratory received far less data. They had no courier counter. No “insulated container.” No messages from Xian. No “The sauce is too spicy.” Only: ⟦↶ □ ⧗⟧ ⟦Ϟ □ ◒⟧ ⟦⊘ ∴ □⟧ ⟦! ≡ □⟧ ⟦⧗ ≡ □⟧ ⟦∴ □ ≡⟧ The researchers first listed the known elements. “□ is still a local parcel.” “◒ is the same stable address.” “Ϟ is a transition.” “∴ is a closure relation, but its frame here is uncertain.” “↶ clearly involves nonstandard ordering.” The moderator nodded. “What about ≡?” “It looks like some kind of closure-supporting record.” Another researcher wrote the sequence on the wall: object transition closure absent record required record appears later closure established Someone said: “If the result exists first, and the subsequent record is necessary for closure, the result itself may form a future obligation.” Someone immediately asked: “Is the obligation imposed by the object, or by an external protocol?” Nobody answered. The first model was written down: Retrocausal command / prophecy fulfillment — 0.55 Second: Administrative reverse-causal logistics protocol — 0.38 Third: Timestamp / observation-order artifact — 0.07 A researcher tapped the second line. “If ! is an institutional requirement, this could be quite mundane.” “How mundane?” “Deliver the things first, supply the paperwork later.” The laboratory was silent for two seconds. Someone said: “What about ↶?” “A service relation allowing the destination leg to finish first.” The moderator looked at both models. “The fragment is insufficient for now.” So the formal report still stated: The artifact manifests prior to its causal justification and subsequently necessitates the future production of a validating causal record that retroactively closes its prior appearance. Its natural-language summary was: The object manifests before its causal justification and subsequently compels a validating causal record to arise in the future, retroactively closing its earlier appearance. By the time the report was submitted, the real Xian had finished the crisps. The insulated container was already washed. No object had compelled the future to generate a cause. No prophecy had been fulfilled. No loop of fate had closed. A courier delivery had simply arrived some time ago. And a form had been completed a few minutes after the parcel. ## Chapter 16 · Tomorrow’s Me Turned Up at Lost and Found Xian only wanted to go home. Today she had already dealt with change split between two tomorrows and received crisps from Li before their reason for sending arrived. She felt today had been enough. But the public recovery node at the residential level’s corner lit up. Recoverable targets associated with your stable address: 1 Xian stopped. A glance. She walked two more steps. Stopped. Went back. “Don’t.” She had already seen an unborn branch try to order breakfast for her. And a convenience store divide her change into two possible tomorrows. Those had at least one advantage: The future stayed in the future. Now the recovery node told her that something associated with her tomorrow had entered today’s service queue early. Xian looked up at the residential level’s timetable. She had a fixed commitment tomorrow morning. Another at noon. And something borrowed to return at night. She told the recovery node: “I did not ask tomorrow to report early.” The system replied: no arrival event recorded. “Then that’s worse. It isn’t even reporting.” The working node shone patiently. Xian sighed. “Don’t.” The system did not answer her wishes. The display unfolded. At the top was a familiar address. ◒ Below it: ⋔ ∷ Together: ◒⋔∷ Xian stared at the sequence. In the presentation window beside it, there really was a local state resembling her. Not a complete second person. More like an address presentation that should have resolved forward along a future branch but had been displayed early in the wrong frame. Its outline matched hers. Its posture did not quite. Xian raised her hand. The state did not follow her movement. It simply remained in a presentation “waiting to be connected back to its route.” ⟦◬ ◒ ◒⋔∷⟧ ⟦⋈ ◒⋔∷ ◒⟧ ⟦⋈ ◒⋔∷ ⋔⟧ ⟦⌂ ◒⋔∷⟧ Xian finished looking. “Why am I at lost and found?” A staff member handling another recovery case nearby looked up. “You aren’t.” Xian pointed at the screen. “Isn’t that me?” The staff member glanced at it. “It has a stable association with you.” “That sentence usually doesn’t answer ‘Is it me?’” “That is an address state of your future branch.” “So it’s still me.” The staff member considered. “You could put it that way.” Xian folded her arms. “I’m not lost property.” “You aren’t.” “Then why can I be claimed?” The staff member showed her the target schema. Three lines appeared. recovery target：future-linked address state recovering participant：N.XIAN owner：not applicable Xian stared at the third. “You even have an owner field.” “Some recovery cases need it.” “Mine doesn’t?” “It doesn’t.” “Then why does this look like lost and found?” “Because it is a recovery service.” “Could you choose a name that doesn’t make people feel they’ve been picked up as stray objects?” The staff member glanced at the public sign above. “You may submit a proposal.” Xian felt that this usually meant: It would not change. She examined the future-linked state again. “How did it get here?” The staff member called up the route trace. An address relation that should have resolved later along an unresolved future path had been bound early to the recovery frame during an ordinary transition on the residential level. Not a rift. Not a hazard. Nobody had kidnapped the future. Just incorrect routing. Xian was silent for a few seconds. “So tomorrow’s me got lost.” “Not the whole of tomorrow.” “Part of tomorrow got lost.” “Closer.” Xian sighed. “I have work tomorrow.” The staff member did not understand its direct connection to the recovery case. Xian added: “I simply hope that my tomorrow will at least stay in tomorrow first.” That was reasonable. The system merely offered no such guarantee. —— She opened the recovery action. The screen displayed: recover target? Xian pressed confirm. The system asked again: recovering participant? Already filled automatically: N.XIAN She looked at her name. “So I have to claim myself.” The staff member said: “You are the recovering participant.” “Isn’t that the same sentence?” “No.” “What’s the difference?” “If you were the owner, there would be an ownership relation.” “There isn’t one now?” “No.” “What if I were property?” “The target type would differ too.” Xian looked. “So right now it is?” 「address state。」 Xian fell silent briefly. “For the first time in my life, I feel ‘I am not property’ needs a system to prove it.” The staff member did not laugh. Perhaps because they had already heard stranger things today. Xian pressed recover. ⟦◒ ∶ ⌂ ◒ ◒⋔∷⟧ In the presentation window, the future-linked state flickered slightly. It was not absorbed into Xian’s body. No merging. No “future returning to the present.” It merely transferred from the incorrect recovery route back to its normal association. ⟦Ϟ ◒⋔∷ ◒⟧ ⟦⊘ ⌂ ◒⋔∷⟧ The list emptied. The nearby schedule preview refreshed automatically. The future-linked entry previously marked: route unresolved / recovery pending Now read only: route association：normal Xian stared at that line. “So tomorrow has gone back to tomorrow now?” The staff member said: “That state has returned to its expected relation.” “I’m asking about tomorrow.” “Your tomorrow never left.” “But part of it was here just now.” “That is why recovery was needed.” Xian felt this answer formed a very solid and very unsatisfying circle. She looked at the emptied position. “So I collected myself.” The staff member said: “You connected an address state associated with you back to its normal route.” “You really insist on this.” “Because those are different things.” Xian prepared to leave. Walked three steps. Turned back. “Will tomorrow’s me remember that I came to collect it today?” The staff member checked the relation status. ⟦⌁ ◒⟧ ⟦⋈ ⋔ ◒⟧ “Continuity normal.” Xian relaxed. “All right.” She turned. Stopped again. “What if tomorrow’s me comes tomorrow and says she never agreed to be collected by today’s me?” The staff member was silent. Really silent this time. Xian waited two seconds. The staff member said: “That would be another case.” Xian nodded. “I knew it.” —— Much later, the H0 laboratory obtained far less than Xian had seen. They did not have: owner：not applicable Nor: recovery target：address state No routing trace. Nor the staff member’s statement: Recovering participant does not equal owner. All they had was: ⟦◬ ◒ ◒⋔∷⟧ ⟦⌂ ◒⋔∷⟧ ⟦⋈ ◒⋔∷ ◒⟧ And subsequently: ⟦◒ ∶ ⌂ ◒ ◒⋔∷⟧ ⟦⊘ ⌂ ◒⋔∷⟧ The researchers first listed known relations. “◒ is the same stable address.” “⋔ is an unresolved future branch.” “∷ is manifestation structure.” “So ◒⋔∷ should be a future-linked manifestation.” The moderator nodded. “What about ⌂?” “It looks like claim or recover.” Another researcher said: “The target is first marked claimable. Later, current ◒ performs recovery on the same target.” “Very like lost property.” Someone immediately added: “But the corpus has no ownership primitive.” The laboratory was briefly silent. The first model was written down: Future self as recoverable property — 0.53 Second: Generic address-state recovery service — 0.41 Third: Identity duplicate detention / quarantine — 0.06 A researcher pointed at the second model. “If ⌂ indicates only a recovery relation, current ◒ may simply be a legally eligible recovering participant.” “Not the owner?” “Not necessarily.” “Then why can the target be claimed?” “Because it is addressable and took the wrong route.” The moderator studied the fragment. “We have no route metadata.” “Nor a property token.” “So retain both models.” The formal report finally still stated: A future instance of the subject is detained as lost property and later reclaimed by its present owner-state. Summary: A future instance of the subject is held as lost property, then retrieved by its present owner-state. By the time the report was sent, the real Xian was home. She checked tomorrow’s schedule once more. Breakfast normal. Transport normal. Work normal. No field said: Tomorrow’s you: held by today’s you. Only the recovery node’s case history contained one more ordinary record: target route restored. Xian was not lost property. Tomorrow was not her property either. An address state that should have proceeded toward tomorrow had simply taken the wrong route today. ## Chapter 17 · The Residents’ Assembly Voted to Delete a Hallway The residents’ assembly lasted forty minutes. Twenty-five of them were spent discussing whether a hallway counted as “frequently used.” The hallway was on the Seventh Residential Fold’s east side. It ran from the middle residential level around a maintenance zone, then connected to the public transfer lobby. In theory, it shortened the walk a little. In practice, over the last thirty cycles most residents had taken another route: brighter, straighter, and less prone to notices every few days saying “Do not keep left; the left side is temporarily not the same left side.” Heng projected usage data into the center of the assembly. Eastern shared passage Ordinary transit usage: low Maintenance intervention: relatively high alternate public route：available Li raised her hand from the back row. “So are we repairing it today?” “No.” “Then posting another notice?” “Not that either.” “What are we doing?” Heng displayed the next page. proposal：decommission from ordinary civic reachability Li looked for two seconds. “You can use ordinary language.” Xian, seated on the other side, said: “Decommissioning.” Heng nodded. “Yes.” Li immediately understood. “Then why didn’t you write ‘decommissioning’ in the first place?” “I didn’t write the formal motion.” The resident responsible for proposing it raised a hand near the front. “It’s me.” Li looked at him. “Do you happen to like writing reports?” “I’m responsible for maintenance.” “That explains it.” —— Not everyone agreed. A resident living on the east side said: “I use that hallway.” Heng checked the data. “Eleven records over the last thirty cycles.” “See?” “Seven were you checking whether it had been repaired.” The resident fell silent. Xian looked down and laughed a little. Another resident said: “I support decommissioning. Last time I used it, the exit was half a maintenance window later than the entrance.” Heng said: “That incident has been repaired.” “But I don’t want to check a second time.” Someone else asked: “Will it be dismantled after decommissioning?” “No demolition proposal at present.” “What will it be left for?” 「maintenance access。」 “Ordinary residents can’t use it?” “No.” “Can they see it?” “Yes.” “Then it’s just a hallway nobody can walk through?” Heng paused. “Yes.” The meeting room was silent for two seconds. Li said: “See? Everyone can use ordinary language.” —— The vote passed in the end. The central display showed: ⟦◬ ◫ ⌇⟧ ⟦⋈ ⌇ ▣⟧ ⟦! ✂ ⌇⟧ Then: ⟦✂ ⌇⟧ ⟦⊘ ⋈ ⌇ ▣⟧ But the announcement on the resident interface had only four characters: Delete hallway Xian looked up when she saw it. “Wait.” Heng was about to switch to the next agenda item. “What’s wrong?” “Didn’t you say decommissioning?” “Yes.” Xian pointed at the announcement. “This says delete.” Heng took a look. “A short title.” “So short its meaning has changed.” “It hasn’t changed.” “‘Decommission hallway’ is four characters too.” Heng fell silent. People in the meeting room began nodding. The proposer said: “Legacy interface vocabulary.” Li said: “So it isn’t a matter of fitting.” “No.” Heng opened the announcement’s notes. They read: remove path from ordinary civic reachability graph Li finished reading. “Now that really wouldn’t fit.” —— After the meeting, Xian deliberately went around to the east side. Not because she needed that route. Simply because she wanted to check: What a deleted hallway looked like. She turned the corner. The hallway remained. The lights were on. The walls were still walls. The floor had not become a black hole. A maintenance unit was even moving slowly beside the distant wall. ⟦◬ ◒ ⌇⟧ Xian stood at the entrance. “Isn’t it still here?” Heng happened to approach from behind and said: “It is.” “Can I walk through?” “No.” “Why?” “It is no longer an ordinary public route.” ⟦◒ ∶ Ϟ ⌇ ?⟧ ⟦◫ ∶ ⊘ Ϟ ⌇⟧ Xian extended one foot forward. No wall blocked the entrance. Nor a door. But the public transition layer did not receive her next step. Her foot could still rest within the entrance area. When she tried farther forward, the routing prompt showed only: no ordinary resident transition relation Xian withdrew her foot. “Strange.” “Where?” “I can see a route, but it isn’t a route.” “It is a path-like structure.” “That’s stranger.” “For the maintenance frame, it is still a path.” “What about for me?” “Not a public route.” Xian turned toward him. “You really like dividing the same thing into lots of relations.” Heng said: “If we didn’t, you would have asked why the hallway disappeared.” “I’m asking now too.” “But it hasn’t disappeared.” “That’s why I’m asking.” Heng did not answer. Because the conversation had begun forming a familiar circle. —— Xian checked the announcement again. “So what does ‘Delete hallway’ actually delete?” ⟦◒ ∶ ✂ ⌇ ?⟧ Heng pointed at the routing status. ⟦◫ ∶ ⊘ ⋈ ⌇ ▣⟧ “Its ordinary association with the public reachability graph.” “Not the hallway.” “Yes.” “Then your title is wrong.” “It is resident-facing shorthand.” “Didn’t you just say the meaning hadn’t changed?” Heng looked at her. “Now I acknowledge compression.” Xian nodded. “Good.” “But the motion itself is correct.” “I know.” “So?” “So I’m only checking whether what was deleted today was the hallway or your word count.” Heng did not answer that. —— The assembly’s final agenda item had actually included another notice. The shared cycle slot previously lent out was expected to return later. It would require a local compatibility check before rejoining the active schedule. Xian paused for half a second at that line. “Is it Wednesday?” Heng said: “We’ll see when it returns.” Xian immediately had a bad feeling. “That sounds as though there will still be something to deal with after it returns.” “Possibly.” “Can I vote against it?” “Not on this agenda.” Xian felt that residents’ self-governance offered very selective freedoms. —— Much later, the H0 laboratory received another version. They did not have the assembly’s twenty-five-minute argument about “frequently used.” Nor the east-side resident’s eleven usage records. Nor “Seven were only checking whether it was repaired.” Nor Xian standing before a clearly visible hallway no longer usable as a public route and asking: “What exactly was deleted?” All they had was: ⟦! ✂ ⌇⟧ ⟦✂ ⌇⟧ ⟦⊘ ⋈ ⌇ ▣⟧ ⟦⊘ Ϟ ⌇⟧ The researchers listed what was known. “! is civic authorization.” “⌇ is a shared passage.” “✂ acts on a path.” “Afterward, its association with dwelling reachability is removed.” “Resident transition is excluded too.” The moderator asked: “So what is the operation?” Someone wrote on the board: graph edge removal Someone else added: topological excision A third said: “What if it really is only municipal decommissioning?” The laboratory paused. The first researcher said: “Formally, that is edge removal too.” “Yes.” “So topological excision cannot be called wrong.” “I didn’t say wrong. I asked whether it was too grand.” Three models were retained in the end: Civic topological excision rite — 0.66 Municipal route decommissioning protocol — 0.29 Physical corridor annihilation — 0.05 The third had almost no support. Because they also had a post-operation observation: ⟦◬ ◒ ⌇⟧ The hallway was plainly still visible. Only one dispute remained: What to call a civic operation that removes a path from the public routing graph. The formal report concluded: The civic body authorizes a topological excision of an inhabited transit segment, severing it from the shared reachability manifold. Summary: The civic community authorizes topological excision of an inhabited spatial segment, severing it from the shared reachability manifold. By the time the report was written, residents of the Seventh Residential Fold had grown used to the other route. Nobody held a ritual. Nobody cut open spacetime. Nobody stood before the hallway mourning the lost manifold. There was merely a very ordinary notice beside the entrance: This route is decommissioned. Please use the western passage. And, deep inside the interface, the still very extraordinary old title: Delete hallway ## Chapter 18 · Wednesday Is Back, but It Is the Wrong Version Xian was the first to see Wednesday return. She had only been passing the public schedule board. Not specifically waiting. At least, that was what she believed. The position at the top that had remained empty suddenly lit up. ⟦Ϟ ⌖≋ ▣⟧ A line appeared beneath: displaced public cycle slot：returned Xian stopped. She stepped closer. She had looked at that position too many times. After EP006, Wednesday had been borrowed from the Seventh Residential Fold. Life continued, but many things had become irritating. Some services extended Tuesday. Some shops changed “Wednesday only” to “We’ll discuss it when Wednesday returns.” Even garbage-processing intervals had briefly been reordered in its absence. What Xian hated most was: Her schedule always looked as though a slot was missing. Now that slot had returned. She stared for two seconds. “It’s back.” A resident updating residential announcements nearby looked up too. “Really?” “Mm.” Xian smiled more openly than usual. She immediately opened her schedule to reconnect regular commitments that had been forced into other cycle slots. The interface displayed: version mismatch Xian’s smile stopped. She looked at those four characters. Then at Wednesday again. “No.” The system ignored her. Xian selected the slot. ⟦◬ ◒ ⌖≋⟧ ⟦⋈ ⌖≋ ⌖⟧ identity check： calendrical identity：recognized She relaxed a little. The next line: active local compatibility：failed Xian stopped relaxing. —— When Heng arrived, she had been studying the schedule board for almost five minutes. “What’s wrong?” Xian pointed at the slot. “Wednesday is back.” “Mm.” “It says the version is wrong.” “Mm.” Xian turned. “How can you answer something like this with ‘Mm’ twice in a row?” Heng glanced at the metadata. “Because both things are true.” “Which two?” “Wednesday is back.” “Yes.” “The version is wrong.” “I know.” “Then what are you asking?” Xian closed her eyes. “I’m asking why Wednesday has versions.” Heng looked at her. “Because it is a versioned temporal segment.” Xian opened her eyes. “In ordinary language.” “When it was lent out, the local schedule was still in its old state.” “So?” “It returned carrying the version state accumulated while it was away.” “So it really is Wednesday?” “Yes.” “Not a different temporal segment?” “No.” “Not a parallel-universe Wednesday?” “There is no evidence.” “Not the Wednesday of one of my future branches?” “No evidence of that either.” Xian nodded. “Good.” A one-second pause. “Then why can’t we use it?” Heng opened the next status layer. ⟦⊘ ⋈ ⌖≋ ▣⟧ identity association：valid active schedule association：withheld reason：version reconciliation pending Xian stared. “So it is Wednesday.” “Yes.” “We just can’t use it as Wednesday right now.” “Temporarily.” “Do you feel there’s something wrong with that sentence?” “No.” “I do.” —— Xian was not the only one with a problem. Very ordinary complaints soon spread across the residential level. The breakfast shop withdrew the Wednesday second-item discount it had been preparing to restore. The public laundry displayed: Wednesday schedule detected service activation pending A resident at a machine asked: “Does today count as Wednesday or not?” The system answered: calendrical identity recognized service compatibility pending The resident turned to Heng: “Does that count as ordinary language?” Heng said: “Not really.” Xian immediately said beside them: “You finally admit it.” Another resident cared more about garbage classification. “I was supposed to discard a batch on Wednesday before it loses stable association by Thursday.” Heng said: “Use the reconciliation fallback window today.” “So Wednesday is back, but we still can’t discard things according to Wednesday?” “Yes.” “Then why did it come back?” Heng did not answer. Because that was plainly not a technical question. —— Reconciliation was scheduled that day. No ritual. No temporal storm. No half of a city disappearing. Only a progress bar resembling a system update appeared beside the schedule board. comparing returned version with local active schedule rebuilding closure-support record service mappings pending Xian stood watching. “How long will it take?” “Uncertain.” “Didn’t you just say it was normal?” “Normal doesn’t mean fast.” “I hate that sentence.” “Many people do.” Heng checked the new metadata. “A closure-support record is needed.” ⟦≡ ⌖≋⟧ Xian frowned at ≡. “This again.” “You recognize it?” “Wasn’t Li just forced to supply paperwork for that reverse-causal delivery?” “Same root, different frame.” “So Wednesday needs paperwork when it returns too.” “Not paperwork itself. A record sufficient to support schedule closure.” Xian looked at him. “You really like making everything auditable in the end.” Heng did not deny it. —— Halfway through the update, the schedule board issued a prompt: conflict：one resident booking references current local Wednesday mapping Xian looked down. That was hers. She had moved a regular meeting to “the first usable Wednesday slot after Wednesday returns.” Now the system did not know whether: returned Wednesday And: local expected Wednesday Could yet be treated as the same active version. Xian said: “It’s me.” Heng said: “I saw it.” “So I’m what’s holding it up?” “No. You are simply the first person to encounter the compatibility check in practice.” “Is that any better?” “Yes.” “Where?” “You did not cause it.” Xian thought for a moment. “All right. That is better.” —— After a while, the system began transitioning. ⟦Ϟ ⌖≋ ▣⟧ The returned version’s service mappings reconnected one by one. The breakfast shop’s Wednesday discount lit up. The laundry’s Wednesday schedule changed from pending to active. The garbage-classification interval reappeared on the public board. Finally: ⟦∴ ⌖≋ ▣⟧ ⟦⋈ ⌖ ▣⟧ The board displayed: schedule closure：complete active calendrical association：restored Xian stared at the two lines. “So Wednesday really is back?” Heng said: “It’s back.” “And usable now?” “Yes.” “The version?” “Reconciled.” Xian thought for a moment. “So a lent-out Wednesday needs updating when it comes back.” Heng paused for a second. “You could put it that way.” Xian nodded. “You could have said that earlier.” —— She dragged her regular commitments back to Wednesday. This time, no error. The breakfast shop resumed Wednesday offers. The garbage-classification interval returned to its original position. The schedule missing a slot was finally complete again. Xian watched for a while. She did know: Wednesday was only a public calendrical slot. Not a friend with intentions. Nor something lost for years. But she still said quietly: “At last.” Heng stood beside her. “You care a lot about Wednesday.” “I care about my schedule not constantly moving.” “That makes more sense.” “I have always made sense.” Heng did not comment. —— Much later, the laboratory also encountered a “wrong-version Wednesday.” This time, however, they did not immediately write: alternate timeline intrusion Nor begin with: parallel calendrical entity replacement A researcher projected the fragment on the wall. ⟦Ϟ ⌖≋ ▣⟧ ⟦◬ ◒ ⌖≋⟧ ⟦⋈ ⌖≋ ⌖⟧ ⟦⊘ ⋈ ⌖≋ ▣⟧ Someone said: “The association between returned segment and known calendrical identity holds.” Someone else said: “But its active local schedule association is excluded.” The moderator asked: “How would we have described this before?” Someone laughed a little. “Invasion by a parallel temporal segment.” “And now?” The researcher retrieved corrections from the previous episodes. EP013： low-order death The more they examined it, the more it resembled: reversible dormancy。 EP014： furnishing transformation Later, it was closer to: classification。 EP015： retrocausal command artifact Later, it was closer to: reverse-causal logistics protocol。 EP016： recoverable property Later, it was closer to: generic address-state recovery。 EP017： civic topological excision rite Later, everyone acknowledged: municipal route decommissioning It sounded more like ordinary language. The laboratory was quiet for a while. The moderator said: “Let’s not embellish it this time.” So the first model became: Versioned temporal-segment return requiring reconciliation — 0.78 Second: Alternate timeline intrusion — 0.13 Third: Future-branch replacement — 0.09 Someone asked: “Have we become more conservative?” The moderator said: “We have begun remembering where we were wrong before.” —— They subsequently issued the formal: Translation Model Revision Notice — R1 Its first provision read: Longitudinal relational consistency is given greater evidential weight than isolated dramatic interpretations. Someone translated it into more ordinary language: If the same relation keeps operating consistently over many episodes, don’t assume one episode suddenly becomes the end of the universe just because it looks frightening. The moderator said: “Don’t put that in the formal version.” “Why?” “It sounds too much like ordinary language.” The laboratory laughed a little. But the methodology truly changed. They revised the previous five episodes: Napping no longer primarily described as low-order death. Furniture no longer primarily described as ontological conversion. Reverse-causal delivery no longer primarily described as a fate-object. Lost and found no longer primarily described as ownership recovery. Deleting a hallway no longer primarily described as a ritual of topological excision. Not because all the old models were absurd. But because: The corpus had grown. Many things that first looked like cosmic horror seemed, within a longer relational history, merely this world’s everyday institutions. —— The formal report concluded: A previously displaced calendrical segment returns in a version state inconsistent with the current local schedule and is withheld from active scheduling pending reconciliation. Summary: A previously detached calendrical segment returns in a version state inconsistent with the current local schedule and is temporarily excluded from the active schedule until reconciliation completes. No “temporal rift” this time. No “invasion by an alternative universe.” No “return of a calendrical personality.” Only: Wednesday had returned. And: It needed updating before use. Act III ends here. And for the first time, the research group began seriously suspecting: Sometimes the outside civilization was not too frightening. The translators were simply too accustomed to making unfamiliar things sound frightening. ## Chapter 19 · The Extra Third Observation Slot On the first morning after Wednesday returned to normal, Heng performed routine checks. Not because something had happened. Quite the opposite. The last few days had been eventful, so he wanted to confirm that all ordinary relations on the residential level were normal again. Wednesday: active。 Eastern hallway: decommissioned as planned。 public observation stabilization： normal。 shared schedule： closed。 Heng went through the entries one by one. Everything so far was boring. That was good. The best state for management work was: Boring. He opened dwelling validation. The first observation: ⟦◬ ◫ ▣⟧ Normal. observer： Heng. target： dwelling frame。 Done. Heng selected the next entry. An extra position appeared. ⟦◬³ ◫ ▣ ?⟧ Heng stopped. Not because it had a red light. It did not. No warning. No hazard marker. Not even an error code. It simply had one more position than usual. The third position was: ? Heng stared for two seconds. Pressed rerun. ⟦◬ ◫ ▣⟧ ⟦◬³ ◫ ▣ ?⟧ ⟦⧈ ◬³ ▣ ?⟧ It was still there. He ran it again. It was still there. —— Heng first did the most ordinary things. Closed the validation panel. Reopened it. It was still there. Changed the measurement window. It was still there. Cleared the previous cache entry. It was still there. He checked the system status. observation stabilization：normal resolver service：normal dwelling frame：stable unknown structural position：present Heng frowned. The last line had not existed before. He did not immediately call anyone. First, he reran the whole process a second time. Same result. Ordinary observation was normal. Three-slot observation was normal too. Only the third binding was: unresolved。 At such moments, the difficult part was not a system reporting an error. Instead: The system seemed quite certain it was not reporting one. —— Xian still held her newly bought breakfast when she was summoned. “What’s wrong?” Heng pointed at the validation panel. “Have a look.” Xian took a look. “At what?” “Perform an observation yourself.” “Why?” “Confirm.” “Confirm what?” “I’ll tell you afterward.” Xian disliked that answer. But she stood before the validation node. First entry: ⟦◬ ◒ ▣⟧ Normal. Second entry: ⟦◬³ ◒ ▣ ?⟧ Xian stopped. “One extra position.” “Mm.” “What is this?” “I don’t know.” “You didn’t know before you called me?” “Yes.” “Then you could at least have said ‘I don’t know’ first.” “I have now.” Xian looked at the third position. It had no content. But it was not blank either. The interface explicitly retained a slot. A measurement appeared beside it: ⟦⧈ ◬³ ▣ ?⟧ structural position：confirmed binding：unresolved Xian slowly put her breakfast aside. “So another person is looking?” Heng said: “Not necessarily.” “Then who is in the third slot?” “I don’t know.” “What do you know?” “It wasn’t there before.” Xian looked at him. “That is a little frightening.” “It’s only a description.” “The description itself is a little frightening.” “Yes, you can.” “So you find it frightening too?” “I didn’t say that.” —— Heng placed the two results side by side. Left: observer = N.HENG Right: observer = N.XIAN Both had a third slot. Both third slots were unresolved. Xian pointed at both. “So it isn’t your problem.” “At least it isn’t associated only with me.” “Nor my problem.” “At least it isn’t associated only with you.” “Could you say the complete sentence at once?” Heng thought for a moment. 「third-slot pattern survives observer change。」 Xian fell silent. “Better if you didn’t.” —— They changed to another ordinary observation target. Its ordinary relation was normal. But the third position appeared again in the dwelling validation frame. Heng entered it in the log. Xian asked: “Could it be left over from Wednesday’s update?” “There is no evidence.” “The eastern hallway?” “There is no evidence.” “Li’s reverse-causal delivery?” “There is no evidence.” “My tomorrow that got lost a few days ago?” “No evidence of that either.” Xian asked about all the recent events in one breath. Each time, Heng answered: “There is no evidence.” Finally, Xian said: “You’ve been saying that more lately.” “There should be more of it after R1.” “The human research group updated its method, so you did too?” “The method was reasonable to begin with.” Xian thought for a moment. “All right, then.” —— Heng then tried local exclusion. Not deleting the relation. Only temporarily excluding the extra structure from the current validation frame, to check whether it belonged to an additional layer. ⟦◫ ∶ ⊘ ◬³ ▣ ?⟧ The system accepted the operation. Next observation: ⟦◬³ ◫ ▣ ?⟧ The third slot remained. Xian looked at the screen. “So it can’t be driven away.” “We can’t put it that way yet.” “Didn’t you just exclude it?” “What was excluded was the local relation instance.” “And?” “A new instance appeared.” Xian liked that answer even less. “Is that any better?” “More precise.” “I’m asking whether it’s better.” “No.” At least Heng answered quickly this time. —— The validation record began having an irritating small problem. The form used to be: observer target result Now it had an additional field: witness / validation binding Status: unresolved Every other part of the form could finish. Only that field stayed open. Xian said: “So our biggest problem now is an extra form field we cannot complete?” “Operationally, for now, yes.” “Not something watching us?” “I don’t know.” “Not someone outside the world?” “I don’t know.” “Not our future selves?” “I don’t know.” “Not the rea...” Heng looked up. “What were you going to say?” Xian paused. “Nothing.” She did not know why a strange word had almost slipped out. Heng did not pursue it. —— Li happened to pass and saw them at the panel. “Broken?” Xian said: “One extra position.” Li took a look. “Which position?” Xian showed her. Li stared for three seconds. “Whose?” Heng said: “I don’t know.” Li looked for another three seconds. “Dangerous?” Heng said: “We don’t know at present.” Li nodded. “Then I’ll be going.” Xian turned. “Just like that?” “What else would it be?” “Aren’t you curious?” “Curious.” “Then why are you leaving?” Li said: “Curiosity doesn’t stop me collecting lunch.” And she really left. Xian watched her go. “Sometimes she makes a lot of sense.” Heng said: “Most people make sense when they’re hungry.” —— Heng finally set the event state to: STRUCTURE CONFIRMED / BINDING UNRESOLVED No hazard marker. No evacuation. No dwelling shutdown. Nor an announcement that “an unknown being is gazing at residents.” Xian looked at the line. “That’s it?” “For now.” “What if it’s still there tomorrow?” “Keep measuring.” “The day after?” “Keep measuring.” “A week?” “Establish a longitudinal record.” Xian sighed. “Can’t Act IV begin by giving me something more like an answer?” Heng looked at her. “Not knowing is an answer too.” Xian frowned. “That sounds like something a researcher would say.” “It is.” —— Much later, the H1 group received this record. Before Act III, they might already have written: trans-dimensional witness intrusion Or: nonlocal observer entity Or something worse. But R1 existed. So the researchers separated two matters first. First: Does the third slot really exist? Second: Who or what is the third slot? Confidence in the first was high. Because: • repeated； • cross-observer； • measurable； • structurally stable。 Confidence in the second was low. Because: • no identity binding； • no personhood evidence； • no hazard marker； • no causal relation； • no provenance。 The laboratory finally wrote: Structural confidence — 0.86 / high Binding-identity confidence — 0.18 / low Someone asked: “Should we call it an external witness?” The moderator said: “As a model, not an identity.” 「higher-dimensional observer？」 “Insufficient evidence.” 「hidden person？」 “Insufficient evidence.” 「system bug？」 “Not yet excluded, but repeated cross-observer results mean it is not the leading explanation.” The final model ranking was: Protocol / grammar extension — 0.36 External validation anchor — 0.28 Observer-frame artifact — 0.20 Genuinely external witness — 0.12 Instrumentation fault — 0.04 Nobody put “god” in the table. Not because they were certain there was none. But because: Slot existence had evidence. A god did not. —— In the Seventh Residential Fold, the third slot was still there that evening. Xian looked once more before going home. “Still a question mark.” Heng said: “Mm.” “Do you really not guess at all now?” “I have hypotheses.” “Then why don’t you say them?” “Because you are asking for an answer.” Xian stood for a while. Finally nodded. “All right.” She turned toward the elevator. After two steps, she turned back. “What if it becomes four slots tomorrow?” For the first time, Heng paused longer than usual. “Then we’ll open another form tomorrow.” Xian laughed. “Sometimes this world really deserves a beating.” The third slot did not answer. Because, at least for now, nobody knew whether it could answer. ## Chapter 20 · For the First Time, the Administrator Admits “This Is a Bit Serious” Xian noticed the problem first. She only wanted some water. Wednesday was back. Her schedule had recovered. The breakfast shop’s discount was normal. So was the laundry. And the garbage-classification interval. Xian felt life was finally something she could follow on a timetable again. Then she put her cup in the sink. Pressed for water. Water emerged. Just not from the outlet. The first stream fell from a position about half a body-width to the sink’s right. Very clean. Very stable. And very accurately missing the cup. Xian watched for two seconds. The water stopped. She moved the cup right. Pressed again. This time, water came from the normal outlet. Filled the cup. Xian stared at the faucet. “...All right.” She returned the cup to its original position. Pressed a third time. Water came out beside the wall. —— The third attempt was more troublesome. There was no sink by the wall. Water spread across the floor. Rift had been lying in the doorway. Seeing water on the ground, she immediately stood. First chased it to the wall. The water stopped. The next stream emerged beside the sink. Rift turned to chase it. Stopped again. A third stream appeared on the other side. Rift stopped in the middle of the room. Looked left. Looked right. Finally looked up at Xian. Xian said: “Don’t ask me.” Rift did not ask. She only chose the position most likely to produce the next stream and sat down. Xian looked at her. “You had better not guess correctly before the system.” —— She first shut off the local resource request. The water stopped. That was at least good. Then she opened it again. Normal. Once more. Abnormal. Xian took out her terminal and recorded the positions. She had intended to report: A plumbing problem. Stopped halfway through the form. If it were only a pipe, the water ought at least to emerge somewhere associated with the pipework. The burst by the wall had not seemed like that. She changed it to: shared resource output position inconsistent. The system replied: submit maintenance observation? Xian pressed it. Heng arrived two minutes later. —— The first thing Heng examined was not the wall. It was the record. The wall came second. “Again.” Xian pressed for water. Normal. Heng said: “Again.” Still normal. Xian looked at him. “It pretends to be normal when you come.” “Again.” On the third attempt, water emerged more than twenty centimeters outside the sink. Heng said nothing. He opened the measurement window. ⟦◬ ◫ □ ▣⟧ ⟦⧈ □ ▣⟧ ⟦⋈ □ ▣⟧ First baseline segment: resource observable expected output relation：valid dwelling association：valid Heng recorded it. Opened the supply again. The water drifted left. ⟦Ϟ □ ▣⟧ ⟦⊘ ⧈ □ ▣⟧ ⟦⊘ ⋈ □ ▣⟧ Xian watched the measurement. “Crooked pipe?” Heng did not answer. “Isn’t it?” “Don’t name it yet.” “You’ve really liked saying that lately.” “It’s useful.” —— Heng called up the observation stabilization service. Xian understood immediately. “You’re checking whether this is like the last outage?” “Mm.” During EP012, many things had looked as though the world was broken. Later, it had only been observation stabilization going offline. Heng observed S03 again. ⟦◬ ◫ ◌ ▣⟧ ⟦⋈ ◌ ▣⟧ Status: stabilization service：normal frame association：normal Xian stared at the two lines. “So it isn’t an outage.” “No.” “Could it just be a display error?” “That seems less likely now.” “Why?” Heng pointed at the water on the floor. “Your shoes are wet.” Xian looked down. Her shoes really were wet. A very ordinary piece of evidence. And persuasive. —— Then Xi happened to return from school. She entered and saw puddles in three different directions. And Heng crouching beside the sink. “Is today’s homework water?” Xian said: “No.” Xi put her schoolbag away. “Can I measure it?” Heng said: “Do not enter the affected area yet.” Xi stopped. She rarely heard Heng use that tone. Not angry. Simply leaving no room to negotiate. She automatically retreated to the doorway. “There really is a problem?” Heng said: “Still confirming.” Xi nodded. “Then I’ll do my homework at Li’s.” Xian said: “Good.” After two steps, Xi pointed at Rift. “What about her?” Rift still sat in the middle of the room like a professional forecaster awaiting the next water outlet. Heng said: “Take her too.” Rift did not want to go. The next stream really did emerge in front of her. She immediately lowered her head. Heng was quicker and picked her up entirely. Held in the air, Rift turned to look at the water. Plainly displeased. Xian said: “Don’t let her join the test this time.” “I wasn’t planning to.” —— After his own observation, Heng gave Xian the observer position. “Your turn.” “Wasn’t I the first to see it?” “I need the same protocol.” Xian complied. The first entry was normal. On the second, water arrival drifted right. measurement out of window。 On the third, stable association briefly fell outside the expected dwelling relation. ⟦◬ ◒ □ ▣⟧ ⟦⊘ ⧈ □ ▣⟧ ⟦⊘ ⋈ □ ▣⟧ Xian looked up. “So you didn’t see it wrong.” “Yes.” “Nor did I.” “Yes.” “And the observation service isn’t broken.” “The present evidence does not support that.” “Then it’s only a crooked pipe?” Heng glanced at her. “If only it were a pipe.” Xian did not answer immediately. She knew this differed from his earlier “I don’t know.” —— They temporarily closed the affected output. Activated another local water source. Maintenance capture first collected the water on the floor. The public notice stated only: Some shared resource outputs on this level are suspended. Please use the alternative supply point. It did not say: Spacetime is collapsing. It did not say: An unidentified being has invaded. It did not even say: Structural hazard. Because Heng had not applied that marker yet. Xian asked: “You still aren’t going to mark it as a hazard?” “One more check.” “Of what?” “Confirming this isn’t a one-off structural slip.” Xian looked at him. “It’s already happened three times.” “The earlier attempts did not use the same observation protocol.” “You administrators are very good at making danger queue first.” Heng said: “At least this keeps every strange thing from becoming a hazard.” Xian remembered yesterday’s third observation slot. “All right, then.” This time, she did not argue. —— They waited seven minutes. The alternate source was normal. The affected relation suspended. Heng initiated a controlled test. Only the minimum output. The first second: normal. The second: normal. The third: the resource arrival position jumped outward. Not by a few centimeters. Entirely beyond the original admissible window. ⟦Ϟ □ ▣⟧ ⟦⊘ ⧈ □ ▣⟧ Heng studied the measurement. This time, he did not rerun it a fourth time. He opened the maintenance record. Added a marker. ⟦⟁ □ ▣⟧ Xian saw the symbol. She looked at the symbol first. Then Heng. “This time it really counts as dangerous?” ⟦◒ ∶ ⟁ □ ▣ ?⟧ Heng said: “It counts.” “Are you certain?” ⟦◫ ∶ ⟁ □ ▣⟧ “Certain.” Xian was silent for two seconds. She had seen many things that looked more like the end of the world. During the outage, people’s local presentations had looked as though they were being deleted. Wednesday could be borrowed. Tomorrow could turn up at lost and found. Only yesterday, an observation slot nobody knew how to fill had appeared. Heng had called none of those hazards. So she asked: “Is it serious?” Heng checked the repeated measurements. Then the resource association log. Then stabilization status. Finally said: “This is a bit serious.” Xian went entirely quiet. Not because of the word “serious.” Because Heng had said it. —— Heng immediately applied an intervention requirement. ⟦! ⟁ □ ▣⟧ All affected outputs were excluded. The alternate water route was expanded. Maintenance capture changed to continuous operation. The residential level issued a short notice: shared resource relation under maintenance affected outputs unavailable use alternate points source localization in progress Xian asked: “Do we need to evacuate?” “Not at present.” “Will the water be cut?” “The alternate route is sufficient.” “Will it spread?” “I don’t know.” “What about the third observation slot?” Heng looked up at her. “What?” “Yesterday’s.” “Still in the log.” “Is it associated with this?” “There is no evidence.” “But they happened close together.” “Temporal proximity is not a cause.” Xian nodded. 「R1。」 “Yes.” “I’m beginning to hate this method. It keeps making the answer ‘We don’t know yet.’” Heng said: “Better than pretending to know.” That was difficult to argue with. —— Later, Xi messaged from Li’s. Is the water fixed? Xian replied: Not yet. Xi: Is the world still here? Xian looked at the room. The walls remained. The floor remained. So did Wednesday. She replied: It was still there. Xi: Then I’ll come home later. Xian thought, then added: Do not use the original sink yet. Xi replied: All right. No panic. No farewell. Only a different place to brush her teeth tonight. —— Much later, the H1 group obtained this data. They first placed EP019 beside it. Not to connect them. Deliberately to separate them. The moderator said: “First ask whether the hazard is established.” The researcher listed: • repeated drift； • out-of-window measurement； • intermittent resource / dwelling association loss； • cross-observer reproduction； • S03 normal； • intervention requirement。 The first question converged quickly: Hazard-structure confidence：0.91 / high Only then did they ask: What is the cause? Model ranking: Shared resource-fold structural drift — 0.47 Boundary-layer degradation — 0.26 Local routing defect — 0.13 Coupling to EP019 witness-slot anomaly — 0.10 Instrumentation artifact — 0.04 Someone asked: “The third slot only appeared yesterday. Really no weight at all?” The moderator said: “Some.” “Then why only 0.10?” “Because temporal adjacency is evidence, but not a causal relation.” “So the causal-link confidence?” 「0.14。」 The researcher entered it in the report. Not zero. But far from a conclusion. R1 still held. —— The formal research summary finally stated: Persistent cross-observer instability has been confirmed in a shared resource relation. Unlike the earlier observation-slot anomaly, this event satisfies the native structural-hazard marker ⟁. Meanwhile, in the Seventh Residential Fold, Heng was following the resource trace farther upstream. The local outlet was not the cause. Observation stabilization was not the cause. An ordinary route defect was beginning to look unlikely too. Part of the trace extended beyond the ordinary local distribution map. Xian stood beside him. “Found it?” “Not yet.” “What do you know now?” Heng watched the source trace. “That the problem isn’t only in this sink.” Xian disliked that sentence. But she now knew: Disliking an answer and whether it has evidence are different matters. The real source would only be located at the next step. ## Chapter 21 · The Boundary of the Universe Is Leaking Water The next day, water was still leaking. Not from the same sink. Heng had disabled that sink yesterday. The affected output was excluded. The alternative supply point was normal. The floor was dry again too. If the problem had only been the local outlet, the story should have ended there. But the maintenance trace had not ended. Early that morning, Heng retrieved yesterday’s resource relation. The first section was easy to understand. Inside the dwelling. The second was still normal. shared resource fold。 The third grew troublesome. It did not reconnect to any known local upstream source. Heng enlarged the route map. Enlarged it again. On the map, the relation was not: Misdirected. It was more like: Entering through a position that previously had no entrance. —— By the time Xian arrived, Heng had been at the maintenance panel a long time. “Still not found?” “Part of it.” “Plumbing?” “No.” 「shared route？」 “Not the main source.” “What is that?” Heng did not answer. He overlaid yesterday’s drift with today’s source trace. ⟦⟁ □ ▣⟧ ⟦◬ ◫ □ ▣⟧ ⟦⧈ □ ▣⟧ The hazard remained. So did the measurements. But this time he was not examining: Where the water emerged. Instead: Where the water entered. “This section,” Heng said. Xian approached. A relation crossed into the map from the edge of the local distribution map. No upstream node. No ordinary civic route. Not even an association traceable to the local source registry. Xian watched for a while. “Is the map broken?” “No.” “How do you know?” “All other relations have closure.” “Only this one doesn’t?” “It does have closure.” Xian frowned. “To where?” Heng opened another map layer. Not a dwelling map. Nor a shared-resource map. More like the maintenance interface between the entire Seventh Residential Fold and an external frame. Xian understood half. Then decided not to understand the other half yet. “What is this?” 「interface map。」 “Which interface?” Heng aligned the trace. ⟦Ϟ □ ≀⟧ ⟦◬ ◫ ≀ □⟧ Xian looked at the new symbol. “That isn’t yesterday’s.” “No.” “So there’s another one today.” “This is not an unknown slot.” “You know what it is?” “Yes.” Xian suddenly was not certain that was good news. —— Heng first performed a local shutoff test. affected dwelling supply： off。 shared resource request： off。 local upstream pull： zero。 Then an interface-side measurement: nonzero。 Xian looked at the results. “Wait.” She pointed at the local supply status. “This side is clearly shut.” “Yes.” “Then why is there still a water relation?” “Because it isn’t coming from this side.” Xian fell silent. “I don’t like that sentence.” “I know.” Heng narrowed the incoming trace again. The relation crossed an interface layer that should have maintained separation. Its association status read: ⟦⊘ ⋈ ≀ ▣⟧ expected isolation： incomplete。 Xian stared for a long time. “So the boundary is leaking?” Heng said: “Yes.” “Which boundary?” 「local-world interface。」 Xian paused. She had many questions. But the first to emerge was still the simplest. “The boundary of the universe?” Heng glanced at her. “You could put it that way.” Xian checked the resource trace appearing across the interface again. “The universe’s boundary is leaking water?” “At present, yes.” Xian was silent for four seconds. “Is that more serious than ‘This is a bit serious’?” “Not necessarily.” “How is it not necessarily?” “Yesterday was a hazard classification.” “And today?” 「mechanism localization。」 “So knowing the universe’s boundary is leaking does not make it more serious than yesterday?” “Severity hasn’t increased because the name got bigger.” Xian thought that was a very typical Heng answer. And annoyingly reasonable. —— The real problem was: This was not water from the local side. When Xian first heard that, she thought Heng meant only its source. Later, she realized he was being very literal. They shut all local supplies. The interface crossing remained. Suspended the shared fold’s upstream supply. It was still there. Increased isolation of the affected dwelling relation. It was still there. The incoming resource’s chemical and local-state profile did not entirely match the Seventh Residential Fold’s current supply specification either. It looked very much like water. Could be captured. Could be measured. But its provenance was outside the local registry. Xian asked: “Then where is this water from?” “I don’t know.” “The next fold?” “Possible.” “Farther away?” “Also possible.” “Another world?” “The model hasn’t converged.” “So you know the universe’s boundary leaks, but not which universe’s water is leaking in?” Heng said: “Broadly.” Xian sat down slowly. “Yesterday was better.” —— The maintenance team quickly established interface-side capture. Not by bringing large buckets. Not entirely, at least. Some resource relations were rerouted to the capture frame. Others confined to measurable windows. Local residents received a new notice: Some shared resources remain under maintenance. Alternative supply normal. Do not reactivate affected routes. No line said: A hole in the universe. That had no operational value for residents. Li saw the notice and asked only: “Can I take a shower?” Xian said: “Yes, with the alternative supply.” “Good, then.” “The universe’s boundary is leaking water.” Li paused. “Will it leak into the bathroom?” “Not at present.” “Then call me when the repair is done.” Xian looked at her. “Are you really not curious at all?” “Curious.” “Then why are you so calm?” Li said: “I was curious about the third observation slot yesterday. I’ve used up today’s allowance.” She left. —— When Xi returned from school, a maintenance boundary had been added at the entrance. She watched from outside. “Still can’t go in today?” “You can enter the home, not the affected zone,” Xian said. Xi glanced at the interface map. “Is that the world boundary?” Heng said: 「local-world interface。」 “The teacher said last time that a boundary is a separation condition, not a wall.” “Yes.” Xi looked at the leakage marker. “So the separation condition has failed?” “Locally incomplete.” Xi nodded. “Then I’ll put it in my homework.” Heng said: “Do not treat an active maintenance incident as a classroom experiment.” Xi immediately asked: “Can I after it’s repaired?” Heng glanced at her. “We’ll see.” Xi evidently interpreted that as: Not rejected. Xian said: “Don’t.” Xi was disappointed. Rift cared nothing about homework. Only about the moving water in the capture frame. This time, she did not even get a chance to approach. The maintenance barrier lit in front of her. Rift stopped. Went left. The barrier followed. Went right. Still there. Finally, she sat and expressed very clear displeasure at the barrier. Xian said: “At least something really has been blocked today.” —— Heng formally established: ⟦≀ □ ▣⟧ ⟦⟁ ≀ □⟧ ⟦! ≀ □⟧ interface leakage confirmed。 existing hazard refined。 maintenance intervention active。 Xian looked at ≀. “So this isn’t another new hazard?” “No.” “It’s the source of yesterday’s hazard?” 「mechanism。」 “You care a lot about that word.” “The source may still be traced farther outward. The mechanism is confirmed as interface leakage.” Xian nodded. “So yesterday was: something really is failing.” “Yes.” “And today is: knowing at which layer it fails.” “Yes.” “But not yet what is on the other side.” “Yes.” “Nor why it failed.” “Yes.” Xian sighed. “Your answers are always only partly complete.” Heng said: “Complete answers usually come later.” “You could print that at the management office.” —— To rule out Heng’s map interpretation, Xian performed an observation too. ⟦◬ ◒ ≀ □⟧ ⟦⧈ ≀ □⟧ She saw the same thing. The resource relation already existed before the local upstream supply. The interface crossing was measurable. Local shutoff did not eliminate the crossing itself. Xian studied the data. “So it really is the boundary.” “Yes.” “You haven’t drawn the map wrong.” “Yes.” “And yesterday’s third slot hasn’t secretly turned into water.” Heng paused. “There is no evidence.” Xian said: “I know. I just wanted to hear you say it.” “There is no evidence.” “Good.” R1 could be irritating. But at least it kept tempting stories in the position of stories for now. —— Much later, when H1 received the data, they did not title it: Collapse of the Seventh Habitable Manifold Someone had suggested that in the first draft. It was deleted. Finally, they wrote: A boundary/interface leakage has been confirmed in the local-world maintenance structure, allowing a shared resource relation to traverse an otherwise excluded interface. Boundary-leakage confidence： 0.94 / high World-annihilation confidence： 0.03 / very low Causal-link-to-EP019 confidence： 0.12 / low Mechanism models: Local-world boundary/interface leakage — 0.72 Adjacent-fold resource coupling — 0.16 Local routing artifact — 0.07 Catastrophic world-boundary rupture — 0.03 Coupling to EP019 witness-slot anomaly — 0.02 A researcher looked at the fourth. “We really are assigning catastrophic rupture 0.03 now.” Someone else said: “Because the boundary remains.” “It’s leaking.” “Leaking does not mean absent.” The moderator added: “Being able to locate leakage itself indicates that an interface structure remains locatable.” That sentence later entered the methodological notes. —— In the Seventh Residential Fold, the maintenance queue acquired a formal work order. Not: End-of-the-world response. It was: world-interface leakage repair / shared-resource containment。 priority： high。 resident impact： moderate。 alternate supply： available。 repair closure： pending。 Xian checked once more when she saw it. “So you really intend to repair the universe’s boundary.” Heng said: “Yes.” “Like repairing a wall?” “No.” “Like repairing a pipe?” “Not that either.” “Like what, then?” Heng called up the tool list. Xian took a look. She recognized none. Heng said: “Like repairing an interface.” Xian nodded. “All right, then.” That answer was no easier to understand. But it was sufficient. For the Seventh Residential Fold, the universe’s boundary was not theology. Today, it was simply a high-priority work order in the maintenance queue. And it really was leaking water. ## Chapter 22 · Everyone Thought It Was an Announcement from Management The announcement was posted in the morning. Its position was ordinary. At the corner of the shared passage, near the recent notice: Eastern hallway decommissioned. Please use the western passage. Less than three steps away. The new announcement’s layout was ordinary too. A bold line at the top. Several bullet points below. A maintenance window in the lower right. One final line at the bottom: For the inconvenience, please use the alternative supply point. Xian glanced at it as she passed. “Water shutoff?” Heng stood beside it checking notice synchronization. “Partial.” “How long?” Heng pointed at the time field. “This interval.” “Alternative supply?” “Normal.” “The laundry?” “Normal.” 「observation stabilization？」 “Normal.” Xian nodded. “All right.” She walked two steps. Stopped. Went back. Read the announcement again. This time, she did not begin with the natural-language summary. She read the glyphs. ⟦! ⟁ ≀ □ ▣⟧ ⟦! ⊘ ⋈ □ ▣ ⧗⟧ ⟦! ⊘ Ϟ □ ≀ ⧗⟧ ⟦⋈ ◌ ▣⟧ Xian’s gaze paused at: ⟁ Then at: ≀ She slowly turned. “Isn’t this universe-boundary maintenance?” “Yes.” “Why did you describe it like a water shutoff?” “Because some water will be shut off.” “I mean this announcement.” “What’s wrong?” Xian pointed at it. “Why have you written universe-boundary maintenance like a water-shutoff notice from management?” Heng looked at her for two seconds. “Because it is an announcement from management.” Xian was briefly quiet. She looked at the sheet again. In the lower right, it really had: maintenance contact alternate resource point estimated restoration window Xian said: “...True.” Heng added: “And the water really will be shut off.” —— The residents plainly treated it as an announcement from management too. Not “mistook it for” one. Really treated it as one. After seeing it, Li checked only one thing: “Is the alternative supply point far?” “One corner to the west,” Xian said. “That’s manageable.” “They’re repairing the world interface today.” “I know.” “You saw that?” “Isn’t it in the first line?” Li looked down again. “I only thought I’d have to go west anyway.” “No thoughts at all about the universe’s boundary?” Li thought for a moment. “I hope they finish on time.” A very ordinary wish. And more practical than any cosmic reflection. —— Xi saw it before school too. With her schoolbag on, she stood before the announcement and read every glyph. “Will it be fixed today?” Heng said: “If the closure test passes.” “Can I watch?” “You cannot enter the maintenance zone.” “I’ll watch from outside.” “Do not block the passage.” “Then I’ll stand beside it.” Xian said: “Why do you want to watch so much?” Xi took the answer for granted. “The teacher just said a world boundary is a relational condition, not a wall. I want to see how a relational condition gets repaired.” Xian felt this world’s teaching materials were sometimes poorly suited to cultivating ordinary childhood interests. Heng said: “You can watch the public status.” Xi immediately accepted. For her, that already counted as approval. Rift cared nothing about public status. She only wanted to know whether the maintenance barrier still contained yesterday’s water that changed positions by itself. She tried to slip inside. The barrier lit. She retreated. Tried left. Lit again. Tried right. Still there. Finally, she sat directly before the barrier. Like a professional supervisor refused entry. —— When the maintenance window began, the notice updated automatically. affected relation suspension：active alternate supply：active stabilization service：normal interface repair：starting The first step was not “repair the universe.” The first step was: Shut off things that would obstruct repairing the universe. Affected resource/dwelling associations were suspended. ⟦! ⊘ ⋈ □ ▣ ⧗⟧ Anomaly-related transitions were excluded too. ⟦! ⊘ Ϟ □ ≀ ⧗⟧ Xian filled a cup at the western supply point. This water behaved. Came from where it should. Holding the cup, she stood before the public status panel. “So the local supply is clean now?” Heng said: “The alternate route is.” “What about the leaking side?” “Containment captures it.” “All the water outside the universe is in a bucket now?” Heng glanced at her. “Not a bucket.” “I know.” “A capture frame.” “I know.” “Then why say bucket?” “Because it sounds more like ordinary language.” Heng did not object. —— The actual repair looked less spectacular than imagined. No pillar of light. No sky splitting. No need for residents to keep collectively away from windows. The maintenance team simply narrowed the leakage window segment by segment on the interface map. First confirmed the failure interval of the separation relation. Then isolated unstable coupling. Moved the incoming resource relation off the active leakage path. Established a replacement association. Then put the interface state into a restoration transition. The public status displayed only: ⟦Ϟ ≀ □ ▣ ⧗⟧ Natural language beside it: interface restoration in progress Xian watched for a while. “That’s it?” “For now.” “Repairing the universe’s boundary looks quieter than replacing my water filter.” “Water filters can be noisier.” “That isn’t the point.” —— One measurement failed partway through. Interface separation had recovered to more than ninety percent of the expected range. But the resource relation retained a small crossing that should not exist. Heng did not execute closure. Xian asked: “Isn’t it almost done?” “Almost is not enough for closure.” “Why?” “Because it still leaks.” “Only a little.” “Still leaking.” Xian looked at him. “You hold the universe’s boundary to higher standards than many residents.” “The boundary doesn’t complain.” “That isn’t a reason.” A second restoration round ran. This time, the incoming crossing fell within the maintenance threshold. Heng still did not execute closure immediately. He called another maintenance observer to measure again. Then had Xian check through resident-side public measurement. Xian saw: unexpected interface crossing：none resource provenance：local / expected alternate route：stable She looked up. “What about this time?” “Wait one more window.” “You really are good at delaying the last step.” “Yesterday you wanted me not to leap to conclusions.” “Now I regret it.” —— The final measurement window ended. No new cross-interface inflow. S03 normal. Resource provenance normal. Boundary separation relation maintained. Only then did Heng execute closure. ⟦∴ ≀ □ ▣⟧ public status： maintenance closure：complete Then ordinary resource association resumed. ⟦⋈ □ ▣⟧ A line was automatically added to the notice: Ordinary supply restored. Xian looked at it. “Fixed?” “Fixed.” “The universe’s boundary?” “This leakage incident is repaired.” “You simply refuse to say ‘The universe’s boundary is fixed.’” “Because the interface has more than this one state.” Xian sighed. “Fine. This universe-boundary water-leak incident is repaired.” “Yes, you can.” “The hazard?” 「operationally closed。」 “So yesterday really was dangerous?” “Really.” “And today it really is repaired?” “The present evidence supports that.” Xian nodded. That was the nearest answer to “It’s done” she could currently get from Heng. —— Once the maintenance zone was released, Xi immediately ran over to inspect the public log. “Can I write my homework now?” Heng said: “You may cite the public closure record.” Xi was delighted. “Can I title it ‘Observations of Local World-Interface Leakage Repair’?” Xian said: “Will your teacher really accept that?” Xi said: “Someone wrote about additional-direction balcony arrangements last time.” Xian remembered EP007. “All right, then.” Rift was finally allowed back into the original area too. Her first act was not to check the boundary. It was to inspect the wall corner where water had appeared yesterday. No water. She waited several seconds. Still none. Finally left in disappointment. She was probably the only resident dissatisfied with the whole repair’s result. —— Much later, H1 examined this document. They classified its genre first. facility / property maintenance notice — 0.96 Then its scope. confirmed local-world boundary/interface hazard maintenance — 0.91 The third question: Was repair closure actually completed? 0.93 A researcher listed the clause sequence: intervention suspension anomalous transition exclusion unaffected stabilization service restoration transition closure normal association restored Someone said: “Entirely a maintenance workflow.” Someone else said: “Yes.” “But its target is the world interface.” “That too.” “So does this count as an ordinary notice?” The moderator said: “In document genre, yes.” “In event scale?” “Not ordinary.” This time, nobody found the statements contradictory. After R1, they had become more accustomed to separating inference layers. —— The announcement was still posted there that evening. Its bottom status had changed from: maintenance active To: closed Most residents only glanced at it. Some checked that water was restored. Some checked that the alternate route was canceled. Some never stopped. If an outsider saw only the announcement’s layout, they would probably say: A management notice. Correct. If they then said: It must only be ordinary plumbing repair. That would be wrong. Because the notice really had addressed: confirmed structural hazard。 Really repaired: local-world interface leakage。 Really completed: repair transition。 And really performed: closure。 Management in the Seventh Residential Fold simply did not switch to an epic typeface because of it. They merely changed the status to: Maintenance complete. Ordinary supply restored. The next day, the announcement was taken down. A copy entered the maintenance archive. Heading, location, queue metadata and resident context all remained. For now, at least. If only the middle glyph lines remained one day, That would be another story. ## Chapter 23 · An Archived Fragment Without a Heading The first thing recovered was not the title. It was seven lines. No management heading. No date. No indication of which level it had been posted on. No work-order number. Nor that important sentence archaeology usually loses first: For the inconvenience, please use the alternative supply point. Only this remained: ⟦! ⟁ ≀ □ ▣⟧ ⟦! ⊘ ⋈ □ ▣ ⧗⟧ ⟦! ⊘ Ϟ □ ≀ ⧗⟧ ⟦⋈ ◌ ▣⟧ ⟦Ϟ ≀ □ ▣ ⧗⟧ ⟦∴ ≀ □ ▣⟧ ⟦⋈ □ ▣⟧ HA’s catalog terminal labeled it: provenance：broken source location：unknown original document class：unresolved glyph integrity：high The first archivist enlarged the fragment. “The relations are well preserved.” A second said: “The context is almost gone.” A third called up known token mappings. ! administrative / intervention requirement ⟁ confirmed structural hazard ≀ world boundary / interface leakage □ resource flow ▣ dwelling frame ⊘ scoped exclusion ⧗ temporal reference ∴ closure The room was quiet for a while. The first said: “The content is substantial.” Nobody disagreed. —— They did not name it yet. That mattered. HA’s first round only arranged the surviving relations. First line: intervention over confirmed boundary hazard / resource / dwelling scope Second line: stable resource association suspended within a temporal interval Third line: transition across boundary relation suspended within a temporal interval Fourth line: stabilization service remains associated Fifth line: boundary/resource transition occurs within temporal relation Sixth line: closure Seventh line: resource/dwelling stable association An archivist studied the last three lines. “There is a restoration shape.” Another researcher said: “It could also be post-event reconstruction.” “! is repeated.” “Administrative directives can also occur in terminal emergency protocols.” “Yes.” They did not rush to choose. The danger of this kind of fragment was: You understand a little of every word. Just enough to begin telling a story. —— HA’s database lacked EP022’s complete management layout. Nor did it have: shared passage notice location。 There was no: alternate resource point。 There was no: maintenance queue status。 There was no: closed work order。 They had only a fragment entered into the archive much later, with its provenance chain already broken. A question therefore emerged naturally: Why would one text discuss confirmed hazard, world boundary, suspension, a terminal-like interval, closure and restoration together? Someone first proposed: boundary-maintenance notice Initial confidence was not high. Someone else proposed: emergency continuity protocol Another proposed: eschatological restoration text They began comparing. Not who could imagine the most frightening account. But: Which document family best explained the surviving structure. —— Two days later, HA created a provisional catalog entry. Only then did it acquire a title. THE ESCHATON STELE The natural-language catalog title: The Eschaton Stele Status： PROVISIONAL ARCHIVAL CLASSIFICATION Eschatological-reading confidence： 0.61 Maintenance-notice hypothesis： 0.27 Other： 0.12 Once the title appeared, the entire fragment suddenly looked different. Not one glyph had changed. But human minds began supplying images. ⟁ A final catastrophe. ≀ A rift in the universe. ⧗ A terminal interval. ∴ A final closure. The final element: ⋈ □ ▣ Was even easy to read as: Reestablishing the order of world and matter after disaster. HA’s provisional gloss read: A final boundary failure is declared. Material continuity is suspended, transit across the cosmic breach is forbidden, stabilizing order is preserved for the remnant, and restoration is promised after a terminal interval. Approximate natural-language rendering: Ultimate boundary failure has been declared. Material continuity will be suspended; transit across the cosmic rift is prohibited. Stabilization of the surviving order is maintained, and reconstruction is promised after the terminal interval. It read beautifully. Too beautifully, even. —— If the story stopped here, “The Eschaton Stele” would be a beautiful name. The only problem was: You had already seen these seven lines. Or at least their family. The core of EP022’s management notice, posted in the shared passage beside “Eastern hallway decommissioned,” was: ⟦! ⟁ ≀ □ ▣⟧ ⟦! ⊘ ⋈ □ ▣ ⧗⟧ ⟦! ⊘ Ϟ □ ≀ ⧗⟧ ⟦⋈ ◌ ▣⟧ ⟦Ϟ ≀ □ ▣ ⧗⟧ ⟦∴ ≀ □ ▣⟧ ⟦⋈ □ ▣⟧ When Xian first saw it that day, she asked only: “Water shutoff?” Heng replied: “Partial.” Not because Xian was less intelligent. Nor because HA was more fanciful. Because Xian had been standing beside the notice. HA had not. —— Nobody immediately laughed when H1 received the Eschaton Stele’s catalog entry. The first researcher said only: “That clause order looks familiar.” The second opened a longitudinal corpus search. The third found the EP022 template. The two sources were placed side by side. Seven lines above. Seven below. The first lines matched. The second matched. The third matched. The fourth matched. The fifth matched. The sixth matched. The seventh matched. The laboratory was silent for several seconds. Someone said: “This isn’t similarity.” Someone else said: “This is the same template family.” The moderator did not begin with the Eschaton Stele’s English gloss. He examined the provenance field first. broken Then the archive ingestion note. original header not preserved Then the source-location field. unknown Only then said: “Bring back the maintenance model first.” —— H1 reread each clause. ! Not prophetic speech. Throughout the corpus, repeatedly: administrative requirement。 ⊘ + ⧗ Not an eschatological seal. In EP022: maintenance window scoped suspension。 ⋈ ◌ ▣ Not the surviving order. It was: observation stabilization service unaffected。 Ϟ In this position, not the world reborn. It was: restoration transition。 ∴ It follows repair. It was: maintenance closure。 Finally: ⋈ □ ▣ Even more direct. ordinary resource / dwelling association restored。 The researcher connected the seven lines. 「intervention。」 「suspension。」 「restricted transition。」 「unaffected service。」 「restoration。」 「closure。」 「normal association。」 Someone else said: “This really looks like an announcement.” The moderator said: “Not merely looks like.” She attached the EP022 template ID beside it. “It is a strong template match.” —— A new review note appeared: Strong template match to a boundary-maintenance notice. Maintenance-notice interpretation confidence： 0.92 / high Residual eschatological interpretation confidence： 0.08 / low HA’s original title was not deleted. Archive policy retained: The Eschaton Stele But another line was added underneath: historical catalog label; probable boundary-maintenance notice fragment Natural language: Historical catalog title; very probably a fragment of a world-interface maintenance notice. A researcher studied the two lines together. “So what exactly is the Eschaton Stele?” Someone else said: “A maintenance announcement without its heading.” There was a pause. She added: “More precisely, a maintenance announcement preserved for so long that everyone forgot where it had originally been posted.” That sentence did not enter the formal report later. But everyone remembered it. —— HA did not protest on receiving the review. They reopened the original evidence matrix. An archivist said: “If this template link had been available then, we wouldn’t have ranked it at 0.61.” Another researcher said: “It wasn’t available then.” “So the catalog note was acceptable?” “The provisional classification was acceptable. It now needs revision.” They raised the maintenance hypothesis from 0.27. Lowered the eschatological reading to a historical interpretation. Nobody had to be proved an idiot. The evidence set had simply changed. H1 had learned that in EP018. HA now encountered the same thing: When new provenance returns, the model must change with it. —— The most interesting part was that the source itself had barely moved. No new token. No new clause. No line had suddenly changed from: “Maintenance” To: “Apocalypse.” What changed were the things beside it usually not considered part of the text: Where it was posted. Who issued it. Which queue. What the previous notice was. What happened after repair. Whether this was a known template. Once those things disappeared, The text began to drift. Not the semantic relations themselves. Human stories began to drift. —— Long ago, when the Seventh Residential Fold’s notice was taken down, Nobody called it a stele. Heng simply put the closure copy into the maintenance archive. Xian watched. “How long will you keep it?” “According to archive policy.” “Will anyone read it?” “Possibly.” “Will they understand it?” “If the metadata remain.” “What if they don’t?” Heng thought for a moment. “Then they’ll need the corpus.” Xian said: “What if the corpus is gone too?” Heng paused again. “Then they may give it an impressive name.” Xian laughed. She did not yet know how accurate that sentence would become. —— EP023 has no new secret answer. The real reader gate was completed before the title appeared. If, before seeing: The Eschaton Stele You had already Thought: “Wait, isn’t this the announcement from EP022?” Then what you are doing now is no longer: Following the annotation. Instead: Read the source first, then assess the annotation. That is the ability Season 1 has been training throughout. The next episode will not offer a new grand mystery. Only another announcement. This time, even the provenance is intact. The only more outrageous part Is that the deadline is very far away. ## Chapter 24 · The Last Announcement Stage A — Blind Look only at three clauses first. No new symbols. ⟦! ≈ □ ♲⟧ ⟦! ♲ □ ▣⟧ ⟦! ∴ ♲ □ ⧗⟧ Stop here first. If you have read all the way to this point, this episode should not begin with the question: “Is there a decoder?” Ask first: How much can you already read for yourself? —— Stage B — Minimal Hints All the following tokens are familiar: ! = administrative requirement ≈ = classification □ = local object / resource parcel ♲ = garbage processing ▣ = dwelling frame ∴ = auditable closure ⧗ = relative temporal reference / deadline The three clauses can therefore be reconstructed at least as: There is an administrative requirement. Some parcels awaiting processing must be classified first. A garbage-processing workflow must be completed in the dwelling frame. And closure must occur before a deadline. Only one more piece of local schedule metadata is supplied now: deadline reference：terminal thermal-equilibrium horizon If you have already reached: “...So we just have to finish sorting the garbage before heat death?” Do not continue yet. You have already read the last announcement of Season 1. —— Stage C — Reveal Please Finish Sorting Your Garbage Before Heat Death After world-interface maintenance ended, the Seventh Residential Fold was quiet for several local cycles. “Quiet” was relative, of course. The third observation slot was still under study. It had not disappeared. Nor had its binding suddenly filled itself in. H1 continued to maintain: structure confirmed / binding unresolved But there was no new hazard evidence. Nobody sealed the residential level because of it. Nor dismantled the world interface repaired yesterday. The water resource returned to its normal relation. Wednesday was normal. The eastern hallway remained decommissioned. The breakfast shop operated as usual. Xi kept going to school. Rift kept doing things whose regulatory status was difficult to judge. That was usually sufficient to call: Life returning to normal. Then management issued a new notification. —— It was posted in the shared passage. The kind of shared passage from the first episode. When Li saw it, she and another self were preparing to move three bags. One Li carried two. The other was about to pick up the third bag. The third bag had originally been placed beside the hallway. The Li about to pick up the bag looked down. Then at the emergency passage width marker. She picked up the bag herself. The other Li said: “What’s wrong?” “Don’t leave it in the hallway.” “Only for a moment.” “Even a moment gets a comment.” “From whom?” Both Lis looked toward the other end of the hallway together. Heng had not appeared. Both were silent briefly at the same time. The Li carrying two bags said: “...Never mind. Keep holding it.” That counted as growth. Or at least: Having been told once before. —— They reached the notice. Only three glyph clauses were especially prominent: ⟦! ≈ □ ♲⟧ ⟦! ♲ □ ▣⟧ ⟦! ∴ ♲ □ ⧗⟧ The Li holding one bag finished reading. “Garbage?” The other Li said: “Classification.” “What now?” “Look at the deadline.” Both looked down. The schedule resolver displayed: terminal thermal-equilibrium horizon A reader-facing gloss followed: Before heat death Neither Li spoke. Two seconds passed. The first asked: “Before heat death?” The second said: “It looks that way.” “Isn’t that deadline too generous?” Heng’s voice came from behind. “No.” Both Lis turned. He carried no hazard log today. No interface map. No third-slot validation form. Only an ordinary residents’ maintenance list. Li pointed at the notice. “Heat death.” “Yes.” “Garbage.” “Yes.” “You think those belong in the same sentence?” Heng took a look. “A deadline and a task.” “I’m asking about how it sounds.” “The grammar is fine too.” Li was dissatisfied. —— Heng called up her garbage entries without closure. Eleven. Three should already have been handled. Two still had incomplete classification. One had been marked by Li herself: “Look at it later” But the system evidently did not recognize that as a disposal category. Heng said: “You delayed eleven local cycles last time.” Li said: “That was last time.” “So this time you have longer.” “Longer?” Heng pointed at: Before heat death. Li fell silent. “You cannot call that ‘longer.’” “Why?” “That is almost no deadline.” “Yes.” “Will anyone check garbage classification once the world reaches heat death?” Heng said: “That’s why it says before heat death.” Li opened her mouth. Closed it again. The other Li said quietly: “He won that one.” “Don’t help him.” —— They carried the three bags to the disposal bay. The place from EP004. The pending-discard rack was unchanged. So was the classification scanner. Li placed the first bag on it. The system displayed: classification incomplete She said: “Everything in this bag is unwanted.” Heng said: “Unwanted is your attitude, not a category.” “Have you said that before?” “Something with the same meaning.” Li looked at the classification field. She had once been very good at treating: I do not want to deal with it As: The relation no longer exists. But EP004 had proved that the public garbage workflow did not accept this philosophy. So she did not push the bag onto another manifestation this time. Only sighed. Started sorting. —— The first bag was quick. The second was more troublesome. It contained a local parcel nobody knew when they had left there. It still had a stable association with the dwelling. But nobody remembered its use. Li asked: “What does this count as?” Heng said: “Check the disposal frame first.” “I have.” “Then follow the frame.” “I want to know what it used to do.” “That is another question.” Li held the object. “How do you classify it without knowing its original purpose?” “Garbage categories do not require a complete biography.” Li paused. “You could put that sentence in EP008.” “What?” “Nothing.” She placed the parcel in the correct category. Classification approved. —— Just as the third bag opened, Rift arrived. She walked around it once. Stopped. Looked at one parcel. Then the interface displayed: local role：static background Li closed her eyes. “Don’t.” Rift looked at her. “Do not mark garbage as furniture.” Rift showed no remorse. The classification scanner refreshed. The parcel still required processing. Li picked Rift up entirely. “You used that trick in EP014.” Rift was quiet in her arms for two seconds. Then marked another nearby bag as static background too. Li held her farther away. Heng said: 「classification conflict。」 Li said: “I know.” “Needs resetting.” “I know.” 「deadline——」 “Before heat death. I know.” This time, she finished the sentence herself first. —— Once classified, the three bags entered the normal garbage-processing association. ⟦≈ □ ♲⟧ ⟦⋈ ♲ □ ▣⟧ Final closure: ⟦∴ ♲ □ ⧗⟧ The system displayed: garbage-processing closure：complete deadline relation：satisfied Li checked the deadline. Then closure. “Really only needs finishing before that?” ⟦⊚ ∶ ∴ ♲ □ ⧗ ?⟧ Heng said: “Yes.” ⟦◫ ∶ ∴ ♲ □ ⧗⟧ Li asked: “No ‘If unfinished before heat death, the world will lose its last classificatory order’?” “No.” “No terminal garbage ontology?” “No.” “No universe collapsing because I didn’t sort things?” “No evidence of that at present.” Li nodded. “Good.” R1 had taught everyone not to add things without evidence. —— On the way home, both Lis passed through the shared passage again. They carried no garbage this time. Nor was a third Li lying in the hallway. Only a small synchronization prompt flashed beside one manifestation’s shoulder. The other Li saw. “You’re not fully synchronized yet.” “I know.” “Want to handle it now?” “At home.” “Don’t sleep in the hallway.” “I never said I would.” “Saying it first.” They passed the emergency passage marker. Width normal. Nobody was blocked. Heng approached from behind. A glance. Said nothing. Li turned around. “No reminder today?” Heng said: “None needed at present.” If she had heard that in the first episode, Li would probably have felt she had won. Now she merely said: “Good.” And kept walking. —— The residential level’s evening schedule updated as usual. Wednesday remained Wednesday. The world-interface maintenance ticket stayed closed. EP023’s archive revision had entered the human-side record. Native residents naturally did not know that anyone had once called their water-shutoff announcement “The Eschaton Stele.” The third observation slot remained: unresolved。 Nobody forgot it. Nor did anyone suddenly obtain an answer because Season 1 was nearly over. Some questions could remain open. Some things only needed repairing. And some garbage could not remain unsorted just because the universe was vast. —— Later, Li passed the noticeboard. “Please finish sorting your garbage before heat death” still hung there. She checked her closure status. All complete. She was pleased. Not because she had solved the universe. Not because she had discovered who the third slot was. Not because human researchers had finally translated every source correctly. Only because: What needed doing today had been done today. Rift passed beside her feet. Uninterested in the noticeboard. Very interested in an empty paper bag beside it. Li picked up the bag first. “This needs sorting too.” Rift looked at her. Li said: “Don’t look at me. Before heat death.” She carried the paper bag toward the disposal bay. The shared passage retained its normal width behind her. The Seventh Residential Fold kept existing too. Very unfamiliar. Very vast. Very contrary to human intuition. And— The garbage still needed sorting. --- # 外側日常：第七居住褶 *改編自《外側日常：第七居住褶》第一季新修稿 v1.0 — Aletheia × 留白 · H2，人類策劃* ## 第01章 · 走廊裡的第十三個我 這不是亂碼，也不是逐字替換密碼。 第一回不要求你「翻譯」它。 只要求你確認一件事：它有沒有看起來像一套會重複使用自己規則的語言？ —— Stage A — Blind Record Local record / shared residential passage / first recovered sequence 先只看 source。 ⟦◬ ◫ ⊚∷ ⌇⟧ ⟦◫ ∶ ⊘ ⊚∷ ⌇⟧ ⟦⊚ ∶ ⌁ ⊚∷ ?⟧ ⟦◫ ∶ Ϟ ⌁⟧ ⟦⊚ ∶ ⊘ ⊚∷ → ⊘ ⌁⟧ ⟦◫ ∶ Ϟ ⌁⟧ ⟦⊚ ∶ ⊘ ⊚∷ → ⟁⟧ ⟦◫ ∶ ⟁ ?⟧ ⟦⊚ ∶ ⟁⟧ ⟦◫ ∶ ⊘ ⟁⟧ ⟦◫ ∶ ⌇ ↟⟧ ⟦Ϟ ⊚∷ ⊘⌇⟧ ⟦◬ ◫ ⌇⟧ 先停一下。 你現在完全不需要知道每個符號是什麼。 只看 pattern。 有幾件事應該已經很明顯： • ◫ 反覆站在同一種位置； • ⊚ 也一樣； • ⊚∷ 反覆作為一個組合； • ⌇ 在第一句、第二句與最後兩句都出現； • Ϟ ⌁ 完整重複兩次； • ⊘ 會作用在不同東西上； • ? 並不是每句都有。 所以至少可以先排除一個假說： 這不是隨機符號串。 —— 第一個閱讀問題 不要問： 「這整段中文是什麼？」 先問： 哪些東西看起來在重複扮演同一種角色？ 例如： ⟦⊚ ∶ ⌁ ⊚∷ ?⟧ ⟦◫ ∶ Ϟ ⌁⟧ ... ⟦◫ ∶ Ϟ ⌁⟧ 第二行和第四行完全相同。 這意味著，如果它真是一套語言，那個 speaker / anchor 很可能在兩個位置做了同一類回應。 再看： ⟦⊚ ∶ ⊘ ⊚∷ → ⟁⟧ ⟦◫ ∶ ⟁ ?⟧ ⟦⊚ ∶ ⟁⟧ ⟦◫ ∶ ⊘ ⟁⟧ 你不需要知道 ⟁ 是什麼。 但它顯然先被 ⊚ 提出，接著被 ◫ 質疑，然後又被 ⊚ 維持，最後被 ◫ 用 ⊘ 處理。 這已經不像描述。 比較像爭論。 —— Stage B — Minimal Hints 如果你想繼續 blind reading，先不要看這一段以下。 目前可以公開確認的只有五件事。 ◬ 與： observer confirms a local state 有關。 第一回可暫時讀成： 看見／確認。 ⌇ 與： shared passage / common transit region 有關。 第一回可暫時讀成： 走廊／通道。 ∷ 表示： 同一 identity 的 multiple local manifestations。 所以： ⊚∷ 不是很多個不同的 ⊚。 ⊘ 表示： 某 target / relation 不再屬於目前 local frame。 重要： ⊘ ≠ 摧毀 ⌁ 與： 某 identity / state 在改變後仍能被重新建立 有關。 第一回只給 provisional gloss： persistence / continuity trace。 它的意思之後還會被修正得更精確。 —— 現在再讀一次 ⟦◬ ◫ ⊚∷ ⌇⟧ ⟦◫ ∶ ⊘ ⊚∷ ⌇⟧ 你至少已經知道： • 有一個反覆出現的 address ◫； • 它確認 shared passage 中有 ⊚ 的 multiple manifestation； • 接著它要求某個 ⊚∷ 不再屬於那個 passage frame。 這還不是全文翻譯。 但現在應該已經足以讓標題開始變得可疑： 走廊裡的第十三個我。 —— Still Withheld 第一回不公開： ⊚ ◫ Ϟ ⟁ ↟ 你只需要知道： • ⊚ 與 ◫ 是穩定重複出現的 address； • 它們不是兩個普通中文字人名的替換符號； • Ϟ、⟁、↟ 之後會有更多 corpus evidence。 —— World Note 001 這個世界不要求： 一個居民只能同時有一具 local body。 如果多個 manifestation 維持足夠的 reconstructible continuity，它們可以被居民視為： 同一個「我」。 所以本篇真正奇怪的問題未必是： 「為什麼有十三個我？」 更可能是： 「為什麼其中一個我睡在公共走廊？」 這一回到這裡就夠了。 完整自然語故事請放到 spoiler layer 再看。 ## 第02章 · 電梯今天只到昨天 第七居住褶的早晨通常不太準時。 不是居民不準時。 是「早晨」本身偶爾會在不同住宅之間有一點排列上的意見。 不過這天的問題和早晨沒有關係。 黎站在共享通行廳裡，看著門上新亮起來的提示。 ⟦◬ ◫ ▣ ⌇Ϟ⧗⟧ ⟦◫ ∶ Ϟ ⌇⧗⟧ 她看了三秒。 又看了三秒。 「所以它有壞嗎？」 衡站在牆邊，正在確認另一組住戶申報。 「有。」 「哪裡？」 「終點。」 黎低頭看了一眼腳邊。 地面還在。 門也在。 通行框本身甚至比昨天乾淨。 她按了一次。 門開了。 裡面也很正常。 至少以第七居住褶的標準來說很正常。 通行空間沿著住宅結構往內折了一層，左邊是她現在站著的樓層，右邊則還沒有決定要成為哪個樓層。 黎走進去。 門關上。 下一刻，她又回到了同一棟住宅。 只是公共照明比剛才暗一點。 牆上的清潔紀錄少了一筆。 走廊邊那盆不知道誰養的植物還沒有長出今天新增的第三片葉子。 最重要的是—— 電梯裡已經有四個黎。 其中一個抱著早餐。 一個靠著牆睡。 一個正在看自己的終端。 最後一個則把兩袋東西堆在門口，明顯完全沒有替後來的人留通道的意思。 黎站在門口。 四個黎一起抬頭。 抱早餐的那個先說： 「妳來幹嘛？」 黎回答： 「下樓。」 「那妳來錯天了。」 「我知道。」 睡著的那個沒有反應。 看終端的那個往旁邊挪了半個位置。 最後一個完全不動。 黎盯著她。 「妳那兩袋可以移一下嗎？」 「等一下。」 「我現在要過。」 「我昨天也要過。」 「妳已經在裡面了。」 「所以？」 黎想了一下。 這句話很難反駁。 至少用「誰比較是現在的黎」這個方向很難。 她往外退了一步。 門沒有立刻關。 顯然系統仍然承認她和裡面的四個黎都具有正常通行資格。 這讓她更不高興。 她重新看向牆上的提示。 ⟦Ϟ ⊚ ▣ ⌇Ϟ⧗⟧ ⟦◬ ⊚ ⊚∷⧗ ⌇⟧ ⟦⊚ ∶ ⌁ ⊚∷⧗⟧ 黎用終端連到管理層。 「衡。」 「嗯。」 「我找到問題了。」 「我知道。」 「昨天的我把電梯塞滿了。」 「我知道。」 「那可以把她們清出去嗎？」 衡終於抬頭。 「清去哪裡？」 「別的地方。」 「那是昨天的共享通行框。」 「我知道。」 「她們是昨天合法使用通行框的住戶。」 「我也知道。」 「那妳要我把合法使用中的住戶排出去，讓今天的妳進去？」 黎停了半秒。 「對。」 衡又低頭看他的申報。 「不行。」 門內抱早餐的黎笑了一聲。 現在的黎瞪她。 「妳不要笑。」 「妳昨天也這樣說。」 「我昨天有這麼煩嗎？」 「妳可以明天再問。」 門關上。 黎站在外面，第一次覺得時間偏移本身不是最麻煩的部分。 最麻煩的是自己。 她重新按了一次。 門開。 這次裡面多了一個黎。 五個。 「為什麼又多一個？」 衡的聲音從終端裡傳來。 「妳剛才第一次進去過。」 「所以？」 「所以那裡現在多了一個剛才的妳。」 黎沉默。 她看著那個剛才的自己。 剛才的自己也看著她。 兩邊同時露出很不耐煩的表情。 「這個可以清掉吧？」 「不行。」 「她才剛出現。」 「對。」 「她甚至沒有待滿一分鐘。」 「那也不是排除資格。」 黎把終端拿遠一點。 她現在開始理解，為什麼有些人不喜歡和自己談判。 這時旁邊來了一位住戶。 對方看了一眼門內的五個黎，又看了一眼門上的提示。 「今天只到昨天？」 衡替系統回答： 「目前是。」 那位住戶點點頭。 「那我走樓梯。」 她轉身就走。 黎看著她離開。 又看了一眼門。 「我們有樓梯？」 衡說： 「有。」 「為什麼我不知道？」 「因為妳每次都搭這個。」 黎站了兩秒。 「樓梯到今天嗎？」 「到。」 「正常的今天？」 「目前是。」 黎轉身走了。 走到轉角前，她又停下來。 「所以它其實還能用？」 衡說： 「能。」 「只是只能去昨天？」 「對。」 「那你為什麼說它壞了？」 「因為今天的人通常想去今天。」 黎想了一下。 很合理。 合理到讓她沒辦法繼續吵。 她走進樓梯口以前，牆上的通行狀態又刷新了一次。 ⟦◫ ∶ ▣ ⌇Ϟ⧗⟧ ⟦⊚ ∶ Ϟ ⌇ ?⟧ ⟦◫ ∶ Ϟ ⌇⧗⟧ 黎回頭。 「衡。」 「嗯。」 「這個什麼時候修好？」 「等終點重新解析到現在。」 「多久？」 「不知道。」 「那我明天搭，會到今天嗎？」 衡終於停下手上的工作。 他看著黎。 「妳要不要先把『明天』『今天』『昨天』分清楚再問？」 黎也看著他。 「不要。」 衡點了一下頭。 「那就走樓梯。」 黎走了。 門在她背後又開了一次。 四個昨天的黎和一個剛才的黎還在裡面。 其中抱早餐的那個探出頭。 「妳要不要順便幫我買一份今天的早餐？」 黎沒有回頭。 「不要。」 門關上。 通行系統仍然運作正常。 只是今天，它只到昨天。 ## 第03章 · 寵物登記表不接受「不可描述」 依附生物登記窗口每個月只開兩次。 不是因為申請很多。 是因為每次開都要先確認窗口本身願意留在同一個位置。 黎到的時候，前面已經排了三組。 第一組的 dependent 長得很像一團被折過很多次的毛。 主人把牠放在地上，毛團往左邊滾了半圈，右邊的影子卻先進了櫃台。 衡看了一眼量測框。 「住宅內最大局部展開？」 主人回答得很熟練。 「一點四到二點一。」 衡填上。 「公共通道？」 「零點八以下。」 「夜間？」 「如果牠做夢，不保證。」 衡在備註加了一筆。 下一組更快。 主人直接把一個發光的盒子推上櫃台。 盒子裡沒有東西。 但是盒子外面一直有東西敲盒蓋。 衡問：「最大？」 「三。」 「最小？」 「零。」 「零不行。」 「牠睡著會完全不佔這裡。」 「那是 observable occupancy 為零，不是 local window 下限為零。」 主人想了一下。 「零點零二。」 「可以。」 黎站在後面看了全程。 她忽然覺得今天可能會很順利。 直到輪到罅。 罅沒有排隊。 牠從黎腳邊的陰影裡滑出去一部分，在櫃台旁邊停下。 另一部分仍留在走廊。 還有一小段不知道怎麼回事，從衡身後那面理論上沒有開口的牆裡伸了出來。 衡抬頭。 罅也抬頭。 兩邊互相看了一秒。 衡把表格推給黎。 ⟦Ϟ ⊚ ※ ▣⟧ ⟦◬ ◫ ※ ▣⟧ ⟦◫ ∶ ! ⧈ ※ ▣⟧ 「局部展開範圍。」 黎接過表格。 上面只有一個欄位。 她看罅一眼。 罅正用一個不太確定是不是頭的部分蹭櫃台。 黎很快寫完。 衡拿回來。 看了一眼。 退件。 黎抬頭。 「為什麼？」 衡把表格轉過去。 她填的是： 不可描述 「這欄不接受這個。」 「但牠真的不可描述。」 「我沒有說牠可描述。」 「那你為什麼退？」 「因為這欄不是問那個。」 黎低頭重新看。 欄位標示仍然只有： 局部展開範圍 她指著罅。 「牠沒有固定大小。」 「我沒問固定大小。」 「牠有一部分不在這裡。」 「我看到了。」 「那你怎麼量？」 「量在這裡的部分。」 黎覺得這句話有問題。 但一時找不到問題在哪裡。 她又低頭。 把原本的答案劃掉。 重新寫： 無法確定 衡看都沒多看一次。 又退件。 ⟦⊚ ∶ ⧈ ※ ?⟧ ⟦◫ ∶ ⊘ ⧈ ※ ?⟧ 「你至少考慮一下。」 「考慮過了。」 「你根本沒量。」 「因為妳填的不是量。」 排在後面那位剛才抱著毛團的住戶咳了一聲。 黎回頭。 對方很有禮貌地說： 「第一次辦？」 「對。」 「我上次也寫『視情況而定』。」 「然後？」 「退了。」 「後來怎麼辦？」 對方指了一下櫃台旁的量測框。 「讓牠自己站進去。」 黎轉回來。 罅已經不見了。 或者說，櫃台附近暫時找不到一個適合用「整隻」來形容牠的位置。 黎低頭。 桌面下方傳來一聲很輕的碰撞。 她蹲下去。 罅有一部分塞在抽屜後面。 另一部分從抽屜把手和木板之間不到一指寬的縫裡繞出來。 還有一小塊出現在她鞋底旁邊。 黎抬頭。 「你看。」 衡看了。 「看到了。」 「這怎麼填？」 「先出來。」 罅沒有動。 衡敲了一下櫃台。 「登記。」 罅動了。 牠像一團不太情願的影子，從抽屜、牆面和黎腳邊同時往中央收回。 收的過程沒有明顯遵守體積守恆。 但最後，牠確實有大部分落進了櫃台旁的量測框。 框亮了。 邊界先往外展開。 擴到一個路過居民需要側身的程度。 又縮回來。 接著向上抬高一小段。 最後停住。 衡記下數值。 黎盯著他。 「你剛剛測量了一個不可描述的存在。」 「沒有。」 「你明明有數字。」 「我量的是牠現在用了多少位置。」 「那不是牠真正的大小。」 「對。」 黎停了一下。 「你知道？」 衡看她一眼。 「不然為什麼欄位叫局部展開範圍？」 黎低頭重新看表。 她第一次覺得那六個字帶有某種針對性。 後面的住戶又咳了一聲。 這次比較明顯。 黎只好把衡給的區間抄進去。 抄到一半，罅忽然往旁邊展開。 不是變大。 比較像是「本來沒有算在這一側的部分」突然決定這一側也應該算牠。 量測框立刻往外彈了一格。 衡把黎剛填的上限劃掉。 改大。 黎：「……」 衡：「繼續填。」 「牠會一直變。」 「所以是範圍。」 「牠要是再變呢？」 「更新。」 「一直更新？」 「只要超出登記窗口。」 黎開始懷疑罅是不是故意的。 她低頭看牠。 罅也看她。 然後，像是為了證明自己完全理解這場爭論，牠突然收縮。 整團 local manifestation 往櫃台下面一滑。 下一秒，大部分的罅都進了最下面那個抽屜。 那個抽屜原本只放得下三份表格、一支筆，和一個不知道誰忘記拿走的杯墊。 現在還多了一隻罅。 黎把抽屜拉開。 裡面看起來還是那麼大。 罅也看起來沒什麼不舒服。 「這合理嗎？」 衡低頭看量測框。 數值已經縮成原本的一小部分。 他把下限改掉。 「很好。」 黎有不好的預感。 「又怎樣？」 衡把表格推回她面前。 「現在下限也有了。」 後面的住戶笑出了聲。 黎回頭。 對方立刻把自己的毛團抱高一點，假裝什麼都沒發生。 黎再看向罅。 「妳是來幫我，還是來增加欄位的？」 罅從抽屜裡伸出一小部分，碰了一下她手腕。 很難判斷這算不算回答。 衡把登記框最後一次打開。 ⟦Ϟ ※ ▣⟧ ⟦◬ ◫ ⧈ ※ ▣⟧ ⟦◫ ∶ ⧈ ※ ▣⟧ 黎把新的上下限抄完。 「所以你們完全不在乎牠到底是什麼？」 衡蓋章。 「登記這件事不在乎。」 「那你們在乎什麼？」 「牠在住宅裡會占到什麼。」 衡把表格收走。 「完整本體等妳哪天想寫論文再處理。」 黎想了想。 「我不想。」 「很好。」 下一位住戶往前一步。 罅從抽屜裡慢慢流回黎腳邊。 她們離開窗口時，牆上的登記狀態已經變成通過。 黎走了幾步，又低頭看罅。 「所以妳現在正式是可登記的不可描述存在了。」 罅蹭了她一下。 黎點頭。 「這樣聽起來比較合理。」 後面的衡沒有抬頭。 他已經在問下一位住戶： 「最大局部展開？」 窗口照常運作。 ## 第04章 · 垃圾請在失去因果性前分類 第七居住褶的垃圾撤銷區在住宅下層。 平常那裡沒有什麼值得看的。 住戶把東西帶進去，分類，確認，等一個很短的處理週期，然後那件東西就不再屬於自己日常生活要負責的範圍。 它不一定消失。 沒有人特別在乎。 離開你的生活因果圖以後，東西去哪裡，是下一個 frame 的事。 但今天撤銷區很熱鬧。 因為服務停了。 黎走到入口時，門口已經排了七袋、一只不斷改變材質的盒子、一把拒絕承認自己已經壞掉的椅子，還有一個看起來像小型雲團、但被標籤寫成「廚餘」的東西。 她停在隊伍最後。 牆上的狀態欄正亮著： ⟦◬ ◫ ♲ ▣⟧ ⟦◫ ∶ ⊘ ♲ ▣⟧ 前面一位住戶看了看公告。 「又停？」 衡站在處理口後面。 「暫停。」 「多久？」 「不知道。」 那位住戶想了兩秒，乾脆把自己那袋東西放進旁邊的 pending rack。 架子立刻亮起一個暫存標記。 「那我晚點再來。」 「可以。」 對方轉身走了。 黎看著她。 又看了看手上的袋子。 她忽然覺得事情沒必要那麼複雜。 輪到她時，她把袋子放到處理口前。 「這個已經不是我的了。」 衡抬頭。 「還是。」 「不是。」 衡掃了一下。 面板亮起： ⟦⊚ ∶ ⊘ ⋈ ⊚ □⟧ ⟦◫ ∶ ∴ ⋈ ⊚ □⟧ 黎指著第一行。 「你看。」 衡看了。 「看到了。」 「我已經把關係排除了。」 「妳宣稱排除了。」 「有差嗎？」 衡把第二行往她那邊轉。 「有。」 黎盯著那個符號組。 「哪裡有？」 「公共帳本還閉合。」 「我昨天就不承認它了。」 「系統昨天也沒接受。」 黎低頭看垃圾袋。 垃圾袋非常安靜。 看起來完全沒有想參與這場爭論。 「我心理上已經跟它斷絕關係了。」 衡點頭。 「恭喜。」 「所以？」 「所以妳心理上不用再愛它。」 「我本來就沒有愛它。」 「那更好。」 「那可以收走嗎？」 「不行。」 黎覺得衡今天特別不合作。 她把袋子往左邊推。 面板上的 association 沒變。 她又往右邊推。 沒變。 她把袋子推到一條地板分界線的另一側。 沒變。 「這裡不是我家了吧？」 「還在妳的 dwelling frame。」 黎又往外推了一點。 旁邊 pending rack 自動滑過來，避免她把垃圾推進 shared passage。 黎看著架子。 「它是不是故意的？」 衡說： 「它在防止未完成 discard 的 parcel 堵公共路。」 這句聽起來很耳熟。 黎決定不追究。 她蹲下來，把袋子上原本的 resident label 撕掉。 系統立刻補了一張新的。 她再撕。 又補。 第三次時，垃圾袋旁邊甚至多亮了一個提醒： attribution label removal does not alter attribution 黎抬頭。 「你們連這個都有？」 「因為有人試過。」 「誰？」 衡沒有回答。 黎想了一下。 「是我嗎？」 「不只妳。」 這讓她安心了一點。 至少不是自己專屬的規則。 這時另一個黎從通道另一頭走過來。 她手上拿著昨天那份早餐的包裝。 兩個黎互相看了一眼。 新的那個把包裝放到同一袋旁邊。 系統亮了一下。 兩件 parcel 都掛回同一個 resident address。 第一個黎皺眉。 「那個不是我吃的。」 第二個黎說： 「是我。」 「那妳處理。」 「我就是妳。」 「但不是現在的我。」 「帳本不這樣看。」 兩個黎一起轉頭看衡。 衡正在處理前面那把椅子的臨時暫存。 完全沒有要參與的意思。 第一個黎只好自己問系統。 「哪個 manifestation 產生的？」 面板回： resident attribution sufficient 黎盯了三秒。 「它懶得分？」 第二個黎糾正： 「它不需要分。」 「我覺得需要。」 「因為妳想把責任分給我。」 「對。」 「那更不需要。」 第一個黎很不喜歡這種自己站在制度那邊的感覺。 她抓起那袋垃圾，往房間方向拖。 衡終於抬頭。 「妳去哪？」 「把它放遠一點。」 「可以。」 「這次可以？」 「移動可以。」 「丟掉不行？」 「對。」 黎停住。 「如果我把它放到房間最裡面，算不算退出我的生活因果圖？」 「不算。」 「如果我看不到它？」 「不算。」 「如果我忘記它？」 「不算。」 「如果我叫昨天的我負責？」 第二個黎在旁邊說： 「不要。」 衡說： 「也不算。」 黎重新把垃圾袋拖回來。 「所以我現在唯一能做的，就是承認它還是我的垃圾？」 衡說： 「可以先暫存。」 他指了指 pending rack。 黎看著那排已經擺得很整齊的待處理 parcel。 每一件都還存在。 每一件也都還帶著自己的 attribution。 只有正式 discard workflow 沒有完成。 「那正常時候到底發生什麼？」 衡把 status page切到說明。 沒有長篇解釋。 只有一個很短的 service diagram： resident association → classification → discard → closure → association no longer required 黎看完。 「所以垃圾也不會消失？」 「不一定。」 「那它去哪？」 「看下一個 frame。」 「你們不知道？」 「這個服務不需要知道。」 黎覺得這句跟昨天的登記窗口很像。 管理系統對宇宙的態度似乎一向是： 只知道做到工作需要的程度。 她把垃圾袋放上 pending rack。 架子亮起。 系統確認： ⟦◫ ∶ ! ⋈ ⊚ □ ▣⟧ ⟦⊚ ∶ ⊘ ⋈ ⊚ □⟧ ⟦◫ ∶ ∴ ⋈ ⊚ □⟧ 黎看了一眼。 「我還是不承認。」 衡說： 「可以。」 「真的？」 「可以。」 黎有點意外。 「那你剛才一直反駁我幹嘛？」 「我沒有反駁妳不承認。」 衡指了指 ledger。 「我只是說它還算妳的。」 黎沉默。 第二個黎在旁邊笑了一聲。 第一個黎轉頭。 「妳不要笑。」 「我昨天也說過。」 「妳昨天什麼都說過。」 「那也是妳。」 黎不想再談 identity。 她看向垃圾處理狀態。 「什麼時候恢復？」 衡說： 「不知道。」 「那我今天還要對它負責？」 「要。」 黎看著 pending rack 上自己的袋子。 「我已經跟它沒關係了。」 衡看了一眼公共帳本。 「妳可以繼續這樣想。」 停了一下。 「在系統恢復以前，它也可以繼續算妳的。」 黎離開撤銷區。 走出幾步，她回頭。 那袋垃圾還在。 沒有消失。 沒有追上來。 也沒有獲得靈魂。 只是安安靜靜地待在一個標著她 stable address 的暫存格裡。 她忽然覺得這比有靈魂更煩。 第二個黎跟在後面。 「晚上要不要來看服務恢復沒？」 第一個黎說： 「不要。」 「那垃圾呢？」 「那不是我的。」 身後的撤銷區立刻響了一聲 attribution reminder。 兩個黎一起加快腳步。 今天的垃圾仍然存在。 更糟的是，它還有完整紀錄。 ## 第05章 · 早餐店拒絕尚未出生的客人 第七居住褶靠近東側轉折口的早餐店每天都比大部分住戶更早開。 原因不是老闆勤勞。 是因為那一帶有三種常用早晨。 店裡如果只配合其中一種，另外兩種的人會把午餐也算進早餐時段。 所以店門口一直掛著一塊很簡單的牌子： 只要你現在餓，就算早餐。 弦很喜歡這家店。 規則少。 東西快。 最重要的是，她有會員。 這天她到的時候，店員正盯著服務介面上一筆被拒絕的訂單。 訂單上的 stable address 是她。 又不是現在這個她。 ⟦◬ ◒ ◒⋔⟧ ⟦Ϟ ◒⋔ ☼□⟧ 弦站到櫃台前。 「這是我的吧？」 店員抬頭看她，又低頭看訂單。 「是妳的。」 「那為什麼拒掉？」 「這個版本沒有會員。」 弦停了一下。 她往右邊看。 靠牆的位置站著另一個自己。 或者更精確一點—— 一個仍然沒有決定會不會成真的自己。 那個 future branch 比現在的弦穿得厚一點，手裡沒有東西，卻已經很確定地對櫃台選好了一份煎蛋和一杯熱飲。 她們互相看了一眼。 future branch 先開口。 「我明天想吃這個。」 現在的弦說： 「妳不要替我決定。」 「我只是點早餐。」 「那更不要。」 店員沒有參與這段爭論。 他只把拒單畫面往弦面前推了一點。 ⟦⊘ ⋈ ◒⋔ ☼□⟧ ⟦◒ ∶ ⋈ ◒⋔ ◒⟧ ⟦! ⋈ ◒⋔ ☼□⟧ 弦看了一會。 「她就是我。」 「對。」 「那我有會員。」 「對。」 「所以她有會員。」 「沒有。」 弦看著店員。 店員也看著她。 兩邊都沒有覺得自己說了奇怪的話。 弦決定換個方式。 「你們認得她是我？」 「認得。」 「她的 address 和我有關？」 「有。」 「她如果最後真的變成我呢？」 店員想了一下。 「那到時候她可以用妳當時有的會員關係。」 「那現在呢？」 「現在她還沒有。」 future branch 在旁邊問： 「那我可以現在辦嗎？」 店員把介面切到註冊頁。 畫面停了半秒。 又切回來。 「不行。」 弦轉頭。 「為什麼？」 「她還沒有穩定到能自己持有這個 service relation。」 future branch 很不滿。 「可是我已經可以餓了。」 店員點頭。 「那是真的。」 「可以餓，不能買？」 「對。」 「這規則很爛。」 「也是真的。」 弦第一次對店員有一點好感。 至少對方不會假裝制度本身很優雅。 她把自己的會員狀態調出來。 「那用我的。」 店員說： 「妳可以買。」 「我就是要買給她。」 「那妳買。」 「所以她其實可以吃？」 「我沒說不能。」 弦看著他。 「你們到底拒絕的是什麼？」 店員指了一下訂單。 「拒絕她用自己的 branch relation 下單。」 「那我用我的下單，再給她？」 「妳的事。」 future branch 往前一步。 「我要一樣的。」 弦回頭。 「妳不要再替我點。」 「我是在替我自己點。」 「妳是不是我還沒決定。」 「所以我現在很餓也要等妳決定？」 兩個弦開始互相看得不順眼。 排在後面的一位客人輕輕敲了敲櫃台。 「不好意思。」 弦回頭。 那位客人旁邊也站著一個帶著 branch marker 的版本。 對方的 future branch 手裡已經拿著早餐。 弦指著她。 「她為什麼可以？」 店員看了一眼。 「家庭服務關係。」 「什麼？」 那位客人解釋： 「我把可觀察 future branch 都加進家庭帳戶了。」 弦沉默兩秒。 「可以這樣？」 「可以。」 「你們剛剛怎麼不說？」 店員說： 「妳沒問。」 弦現在非常確定，未來分支不是今天最煩的東西。 她打開服務設定。 找了半天。 沒有找到家庭帳戶。 「在哪？」 店員指了一下。 「妳的 branch policy 設成『不允許未實現 continuation 預先繼承服務資格』。」 弦愣住。 「誰設的？」 介面顯示： N.XIAN 弦轉頭看 future branch。 future branch 也看她。 「這是妳設的？」她問。 「我還沒活到那裡。」 「那就是我設的。」 「看起來是。」 弦開始回想自己什麼時候會做這種事。 很快想起來了。 上一次她的某個 future branch 提前訂了三個月的早餐，最後那條 branch 沒有 realized，帳單卻先進了暫存區。 她當天回家就把預先繼承關掉了。 弦把臉埋進手裡。 future branch 很有禮貌地等她接受這個事實。 店員也等。 後面的人也等。 最後弦抬頭。 「好。」 她指著自己。 「我買。」 店員點頭。 ⟦◒ ∶ ⋈ ◒ ☼□⟧ 訂單通過。 future branch 的原訂單仍然是拒絕狀態。 ⟦⊘ ⋈ ◒⋔ ☼□⟧ 弦看著兩個狀態並排在一起。 「所以你們不是不賣給未來的我。」 「不是。」 「也不是她不存在。」 「不是。」 「只是她沒有這家店的服務關係。」 「對。」 弦接過早餐。 「這聽起來比『尚未出生禁止用餐』無聊很多。」 店員說： 「我們沒有那條規定。」 future branch 在旁邊說： 「我覺得可以加。」 「妳閉嘴。」 店員把下一位客人的訂單拉進來。 弦端著早餐走到旁邊的位置坐下。 future branch 跟過來。 「所以我可以吃嗎？」 弦看了她一眼。 「妳剛剛不是很會自己點？」 「被拒了。」 「那是妳的問題。」 future branch 沉默一秒。 「也是妳的。」 弦低頭看早餐。 這句很難反駁。 她把盤子往中間推了一點。 future branch 伸手。 店裡的服務介面沒有任何反應。 正如店員說的。 它只管誰有資格下單。 不管買到以後誰吃。 弦剛想說點什麼，future branch 忽然停了一下。 她的輪廓稍微淡了。 不是消失。 只是其中一條 possibility 暫時失去了一點 local weight。 弦抬頭看她。 ⟦◬ ◒ ◒⋔⟧ 還在。 弦放心地咬了一口。 future branch 看著她。 「妳明天真的會吃這個嗎？」 弦說： 「現在不確定了。」 「為什麼？」 「因為妳先吃過了。」 future branch 想了想。 「那我是不是正在讓自己不會出生？」 弦也想了想。 然後把另一半早餐拉回自己這邊。 「妳先不要吃了。」 future branch 很不滿。 店員遠遠地看了她們一眼。 什麼都沒說。 他已經開始處理下一筆普通得多的訂單。 至少那一筆只有一個客人。 ## 第06章 · 鄰居把星期三借走了 星期三消失的那天，最先發現問題的不是管理員。 是早餐店。 他們早上照常開門，照常把三種常用早晨都標進服務板，照常把「只要你現在餓，就算早餐」掛在門口。 然後第一個想點星期三套餐的人發現，菜單上沒有星期三。 店員看了一眼。 又看了一眼。 「奇怪。」 旁邊的人問： 「賣完了？」 「不是。」 「那是停賣？」 「也不是。」 店員把 schedule 拉出來。 週期從前一個位置直接接到了下一個位置。 中間乾乾淨淨。 不是空白。 不是 error。 就是沒有那個 slot。 店裡安靜了一秒。 有人說： 「喔。」 然後大家繼續吃早餐。 第七居住褶對這類事情的容忍度一直很高。 只要不要影響結算。 弦聽到消息的時候，正準備去上班。 她走到住宅的公共 schedule board 前。 上面原本應該排列得很規律的 cycle slot，現在中間少了一格。 ⟦◬ ◫ ⌖ ▣⟧ ⟦Ϟ ⋈ ⌖ ▣⟧ ⟦⊘ ⋈ ⌖ ▣⟧ 弦盯著那個位置。 「今天星期幾？」 旁邊有人回答： 「不是星期三。」 「我知道不是。」 「那妳問什麼？」 弦想了一下。 「我想確認我是不是跳過了什麼。」 公共 board 很誠實。 沒有。 是住宅跳過了。 弦找到衡時，衡正站在 schedule terminal 前，旁邊已經排了幾個居民。 第一個人問： 「所以今天不用上班？」 衡說： 「看妳的 obligation 綁哪個 frame。」 第二個人問： 「學校呢？」 「同樣。」 第三個人問： 「預約呢？」 「同樣。」 第四個人很開心。 「那我今天多放一天？」 衡看了她一眼。 「妳原本今天就休假。」 「那我多放一個沒有用途的星期三？」 「本地沒有星期三。」 「那更好。」 她走了。 弦排到前面。 「本地真的沒有？」 「目前沒有。」 「只有我們？」 衡把附近幾個 dwelling frame 拉出來。 隔壁兩個還有。 再遠一點的也有。 只有這一棟的 schedule relation 被排除。 弦看著顯示。 「所以星期三沒消失。」 「沒有。」 「只是我們到不了。」 「對。」 「誰拿走的？」 衡看了一眼操作紀錄。 「鄰居。」 弦等了一下。 「哪個鄰居？」 「不重要。」 「怎麼會不重要？」 「因為現在要處理的是本地 schedule。」 「那借多久？」 「還沒到歸還時間。」 弦本來還想問。 但她忽然想起比較重要的事。 「那我今天的班還算要上嗎？」 衡切到 local obligation。 ⟦◒ ∶ ! ⋈ ◒ ⌖ ▣ ?⟧ ⟦◫ ∶ ⊘ ! ⋈ ◒ ⌖ ▣⟧ 「不算。」 弦立刻冷靜很多。 旁邊原本在抱怨預約取消的人也不說話了。 「確定？」 「本地沒有可到達的星期三，這個 frame 不會記妳缺席。」 弦點頭。 然後問： 「那結算呢？」 衡看她。 「什麼？」 「結算。」 「哪個？」 「工作週期。」 衡把另一個 ledger 拉出來。 ⟦◒ ∶ ∴ ⋈ ◒ ⌖ ?⟧ ⟦◫ ∶ ∴ ⋈ ◒ ⌖⟧ 「算。」 弦又確認一次。 「星期三還算？」 「公共 ledger 算。」 「即使我們這裡沒有？」 「對。」 「即使我沒上班？」 「妳不是沒上班。」 「那我是什麼？」 「沒有可到達的上班日。」 弦站在原地，認真消化這句話。 旁邊那個預約被取消的住戶問： 「這樣也算？」 衡說： 「local schedule 和 public ledger 是兩個 frame。」 對方想了想。 「那我預約費呢？」 「妳去問預約系統。」 對方轉身走了。 衡顯然很滿意這個問題不歸自己。 弦還沒走。 她看著 public ledger。 又看著 local schedule。 再看 public ledger。 「所以今天不用上班。」 「本地對這個 slot 沒有 active obligation。」 「結算照算。」 「對。」 「那星期三什麼時候還？」 衡看了一眼 restoration record。 ⟦◒ ∶ Ϟ ⋈ ⌖ ▣ ?⟧ ⟦◫ ∶ Ϟ ⋈ ⌖ ▣ ⧗⟧ 「之後。」 「多之後？」 「還沒解析到具體位置。」 弦沉默。 正常情況下，她會要求更明確。 這次她沒有。 「那不用急。」 衡抬頭。 「什麼？」 「反正結算還算。」 「是。」 「班也不用上。」 「本地目前不用。」 「那先不要催鄰居。」 衡看了她兩秒。 「我本來也沒打算催。」 弦心情很好地離開。 走到 schedule board 前時，幾個住戶正在討論要怎麼利用這個突然空出來的日子。 有人想睡。 有人想把星期三的清掃挪到星期四。 有人堅持既然星期三不存在，就不能把星期三的垃圾算到星期四。 垃圾撤銷區那邊立刻貼出通知： 垃圾分類依 parcel relation，不依星期名稱。 弦路過時看了一眼。 覺得合理。 她又看向公共 schedule。 隔壁 dwelling 的星期三依舊正常亮著。 一個外棟住戶剛好經過，看到她盯著 board。 「你們這裡沒星期三？」 「嗯。」 「方便嗎？」 弦想了想。 「目前很方便。」 對方點頭。 「我們那邊還有。」 「借我？」 對方很認真地想了一下。 「不行，我晚上有課。」 弦也點頭。 這回答完全合理。 她回到自己 dwelling 前，又遇見一個人。 對方手裡拿著一張錯過的 delivery notice。 「請問星期三去哪了？」 弦指向管理 terminal。 「鄰居借走了。」 「多久？」 「之後會還。」 「那我星期三的包裹呢？」 弦說： 「不知道。」 停了一下。 她又補： 「但結算還算。」 對方看了她一眼。 「我問的是包裹。」 「那你要問快遞。」 弦忽然理解衡剛才為什麼那麼輕鬆。 把不是自己 frame 的問題交回正確 service，真的很舒服。 下午，住宅 board 更新了一次。 星期三仍然不在。 ⟦◬ ◒ ⌖ ▣⟧ 弦重新看了一眼自己的 settlement。 還在。 ⟦◒ ∶ ∴ ⋈ ◒ ⌖⟧ 她關掉終端。 完全沒有催歸還。 那天晚上，整棟住宅都少了一個星期三。 宇宙沒有因此出現裂縫。 時間也沒有停止。 只有幾個人的行程需要重排。 以及至少一個人，因為不上班但照常結算，而對鄰居借走公共 calendrical slot 這件事產生了相當寬容的態度。 星期三之後會回來。 沒有人特別急。 至少弦不急。 ## 第07章 · 禁止在陽台展開第四個方向 析的學校作業原本很簡單。 至少老師是這麼說的。 作業要求： 在不破壞原有住宅三個常用方向的情況下，建立一個新的局部可達方向，放入標準測試物，再完整取回。 最後還附了一句： 請勿於公共通道進行。 析看到這句時，第一個想法是： 那就在陽台。 這個想法本身沒有錯。 問題只是，她只看了學校規則。 沒有看住宅規則。 下午，析把陽台門打開。 先把曬到一半的衣服往左移。 再把一盆不太需要光、但堅持每天跟著光源轉向的植物推到右邊。 空出正中間。 她拿出學校發的方向標記器。 第一步，建立局部錨點。 第二步，確認原有三個方向穩定。 第三步，在「不是前三個方向」的位置給出一個新的可達關係。 析做得很慢。 也很認真。 幾分鐘後，陽台欄杆旁邊多了一個很難用「哪裡」形容的位置。 它不是左邊。 不是右邊。 不是上面。 不是下面。 如果伸手過去，手會在原本三個方向都沒有移動的情況下，碰到另一個可用位置。 析眼睛亮了。 她把一個標準測試方塊放進去。 方塊消失了一半。 另一半還在陽台上。 她又把它拉回來。 完整。 析立刻拍照傳到班級群組。 同學一： 「妳成功了？」 析： 「一次過。」 同學二： 「我的會漏到客廳。」 析： 「妳錨點沒鎖。」 同學二： 「我媽叫我不要再做了。」 析正準備回「技術問題」，住宅系統先跳出一個通知。 ⟦Ϟ △ ⊥ ▣⟧ ⟦◬ ◫ ⊥ ▣⟧ 析看了一眼。 忽略。 三十秒後，門鈴響了。 衡站在外面。 析開門。 「你怎麼來了？」 「陽台。」 「陽台怎麼了？」 「多了一個方向。」 析往裡看了一眼。 「你們現在連這個都會通知？」 「住宅結構有變會通知。」 「那不是住宅結構。」 「我看一下。」 析本來想說不用。 但衡已經走到陽台。 那個新方向還在。 而且很穩。 穩到剛才放進去的測試方塊，現在可以整顆留在那裡，只露出一小角。 衡伸手。 沒有碰方塊。 他換了一個進入方式。 碰到了。 析有點得意。 「怎樣？」 衡說： 「申報。」 析臉上的得意立刻少了一半。 「這是作業。」 「我知道。」 「作業也要申報？」 「如果妳的作業變成住宅結構。」 「它又不是房間。」 衡指著方塊。 「可以放東西？」 「可以。」 「拿得回來？」 「可以。」 「入口在妳家陽台？」 析開始覺得這串問題方向不對。 「……可以。」 「那先量。」 ⟦◫ ∶ ! ⧈ ⊥ ▣⟧ 析皺眉。 「這要怎麼量？」 「照原本的量。」 「它根本不在原本三個方向。」 「那就不要用原本三個方向量。」 析看著衡。 「你剛剛講了一句完全沒有幫助的話。」 衡拿出住宅量測器。 「有幫助。」 他把探測範圍對準那個 additional direction。 量測器沒有把它壓回熟悉的長、寬、高。 而是沿著那個方向本身，建立一個可用的 local window。 析看著數值慢慢穩定。 「這也算？」 「算。」 「但這不是正常尺寸。」 「我沒有量正常尺寸。」 「那你量什麼？」 「妳可以用多少。」 析沉默。 這句很像她前幾天聽黎抱怨寵物登記時，衡說過的話。 她開始理解，大人有時候不是答案很多。 只是很會把問題縮到表格能用。 衡把量測結果傳給她。 「填。」 析沒有接。 「等一下。」 她走到陽台，把測試方塊拿回來。 再把新方向的 local extent 縮小。 原本大概能放一張小桌子的範圍，慢慢縮成只夠塞進一個書包。 「現在呢？」 衡重新量。 「還是填。」 析又縮。 這次只剩一個鉛筆盒的大小。 衡重新量。 「還是。」 析瞪他。 「都這麼小了。」 「小型改建也是改建。」 「這不是改建。」 「那是什麼？」 「作業。」 「作業是用途。」 衡指了一下陽台。 「這是結構。」 析不服。 她打開班級群組。 直接撥給老師。 老師很快接起來。 畫面上先出現一張桌子。 過了兩秒，老師才從桌子的另一個可達面探出來。 「怎麼了？」 析把鏡頭轉向衡。 「管理員說我的作業算住宅改建。」 老師看了一眼新方向。 「妳開在哪？」 「陽台。」 老師停了一下。 「學校不是有寫不要在公共通道嗎？」 「陽台不是公共通道。」 「對。」 析立刻看向衡。 衡沒有任何反應。 老師接著說： 「但那只是學校規則。」 析的表情僵住。 「所以？」 「住宅規定妳自己處理。」 「作業說可以在住宅做。」 「可以做。」 「那為什麼還要申報？」 老師想了一下。 「因為『可以做』跟『不用申報』不是同一句話。」 衡點了一下頭。 析立刻說： 「你不要點頭。」 衡不點了。 老師看著析的方向結構。 「做得不錯。」 析稍微高興一點。 「真的？」 「很穩。」 「那可以交了？」 「量測紀錄一起交。」 析又看向衡。 衡把剛才的數據往她面前推了一點。 老師說： 「正好。」 通話結束。 析現在連最後一個可以求援的大人都失去了。 她抱著手臂站在陽台。 「可是它真的不在原本三個方向裡。」 衡說： 「我知道。」 「那怎麼能算我多蓋一塊？」 「妳能進去嗎？」 「能。」 「東西能放？」 「能。」 「能取回？」 「能。」 「入口在妳家？」 析沒有回答。 衡說： 「那它跟妳家有關。」 析看著那個新方向。 ⟦△ ∶ ⊘ ⋈ ⊥ ▣ ?⟧ ⟦◫ ∶ ⋈ ⊥ ▣⟧ 她最後一次努力。 「那我把它縮到只夠放一支筆。」 她真的縮了。 那個新方向變成一條幾乎看不出來的局部開口。 析把筆插進去。 筆消失。 再拉回來。 衡重新量。 析盯著他。 衡說： 「還是要。」 析深吸一口氣。 「你們的規定到底管到多小？」 「管到它不再是可使用住宅結構。」 「那多小才不算？」 「放不進妳現在這支筆的時候，可以再討論。」 析看著筆。 又看著新方向。 又看著申報表。 最後，她把新方向稍微放大。 衡問： 「幹嘛？」 「反正都要申報。」 她把書包塞進去。 「那我至少要用。」 衡第一次露出一點像是贊同的表情。 「合理。」 析開始填表。 第一欄： 新增結構類型 她填： 學校作業。 系統退回。 析咬牙。 改成： 局部額外方向。 通過。 第二欄： 可用展開範圍 她照衡量的數值填。 第三欄： 用途 析停了一下。 寫： 放書包。 衡看見了。 「不是作業？」 析說： 「作業交完了。」 「那這個呢？」 「現在是收納。」 衡點頭。 「那申報更合理。」 析突然很想把方向關掉。 但想到明天不用再把書包丟客廳，她又忍住。 表格送出。 住宅系統接受。 新 direction 仍然安靜地開在陽台。 析把剩下的作業資料也塞進去。 晚上，同學在群組問： 「妳那個第四方向還留著嗎？」 析回： 「留著。」 「不是作業做完了？」 「現在是櫃子。」 同學回了一串沉默符號。 析很滿意。 她至少從一份必須申報的作業裡，得到了一個不用占原本三個方向的收納空間。 第二天老師評語只有一句： 結構優秀。行政處理自行負責。 析覺得前半句比較重要。 ## 第08章 · 房租不能用童年記憶支付 黎繳房租那天，手上沒有足夠的普通結算資產。 這件事本身不稀奇。 她前兩個週期把能流動的額度花在一堆「現在不買以後會更麻煩」的東西上，其中包括一個會自己重排抽屜的收納框、一組只在晚上有重量的餐具，還有罅非常喜歡、但黎到現在也不知道用途的三顆灰色球。 所以她坐在住宅結算區時，系統很客氣地告訴她： 普通 settlement asset 不足。 黎看了一眼。 「差多少？」 衡把缺口顯示給她。 黎看完，覺得還好。 不是補不起。 只是她現在不想補。 她把自己的可用資產往下翻。 有幾筆太小。 有一筆是未完成的 future credit，現在不能用。 還有一筆是她上個月幫人找回一個迷路方向得到的報酬，但那筆 relation 只能拿去換交通服務。 翻到最下面時，她停了。 那裡有一段很舊的東西。 不是物件。 也不是一個單純可以播放的影像。 它比較像一段仍然和她自己綁在一起的過去。 黎把它拖進評估框。 畫面安靜了一秒。 然後跳出一個很高的估值。 黎挑眉。 「這個夠。」 衡抬頭。 「什麼？」 「這個。」 她把那段 trace 推給他。 ⟦◬ ◫ ◈ ⊚⟧ ⟦⋈ ◈ ⊚⟧ 衡先看了 relation。 再看內容。 那是一個很早的黎。 小很多。 站在一個現在已經不存在的院子裡。 地面剛下過雨。 石縫裡有一點積水。 遠處有人喊她回去。 她沒有回。 因為院牆下有一塊很亮的東西，她一直以為那是什麼寶物，蹲在那裡挖了很久。 最後挖出來的只是一片破掉的透明材料。 小時候的黎卻很高興。 她把那片東西舉到光下面，發現世界會從裂口裡分成兩層。 那段 trace 不只保留畫面。 還保留雨後空氣的味道、膝蓋碰到濕地面的涼、手指沾到泥時的不耐煩，以及她第一次覺得： 原來同一個東西，可以因為看法不同而變成完全不同的世界。 衡把 trace 關掉。 黎問： 「值多少？」 衡重新看估值。 「很多。」 「夠不夠？」 「夠。」 黎立刻把它推進住宅 settlement。 ⟦⊚ ∶ ¤ ◈ ▣⟧ ⟦◫ ∶ ∴ ¤ ◈ ▣ ?⟧ 系統轉了一圈。 拒絕。 ⟦◫ ∶ ⊘ ∴ ¤ ◈ ▣⟧ 黎抬頭。 「為什麼？」 「不能這樣付。」 「你剛剛不是說它很有價值？」 「是。」 「那有價值為什麼不能付房租？」 衡沒有回答。 他先把另一位住戶的 settlement 拉過來。 對方用的是一組很普通的 transferable service credits。 評估。 通過。 closure。 整個流程不到五秒。 那位住戶拿著完成通知走了。 黎看著她。 「她那個明明比我的便宜。」 「對。」 「那為什麼她可以？」 「因為可以完整轉。」 「我的不能？」 「可以轉。」 黎停了一下。 「你現在是不是在故意講話？」 「沒有。」 「有價值。」 「對。」 「可以轉。」 「對。」 「不能拿來付。」 「對。」 黎把手放到桌上。 「那你最好有一個很好的理由。」 衡把她那段 childhood trace 的 relation 展開。 ⟦◫ ∶ ⋈ ◈ ⊚⟧ 黎看了一眼。 「這又怎樣？」 「它還綁著妳。」 「那就拆。」 衡看她。 「確定？」 「不然怎麼轉？」 衡沒有按下去。 他先把 possible settlement result 做成 preview。 那段 childhood trace 從她的 identity relation 上被排除。 畫面裡，小時候的黎還在院子裡。 雨還在。 透明碎片也還在。 但現在的黎看著它時，沒有任何熟悉感。 她知道那件事發生過。 知道畫面裡那個人理論上是自己。 卻沒有「那是我」的感覺。 更麻煩的是，旁邊幾段和它相連的 continuity relation 也開始變淡。 不是整個人消失。 也不是失去所有記憶。 只是有一部分「為什麼後來的自己會變成這樣」變得接不上。 黎盯著 preview。 過了幾秒才說： 「這個是模擬？」 「是。」 「真的轉出去會這樣？」 「大致。」 「大致？」 「實際 side effect 可能比 preview 多，也可能少。」 「你們這個 preview 很沒說服力。」 「所以住宅 settlement 不收。」 黎把畫面關掉。 嘴上還是不服。 「不就是一段記憶嗎？」 衡說： 「不是。」 「差在哪？」 「妳第一回在走廊那個 manifestation，為什麼不能直接拖走？」 黎立刻想起來。 「還沒同步完。」 「那時候我們看的是可重建 continuity。」 「所以？」 「這一段不是普通存檔。」 衡重新打開那段童年 trace。 「它和妳現在還有 anchored relation。」 黎看著雨後的院子。 「所以把它賣掉，我就不記得了？」 「不一定只是忘記。」 「那是什麼？」 「可能變成一個知道發生過，但不再把那件事當成自己人生的人。」 黎皺眉。 「聽起來還是忘記。」 「不一樣。」 「哪裡不一樣？」 衡想了一下。 「妳可以忘記一件事，但它仍然參與妳怎麼變成現在這個妳。」 黎沒有立刻回話。 衡補了一句： 「這段比較接近那種。」 沉默了一會。 黎又看了一眼估值。 真的很高。 高到不只夠這期房租。 還夠她把下個週期也一起結掉。 她很認真地心動了大概十秒。 然後問： 「如果我只切一小部分？」 「可以重新評估。」 「哪部分比較不重要？」 「那不是住宅結算替妳決定的。」 「你不是管理員嗎？」 「不是妳的人生編輯。」 黎很嫌棄地看了他一眼。 「你偶爾講話真的很像公告。」 「謝謝。」 「不是稱讚。」 「我知道。」 黎把 trace 拉回自己這邊。 但沒有立刻關掉。 小時候的自己還蹲在雨裡。 她忽然想起那片透明碎片其實最後被她帶回家，放了很多年。 後來去哪了，她反而真的忘了。 這種普通的忘記，和剛才 preview 裡那種「知道卻不再屬於自己」確實不太一樣。 黎把 settlement request 撤回。 ⟦⊚ ∶ ⊘ ¤ ◈ ▣⟧ 衡關掉 rejection preview。 然後把房租缺口重新顯示出來。 黎看了一眼。 「所以現在呢？」 「房租還是要付。」 ⟦◫ ∶ ! ⋈ ⊚ ▣⟧ 「我知道。」 黎又翻了一次資產列表。 翻到那組只在晚上有重量的餐具時，她停住。 「這個可以賣嗎？」 衡看了一眼。 「可以。」 「會改寫我嗎？」 「不會。」 「有沒有很值錢？」 「沒有。」 黎嘆氣。 「那個收納框呢？」 「有住戶要。」 「真的？」 「有人很喜歡抽屜自己整理。」 黎有點捨不得。 「那罅那三顆球？」 衡說： 「別碰。」 「為什麼？」 「我不知道。」 「你不知道還叫我別碰？」 「罅知道妳要賣嗎？」 黎安靜了。 兩人一起往腳邊看。 罅不知道什麼時候已經出現在桌子下面。 三顆灰色球全都不見了。 黎：「……」 衡：「看來知道了。」 最後，黎賣掉了那組餐具和一部分不再需要的普通 service credits。 房租勉強補齊。 童年還在。 離開結算區以前，黎回頭看了一眼那段 trace。 估值仍然很高。 她把它從「可用 settlement asset」清單移回私人 archive。 停了一下。 又加了一個標記： 不要拿來繳房租。 這個標記本身沒有任何制度效力。 但黎覺得很有必要。 ## 第09章 · 便利商店找零給了兩個可能的明天 弦只是想買一瓶喝的。 她進便利商店的時候，甚至沒有帶任何 future branch 一起來。 至少她以為沒有。 店裡的自助結帳台今天很安靜。 前面只有一個住戶，買了兩個包裹、一份還沒決定口味的點心，和一個看起來像袋子、實際上只在被拿起來時有內側的容器。 結帳都很順。 輪到弦。 她掃了飲料。 又掃了一包小東西。 螢幕顯示總額。 她付款。 ⟦◬ ◒ □⟧ ⟦◒ ∶ ¤ □⟧ ⟦∴ ¤ □ ◒⟧ 交易成功。 這部分完全正常。 弦把東西裝進袋子，等找零。 機器響了一聲。 然後吐出兩個結算提示。 不是兩枚硬幣。 也不是兩張紙。 更像兩份暫時掛在她交易紀錄旁邊的「之後會變成某種東西」的可用 claim。 第一份帶著一個 future branch marker。 第二份也有。 而且不一樣。 ⟦Ϟ ⫯⋔ ◒⟧ ⟦Ϟ ⫯⋔ ◒⟧ 弦盯著它們。 「……什麼？」 結帳台沒有語氣地顯示： 找零已完成。 弦抬頭。 櫃台店員正在整理貨架。 「不好意思。」 店員走過來。 「怎麼了？」 弦指著兩個 settlement。 「它說找零完成了。」 「嗯。」 「哪一個是我的？」 店員看了一眼。 「兩個都跟妳這筆交易有關。」 弦皺眉。 「我不是問跟我有沒有關。」 她點第一份。 「這個？」 店員看： 「如果第一條 future branch realized，這份會穩定。」 弦點第二份。 「這個？」 「如果第二條 realized，這份。」 「所以到底哪個是我的？」 「現在還不知道。」 弦沉默。 「那你們怎麼敢寫『找零完成』？」 店員把 accounting detail 打開。 ⟦◒ ∶ ∴ ¤ ⫯ ?⟧ ⟦∴ ¤ ⫯ ◒⟧ 「價值對。」 「我知道價值對。」 「ledger 也結了。」 「我也知道。」 「那哪裡有問題？」 弦看著他。 「我現在沒有錢可以用。」 店員指了一下兩份 branch settlement。 「有。」 「哪一份？」 「要看之後。」 「我說現在。」 店員停了兩秒。 「那現在沒有穩定形式。」 弦深吸一口氣。 她最近已經很努力接受： • future branch 可以先來點早餐； • 星期三可以暫時不在； • public ledger 可以和 local schedule 各算各的。 但她真的覺得： 找零至少應該是現在的事。 她把第一份 settlement 拉到旁邊的飲料補充機。 想買另一瓶更便宜的。 機器掃了一下。 拒絕。 理由： settlement 尚未 current-frame stable。 弦把第二份也試了一次。 一樣。 她回頭看店員。 店員的表情很像： 我剛剛就是這個意思。 弦說： 「你不要露出那種表情。」 「我沒有。」 「你有。」 店員沒有爭。 排在她後面的人探頭看了一眼。 「branch 找零？」 弦轉頭。 「你也遇過？」 「常用。」 「好用？」 「很好用啊。」 弦看著對方。 對方說： 「我有兩條常用 continuation，一條會經過北側市場，一條會去學校。找零綁 branch，我在哪條 realized 就在哪條用，不用自己搬。」 弦想像了一下。 「所以你覺得這很方便？」 「很方便。」 「你不會想現在就知道自己拿哪一份？」 「我為什麼要知道？」 弦看著他。 對方也看著她。 兩個人同時確定： 對方的生活習慣不可理解。 店員問： 「需要我幫妳改 settlement preference 嗎？」 「可以改？」 「可以。」 弦立刻把終端伸過去。 店員點開設定。 上面寫： 優先：current-frame stable settlement 備選：branch-conditioned settlement 條件：stable form inventory insufficient 時自動切換 弦讀完。 「所以你們是沒零錢？」 「不是。」 「那為什麼切換？」 店員指著最後一行。 本地 current-frame settlement pool 正在重新平衡。 「多久？」 「一下。」 「一下是多久？」 「不知道。」 弦閉上眼睛。 這句她最近聽得太多了。 她又看兩份 branch settlement。 一份如果她明天走 A continuation，會成為可用找零。 另一份如果走 B continuation，會成為可用找零。 價值都沒有錯。 誰也沒有騙她。 系統甚至比普通找零更精確。 她還是不喜歡。 ⟦◒ ∶ ⊘ ⧗ ⫯⟧ ⟦◒ ∶ ⊘ ⫯⟧ 「我不要。」 店員問： 「兩份都不要？」 「這個形式不要。」 「那要等 current pool 回來。」 弦看了一眼時間。 她不想等。 她回頭看貨架。 最靠近結帳區的是一排非常普通的小商品。 電池。 紙巾。 糖。 一包不知道為什麼被分類成文具的透明夾子。 她拿起一包糖。 掃描。 差額還有一點。 又拿一顆薄荷糖。 再掃。 差額： 0 弦看著螢幕。 店員也看。 ⟦Ϟ □ ◒⟧ ⟦∴ ¤ □ ◒⟧ ⟦⊘ ⫯⟧ 兩份 branch settlement 從這筆交易的 settlement frame 裡退掉。 沒有消失。 沒有被銷毀。 只是： 這筆交易不再需要它們。 弦看著乾乾淨淨的結帳畫面。 心情立刻好了。 店員說： 「這樣可以？」 「可以。」 「妳多買了兩樣本來不需要的東西。」 「現在需要了。」 「為什麼？」 「因為它們讓我不用拿明天的找零。」 店員想了想。 「合理。」 後面那個喜歡 branch settlement 的住戶說： 「其實妳可以學著用。」 弦把糖收進袋子。 「我會用。」 「那妳為什麼——」 「我只是不想用在找零。」 她停了一下。 「早餐也是。」 對方沒聽懂。 沒關係。 弦拿著東西離開便利商店。 走到門口，她停了一下。 回頭看那兩份 settlement。 它們已經不再屬於這筆 transaction。 但她的 future branch 還好好的。 一條可能明天會去北側。 另一條可能不會。 都還在。 弦看了一會。 然後很滿意地走了。 宇宙仍然有很多可能。 只是她這次不用等其中一個可能 realized，才知道自己到底拿到了多少找零。 ## 第10章 · 樓上的孩子長出一條新時間軸 析早上發現自己長東西的時候，第一個反應是把被子重新蓋回去。 她沒有尖叫。 也沒有叫大人。 她只是想再睡五分鐘。 因為那個新東西看起來暫時不痛。 五分鐘後，她睜開眼。 還在。 這就有點麻煩了。 它不是手，也不是腳。 不是新的 manifestation。 比較像某個原本必須繞路才能看到的時間關係，突然有了一條可以直接抵達的方向。 析坐在床上，看著書桌上的兩件事。 一件是昨天寫到一半的作業。 另一件是今天早上還沒發生、但已經被學校排進流程的繳交檢查。 以前這兩個 event 對她來說只能靠 schedule service 排出先後。 現在不需要。 她一看就知道。 不是猜。 不是系統提示。 是直接看得到那個 relation。 析愣了一下。 她又拿兩件更無聊的事試。 陽台那盆植物今天轉向光源。 廚房加熱器完成早餐。 原本這兩個 event 在她自己的 observation frame 裡沒有必要直接比較。 現在可以。 析盯著空氣。 「喔。」 她想了想。 「這很方便。」 然後她去刷牙。 —— 早餐吃到一半，析才想起： 新長出來的東西通常要量。 這是她上次在陽台做作業之後學到的。 她很不情願地打開住宅終端。 系統比她更早知道。 ⟦⌑ △ ⊥⧗⟧ ⟦◬ △ ⊥⧗⟧ ⟦⧈ ⊥⧗ △⟧ 通知上只有一句： new stable capacity detected. 析看了一眼。 「它怎麼知道比我快？」 終端沒有回答。 她把訊息轉給衡。 不到十分鐘，衡上樓。 不是因為事情嚴重。 是因為他本來就在附近檢查另一戶把窗外當儲藏層用的申報。 衡進門時，析已經把新 capacity 測了三次。 「早。」 「早。」 「哪裡？」 析指了指自己。 衡看著她。 析補： 「不是身體那種哪裡。」 「我知道。」 她把 measurement 打開。 衡看了一會。 「穩定。」 「嗯。」 「重複得到？」 「五次。」 「妳剛才說三次。」 「你上樓的時候我又試了兩次。」 衡點頭。 析看著他。 「所以是真的？」 「目前看是。」 「不是作業留下來的？」 這個問題有理由。 EP007 那條 additional direction 還在陽台，而且現在已經真的被她當櫃子用。 衡把兩者的 association 分開看了一次。 「不是。」 析有點高興。 「那是我自己的？」 「是。」 ⟦⋈ △ ⊥⧗⟧ 析安靜兩秒。 然後問： 「那我現在算兩個嗎？」 衡抬頭。 「什麼？」 「我有原本那一套。」 析指左邊。 「現在又多一條。」 指右邊。 「那不是兩份？」 「不是。」 ⟦△ ∶ △∷ ?⟧ ⟦◫ ∶ ⊘ △∷⟧ 析確認： 「所以沒有第二個我？」 「沒有。」 「也沒有另一個 manifestation？」 「沒有。」 「地址？」 「一個。」 析明顯鬆了一口氣。 衡問： 「妳很擔心？」 析立刻說： 「學費。」 衡停了一下。 「什麼？」 「如果算兩個學生，學校會不會收兩份？」 衡看著她。 這次是真的沉默了兩秒。 「妳第一個想到這個？」 「很重要。」 「妳長了一條新的 temporal axis。」 「所以才重要。」 析把學校帳務頁叫出來。 「你看，我原本是一個 student address。」 「對。」 「現在 new capacity 也綁我。」 「對。」 「那會不會多一份 obligation？」 ⟦△ ∶ ! ¤ ⋈ △ ⊥⧗ ?⟧ 衡看了一眼住宅端。 「住宅這邊不會把妳算成兩個。」 「學校呢？」 「問學校。」 析皺眉。 「你不知道？」 「我不是學校。」 這句很合理。 合理得讓析不能抱怨。 她打開學校服務台。 因為還沒到上課時間，值班的是一個自動 registrar。 析把 new capacity record 丟進去。 系統掃描。 確認 stable address： N.XI 確認新增 capacity： one 確認新增 student address： zero 然後顯示： billing subject unchanged. 析靠近螢幕。 「所以？」 registrar 回： 學費 obligation 綁定 student address，不綁 capacity count。 衡在旁邊說： 「就是不會多收。」 析沒有理他。 她又問系統： 「那如果以後再長一條？」 billing subject unchanged. 「三條？」 billing subject unchanged. 「十二條？」 billing subject unchanged. 析開始放心。 她最後問： 「那如果我真的變成兩個？」 系統停了一下。 請在發生後重新申報。 析把畫面關掉。 「很好。」 —— 事情本來可以到這裡結束。 但析對新東西的興趣通常不會只停在「不會多收錢」。 她坐回書桌。 把昨天那份作業拖出來。 那份作業有一個很討厭的部分。 老師要求她把幾組原本在不同 local temporal relation 裡的事件排成可比較順序。 上週她做這題時，需要叫外部 service 幫忙建立 comparison。 現在不用。 析看了一眼。 第一組。 直接排完。 第二組。 也可以。 第三組原本最麻煩。 她停了一下。 new axis 很自然地把幾個 relation 展開成可比較結構。 析眼睛亮了。 她開始飛快寫答案。 衡還沒走。 他在旁邊看了半分鐘。 「這是作業？」 「嗯。」 「新能力可以直接用？」 「可以。」 「那很好。」 析寫到一半停下來。 「等一下。」 衡立刻知道她又想到什麼。 「什麼？」 析看著作業。 又看著 new axis。 「如果我可以沿不同 temporal relation 同時比較，那我是不是可以交兩份答案？」 「為什麼要交兩份？」 「一份用原本方法。」 「嗯。」 「一份用新 axis。」 「還是妳的作業。」 「可是方法有兩個。」 「學生還是一個。」 析皺眉。 「你為什麼一直拿 student address 壓我？」 「因為妳一直想把一個學生算成兩份。」 析想了想。 「那我能不能拿兩份分數？」 衡說： 「妳問老師。」 析真的問了。 老師這次回得很快。 不行。 析回： 為什麼？ 老師： 因為妳交的是同一份作業。 析： 但我有新時間軸。 老師： 恭喜。 析： 所以？ 老師： 所以作業應該更快寫完。 析看著那句話。 第一次對自己的成長產生一點後悔。 —— 上午到學校時，她班上有兩個人已經知道這件事。 其中一個是昨天在群組裡說自己 additional direction 會漏到客廳的同學。 對方一看到析就問： 「真的長了？」 「嗯。」 「能用？」 「能。」 「痛嗎？」 「不痛。」 「要申報嗎？」 「住宅不用新增身份申報，capacity record 有。」 「學費呢？」 析很滿意終於有人問到重點。 「一份。」 同學也鬆了口氣。 「那很好。」 另一個同學問： 「你們怎麼都先問學費？」 兩人一起看她。 「因為很重要。」 老師走進教室。 看了析一眼。 「恭喜。」 析有點戒心。 「謝謝。」 「既然妳新的 axis 已經穩定，今天的排序練習不用外部比較服務。」 析沉默。 全班有人笑了。 析低頭看自己的 new capacity。 昨天她還覺得長大可能是一件好事。 今天她開始發現： 新能力最直接的副作用，通常是大人認為你可以自己做更多事。 放學前，學校系統又更新了一次資料。 student address： one. billing obligation： one. stable capacity： plus one. 析看著三行資料，覺得整體還算公平。 至少沒有兩份學費。 至於多出來的作業能力—— 她決定之後再想辦法鑽別的漏洞。 ## 第11章 · 請勿在公共區域使用真名 析把完整名字寫上去的時候，是真的覺得自己很有道理。 學校這週把幾份作業貼到住宅共享區。 她那份正好是前幾天做的 local direction project。 老師說： 「作品旁邊記得署名。」 同學們都寫得很隨便。 有人寫一個暱稱。 有人只留班級 address 的短形式。 還有人畫了一隻根本看不出來和本人有什麼關係的東西，然後堅持那就是簽名。 析不喜歡。 她覺得既然要署名，就應該準確。 尤其她前一天才確認過： 自己還是只有一個 stable address。 既然只有一個， 那就更應該寫最完整的那個。 她站在公共佈告欄前，把完整 resolver form 一筆一筆寫了上去。 寫完還退後看了一下。 很好。 完整。 清楚。 不會和別人搞混。 旁邊同學看了一眼。 「妳寫這麼完整？」 「不然呢？」 「我寫暱稱。」 「那不準確。」 同學聳肩。 「又不是要叫妳過來。」 析正準備回答： 「名字本來就是——」 她忽然停住。 因為自己真的過來了。 不是正在寫字的這個自己。 而是另一個 local presentation。 那個析原本應該還在樓上，把作業資料塞進前幾天申報過的 additional direction 收納區。 結果公共 frame 一解析牆上的 resolver key，她的一個 manifestation 被直接 re-address 到佈告欄旁邊。 兩個析同時看著彼此。 站在旁邊的同學也看著她們。 三個人沉默兩秒。 同學先說： 「妳看。」 析回答： 「這不算。」 「什麼不算？」 「不算妳剛剛說對。」 「可是妳真的被叫過來了。」 「不是叫。」 「那是什麼？」 析還沒想好更精確的詞，公共 display 先跳出提示。 ⟦Ϟ △ ⟟△ ⌇⟧ ⟦Ϟ △∷ ⌇⟧ 接著提示變成： 公共解析狀態：有效 權限狀態：未確認 析皺眉。 「這個欄不是只能顯示嗎？」 同學說： 「它可以解析作品作者。」 「解析短名吧。」 「妳給它完整的。」 析看了一眼牆。 又看了一眼被拉過來的自己。 那個析手上還抱著一疊作業紙。 「妳怎麼來的？」 另一個析說： 「我本來在樓上。」 「我知道。」 「然後突然這裡變成可達位置。」 「我也知道。」 「那妳幹嘛問？」 析沒有回答。 因為這件事正在朝一個她不喜歡的方向發展： 同學可能真的說對了。 公共系統又刷新一次。 那個被拉過來的析往牆邊偏了一小步。 她把手裡的紙抱得更緊。 「我能回去嗎？」 「等等。」 「我還要交別的作業。」 「我知道。」 「妳不是剛長新時間軸嗎？不能自己看快一點？」 「那不是拿來處理這個的。」 「那長了有什麼用？」 析轉頭瞪她。 另一個析也瞪回來。 同學往旁邊退了一步。 「妳們先自己吵。」 這時衡從共享通道另一頭走過來。 他不是特地為析來的。 他手上還拿著兩份完全不同的住宅申報。 只是 public resolver warning 剛好出現在他的管理端。 衡走到佈告欄前。 先看牆。 再看兩個析。 「誰寫的？」 兩個析一起指向寫字的那個。 寫字的析說： 「我。」 衡看了一眼完整 resolver form。 「擦掉。」 析立刻不服。 「為什麼？」 衡指了一下另一個她。 「因為它在解析。」 「這是我的名字。」 「我知道。」 「而且只有一個 address。」 「我也知道。」 析愣了一下。 「那為什麼不能寫？」 衡把公共 display 的權限層打開。 ⟦◫ ∶ ! ⊳ ⟟△ ⌇⟧ ⟦△ ∶ ⊳ ⟟△ ?⟧ 「因為這裡不是妳自己的 resolver frame。」 「可是 key 是我的。」 「對。」 「那我為什麼沒有權限？」 「妳有自己的 key，不代表這裡要執行它。」 析停住。 這句話很像前幾天的： 有新方向，不代表不用申報。 她不喜歡這種句型。 因為通常代表她接下來的漏洞已經被堵了。 「那我自己的名字，也不能寫？」 衡說： 「可以寫顯示名。」 「那不是真的完整名字。」 「夠大家知道是妳。」 析看了一眼同學。 同學把自己的暱稱指給她看。 「我就說。」 析說： 「妳今天話很多。」 衡開始把 full resolver state 從 public frame 排除。 ⟦◫ ∶ ⊘ ⟟△ ⌇⟧ 牆上的完整 form 還看得見。 但 resolver capability 不再對它執行。 幾秒後，那個被 re-address 過來的析感覺到原本的 address path鬆開。 她往後退了一步。 不是在空間裡退。 而是重新回到原本可達的 local structure。 手上的作業紙跟著一起走。 同學看得很開心。 「很酷。」 析說： 「哪裡酷？」 「妳簽名可以把自己叫過來。」 「不是叫。」 「那叫什麼？」 衡說： 「解析。」 同學點頭。 「妳簽名可以把自己解析過來。」 析覺得更難聽了。 她拿擦除工具，把完整 resolver form 清掉。 然後重新寫了一個短名。 只有平常學校、同學和活動板用的 display label。 公共 display 掃了一次。 沒有任何 manifestation 被拉過來。 也沒有權限警告。 析盯著那個短名。 「這樣真的算我嗎？」 衡說： 「夠這裡用。」 「可是它不完整。」 「這裡也不需要完整。」 「那如果有人找錯呢？」 「這個 frame 只需要知道作品是哪個學生交的。」 「不是完整 identity？」 「不是。」 析想了一下。 她忽然發現： 原來「準確」也有 frame。 前一天她才高興自己只有一個 stable address。 今天則發現： 只有一個，不代表每個地方都應該拿最完整的那個來用。 她看了看新簽名。 還是覺得不夠漂亮。 於是在旁邊又畫了一個小圖案。 同學問： 「那是什麼？」 「更安全的名字。」 「看不出來像妳。」 「本來就不是給 resolver 看。」 衡已經轉身準備去處理下一個申報。 析忽然叫他。 「等一下。」 衡回頭。 「什麼？」 析指著牆。 「所以我剛剛不是簽名？」 「妳有在簽名。」 「那為什麼你一直叫我擦？」 衡看著她。 「因為妳寫的不是普通簽名。」 他指了一下剛剛完整 resolver form 所在的位置。 「是 resolver key。」 析想了一秒。 「那老師說『署名』沒有寫清楚。」 衡說： 「妳可以去跟老師反映。」 析眼睛一亮。 這件事終於出現一個她可以追究的人。 晚上，老師收到她的訊息： 建議下次作業說明加註「使用 public-safe display label，不要使用 full resolver form」。 老師很快回： 好。 又過了一會，再補一行： 我以為這不用寫。 析盯著那行字很久。 最後回： 對學生來說需要。 然後她把這張截圖存了下來。 這一次，她覺得自己確實贏了一點。 ## 第12章 · 停電不是世界終結，真的不是 事情最開始只是走廊暗了一下。 不是燈。 燈還亮著。 真正暗掉的是「東西被正常看見」這件事。 黎正從共享通道走回住宅，走到一半，身後兩個 local manifestation 忽然淡了。 不是半透明。 而是普通 observation layer 突然抓不到。 前一秒還有人。 下一秒只剩一個空位置，外加公共系統堅持那裡仍有 address relation。 黎回頭。 「……我是不是少了兩個？」 旁邊居民看了一眼。 「看起來是。」 「那是少了，還是看不到？」 「我不知道。」 「你這回答沒有幫助。」 「我只是路過。」 住宅 display 在這時一起刷新。 ⟦◬ ◫ ◌ ▣⟧ ⟦◫ ∶ ⊘ ◌ ▣⟧ 畫面下一秒少了一角。 不是破掉。 那一角只是忽然失去穩定 presentation，像一塊仍然存在、但不再願意被 ordinary observation 描出來的空白。 有人從樓上喊： 「又來？」 另一個住戶回答： 「這次比較大。」 第三個人很有氣氛地說： 「世界開始被不可見的黑暗吞掉了。」 沒有人理他。 因為便利商店的冷藏櫃還正常。 早餐店也還開。 世界真要終結，通常不會只挑住宅顯示層。 弦從轉角出現。 出現一半。 她右側的一個 branch-linked presentation 還在，左側少了一塊，走起路來沒有影響，但看起來像畫面忘記載入。 「有人現在看得到我全部嗎？」 黎說： 「沒有。」 弦皺眉。 「那我等一下的預約會不會算我沒到？」 黎看著她。 「妳現在這樣還在想預約？」 「不然呢？」 很合理。 樓上突然傳來析的聲音。 「我的時間軸不見了！」 她衝下樓。 本人看起來完整。 但前幾天才長出的那條 additional temporal axis，在住宅 ordinary presentation 裡完全看不到。 析一臉不可接受。 「昨天才長的。」 「我知道。」黎說。 「我還沒用滿一天。」 「能力有保固嗎？」 「不知道。」 「那妳可以問老師。」 析立刻瞪她。 「這又不是作業做壞。」 公共佈告欄也開始降級。 昨天剛修正過的 public-safe display label 還在，但 author resolver 只剩一半功能。 measurement interface 則更直接： local presentation unstable measurement deferred 析站在它前面。 「它連我都量不到了。」 弦說： 「至少妳本人還看得到。」 析低頭看自己。 「目前。」 剛才那位很愛講世界終結的居民又來了。 「現在連高階時間方向都從現實中剝落——」 析打斷他。 「不是剝落。」 「妳怎麼知道？」 「因為我還會。」 「妳看得到嗎？」 析停了一下。 「看不到。」 「那怎麼證明？」 析更不爽了。 她試著用新 axis 排一次事件順序。 結果依然能得到原本的 relation。 只是住宅顯示層不把那條 axis 呈現出來。 她立刻說： 「還在。」 那位居民說： 「也可能是最後的殘響。」 析：「你可不可以不要幫我的能力寫悼詞？」 衡這時終於從管理 terminal 那邊走過來。 他臉色不是緊張。 是忙。 手上有五個 service warning。 後面還跟著一位住戶，正在問垃圾撤銷區今天還算不算正常開放。 衡先回答那位： 「垃圾先不要丟進 presentation 不完整的槽。」 「會怎樣？」 「分類介面現在不可靠。」 「垃圾會消失嗎？」 「不會。」 「那為什麼不能丟？」 衡看著他。 「因為恢復之後還是要分類。」 住戶露出一個「那確實」的表情，走了。 黎立刻插進來。 「我呢？」 衡打開她的狀態。 ⟦⊘ ◬ ⊚∷ ▣⟧ ⟦⊚ ∶ ◬ ⊚ ?⟧ ⟦◫ ∶ ⊘ ◬ ⊚ ▣⟧ 「現在 ordinary observation 抓不到妳全部。」 「所以我少掉了？」 衡沒回答這個問法。 他看 persistence。 ⟦◫ ∶ ⌁ ⊚⟧ 又看 dwelling association。 ⟦◫ ∶ ⋈ ⊚ ▣⟧ 「沒有。」 黎鬆了一點。 「那我左邊那兩個呢？」 「relation 還在。」 「看得到嗎？」 「現在不穩定。」 「那你為什麼這麼確定？」 「因為不是只有 observation 一條 relation。」 黎想了一下。 這句她聽懂了。 弦立刻排到下一個。 「我。」 衡切過去。 她的 presentation 還是一半完整、一半像被畫面跳過。 ⟦⊘ ◬ ◒∷ ▣⟧ ⟦◒ ∶ ◬ ◒ ?⟧ ⟦◫ ∶ ⌁ ◒⟧ ⟦◫ ∶ ⋈ ◒ ▣⟧ 弦看完只問： 「所以我的預約？」 衡說： 「妳還在。」 「我知道。我問預約。」 「預約系統那邊目前也降級。」 「會算缺席？」 「不知道。」 弦深吸一口氣。 「這才是問題。」 黎非常同意。 析把自己擠進來。 「我的新 axis。」 衡看了一眼。 ordinary observation： unavailable capacity association： stable measurement： deferred 析問： 「所以還在？」 「還在。」 「只是現在看不到？」 「對。」 「那作業證明呢？」 衡看她。 「妳昨天不是已經交了？」 析停住。 「喔。」 這個問題暫時解決了。 公共區域開始有人把情況越講越大。 「住宅邊界正在失去可見性。」 「一部分時間不再呈現。」 「個體開始從世界表面剝離。」 還有人把一句： observation service unavailable 轉述成： 世界停止承認觀察者。 衡沒有參加任何一種解釋。 他只在看 restore queue。 幾分鐘後，系統終於回了一條 transition estimate。 ⟦Ϟ ◌ ▣ ⧗⟧ 黎問： 「多久？」 「短 offset。」 「人話。」 「等一下。」 「那就說等一下。」 衡沒理她。 住宅裡那種「有東西還在，但畫面不肯承認」的感覺持續了一會。 然後第一個 manifestation 回來了。 不是被創造。 只是 ordinary observation relation 重新成立。 接著第二個。 弦缺掉的 presentation 一塊一塊恢復。 析的新 temporal axis 也重新出現在 measurement layer。 她第一件事不是歡呼。 是立刻把昨天那份作業重新掃一次。 「數據一樣。」 衡說： 「因為它本來就沒消失。」 析點頭。 合理。 那位一直說世界被黑暗吞掉的居民站在旁邊。 他看著所有東西重新出現。 沉默幾秒。 「所以……不是末日？」 黎說： 「你可以繼續當末日。」 「什麼意思？」 「只是我們這邊看起來已經修好了。」 弦的預約系統也恢復。 沒有算缺席。 她的心情明顯比世界沒有終結更好。 住宅 display 最後把 incident state 收回 ordinary mode。 就在所有人準備散開以前，terminal 留下兩行沒有翻譯的紀錄。 Major Gate 01 先不要往下找 decoder。 最後兩句是： ⟦⋈ ⊚ ▣⟧ ⟦◫ ∶ Ϟ ⋈ ▣ ⧗⟧ 這裡沒有新符號。 如果前十一回的 relation 已經開始變成直覺，先自己回答： 1. ⊚ 和住宅的 relation 還在不在？ 2. ◫ 說的是永久失去，還是之後會 transition？ 3. 前面那些「突然看不到」比較像 existence failure，還是 infrastructure failure？ 先停在這裡。 不要急著看官方答案。 ## 第13章 · 人類把「午休」翻成「低階死亡」 弦吃完午飯之後，做了一件非常普通的事。 她看了一眼下午的 schedule。 第一個 appointment 還有一段時間。 一條 future branch 提醒她： 如果現在不休息，晚一點會後悔。 另一條 future branch 說： 如果現在休息，晚一點也可能後悔。 弦把兩條提示一起關掉。 「那我自己決定。」 她把窗邊的 ordinary observation presentation 調暗。 不是停掉。 也不是把自己排除出住宅。 只是把原本維持得很完整的 local manifestations 收掉幾個。 ⟦◬ ◒∷ ▣⟧ ⟦⊘ ◬ ◒∷ ▣⟧ 她躺下。 外面的住宅褶還是照常運作。 有人在共享通道搬東西。 有人在樓下抱怨找零。 析不知道在什麼地方又和學校規定打架。 弦沒有參與。 她只是睡著。 睡著以後，她仍然和 dwelling 保持 stable association。 她的 reconstructible persistence 也沒有中斷。 ⟦⌁ ◒⟧ ⟦⋈ ◒ ▣⟧ 只是不再花力氣維持全部 ordinary presentation。 對第七居住褶的人來說，這完全不值得記錄。 對很久以後的人類研究組來說，不是。 —— H0 研究室拿到這段 fragment 的時候，資料已經不完整。 沒有影像。 沒有聲音。 沒有「午休」標籤。 沒有住戶日誌。 沒有 activity metadata。 只有 relation corpus。 一位研究員把七行 glyph 投到牆上。 ⟦⊘ ◬ ◒∷ ▣⟧ ⟦⌁ ◒⟧ ⟦⋈ ◒ ▣⟧ ⟦⧗ ◒ ▣⟧ ⟦Ϟ ◒∷ ▣ ⧗⟧ ⟦◬ ◒∷ ▣⟧ ⟦☼ □ ◒⟧ 「先不要翻自然語。」主持人說。 「先列 relation。」 另一位研究員開始寫。 「active observation 降低。」 「persistence-like trace 保留。」 「subject 與固定 locus association 持續。」 「之後有 temporal offset。」 「manifestation 回來。」 「最後有 consumption。」 主持人點頭。 「有沒有 entity deletion？」 「沒有。」 「有沒有 continuity break？」 「至少這段看不出來。」 「有沒有 reconstitution-like pattern？」 「有。」 有人說： 「這比較像休眠。」 另一個人回： 「也可能是某種 death-like reversible phase。」 沒有人笑。 因為兩個說法都合理。 他們手上的資料只告訴他們： 這個 subject 先不再普通可觀察，之後又回來，期間 persistence 沒斷。 如果你從一個完全不同的生物學與存在論傳統出發， 這很容易被叫成： reversible death。 研究組開始打 confidence。 Low-order death state： 0.62 Reversible dormancy / inactive phase： 0.31 Observation-layer service degradation： 0.07 一位比較保守的研究員看著第二個數字。 「我還是覺得 dormancy 應該更高。」 主持人問： 「理由？」 「因為 stable locus association 沒斷。」 「death-like state 也可以不斷。」 「persistence 也沒斷。」 「所以不是 full death。」 「後面 consumption 也可能只是醒來吃東西。」 研究室安靜了一秒。 有人把這句寫進 note。 Alternative mundane interpretation cannot be excluded. 主持人看了一眼。 「保留。」 然後他們繼續工作。 沒有人知道，那句話其實幾乎就是答案。 —— 過了一段時間。 弦醒了。 ⟦⧗ ◒ ▣⟧ ⟦Ϟ ◒∷ ▣ ⧗⟧ ⟦◬ ◒∷ ▣⟧ 她第一件事不是確認自己有沒有復活。 是看 appointment。 「還來得及。」 第二件事是餓。 她去拿了點東西。 ⟦☼ □ ◒⟧ 吃完以後，又確認了一次自己的 dwelling relation。 ⟦⋈ ◒ ▣⟧ 還在。 一直都在。 她根本不知道，某個很久以後的研究資料庫裡，自己剛剛完成了一次： low-order death → causal residue → reconstitution → restorative ingestion 的完整流程。 如果知道，大概只會問一件事： 「那午睡算不算請假？」 —— H0 的 provisional report 最後寫得非常漂亮。 Subject enters a low-order death state, retains causal residue, reconstitutes after temporal displacement, then performs restorative ingestion. 中文摘要： 主體進入低階死亡，保留因果殘留，經時間位移後重構，並執行恢復性攝取。 下方還有一行很謹慎的附註： Reversible dormancy / inactive phase remains a viable alternative. Confidence： 0.31 在這一整頁研究報告裡， 最接近真相的那一句， 分數最低。 而弦已經吃完東西，出門去做下午該做的事了。 ## 第14章 · 罅把訪客標記成家具 弦去黎家作客的時候，先被門口認成了一個東西。 這句話聽起來不好聽。 但住宅 visitor layer 本來就這樣工作。 先確認： 有一個 coherent entity 進入 dwelling frame。 再確認： 這個 entity 和哪個 stable address 有關。 門邊的 presentation 一閃。 ⟦◬ ※ ◇ ▣⟧ ⟦⋈ ◇ ◒ ▣⟧ 弦看了一眼。 「為什麼我是菱形？」 黎在裡面說： 「那不是妳的名字。」 「那是什麼？」 「先確定妳是一個東西。」 弦停在門口。 「你家的系統歡迎方式很差。」 「不是我家的。」 黎指了指趴在桌下的罅。 「牠的 visitor classifier。」 罅抬頭看了弦一眼。 只一眼。 接著 presentation 又跳了一次。 ⟦≈ ※ ◒ ▱⟧ ⟦◬ ※ ◒ ▱⟧ 然後罅不看她了。 弦一開始沒發現。 她把帶來的東西放到桌上。 罅沒有反應。 她從門邊走到窗邊。 罅從她前面經過時，路線非常自然地繞了一個小弧。 弦回頭。 罅繼續走。 她往左移一步。 罅繞左邊。 她往右移一步。 罅繞右邊。 弦皺眉。 「牠在躲我？」 黎正在拆她帶來的東西。 「牠平常也會繞人。」 弦故意站到罅正前面。 罅停下。 往旁邊繞。 弦再擋。 罅又繞。 第三次，罅甚至提前改路。 整個過程沒有一次抬頭看她。 ⟦⊘ ◬ ※ ◒⟧ 弦慢慢轉頭。 「黎。」 「嗯？」 「你家寵物是不是看不到我？」 黎抬頭。 「看得到吧。」 「牠完全不看我。」 「那也可能是不想理妳。」 「我希望是那個。」 弦走到罅旁邊，蹲下來。 「罅。」 罅從她膝蓋旁繞過去。 弦站起來。 又走兩步。 ⟦Ϟ ◒ ▣⟧ 「我明明在動。」 黎看了幾秒，終於覺得有點不對。 她把罅的 local classifier 拉出來。 最上面一行寫： target: N.XIAN 下一行： local role: static background 黎沉默。 弦湊過去。 「那是什麼？」 黎說： 「牠把妳標成背景了。」 「背景？」 「靜態背景。」 弦看了看自己。 又抬手晃了晃。 「我一直在動。」 「我知道。」 「那為什麼還是靜態？」 黎往下看設定。 「分類沒有更新。」 弦又沉默兩秒。 「牠是不是把我變成家具了？」 黎立刻說： 「沒有。」 「那為什麼我在牠那裡跟家具一樣？」 「因為家具通常也不用主動追蹤。」 這個答案完全沒有安慰作用。 弦走去拿桌上的杯子。 拿得動。 她又坐下。 坐得下。 她開口： 「我會說話。」 黎說： 「我知道。」 「我還能走。」 「我也知道。」 「那你快把那個標記拿掉。」 「正在。」 黎把 classification relation 清除。 ⟦⊚ ∶ ⊘ ≈ ※ ◒ ▱⟧ 罅停了一下。 抬頭。 第一次正眼看向弦。 ⟦◬ ※ ◒⟧ 弦往左走。 罅的 attention 跟著往左。 她往右。 罅也跟。 ⟦Ϟ ◒ ▣⟧ ⟦◬ ※ ◒⟧ 弦終於鬆了一口氣。 「所以我沒變成家具。」 「沒有。」 「只是被牠當家具？」 黎想了一下。 「嚴格來說，是背景。」 弦看著罅。 罅現在又開始正常注意她了。 甚至還聞了聞她帶來的袋子。 弦說： 「這有比較好嗎？」 「有。」 「哪裡？」 「背景比家具廣。」 弦覺得黎沒有在幫忙。 —— 很久以後，H0 研究室拿到的不是整段。 他們只有： ⟦≈ ※ ◒ ▱⟧ ⟦◬ ※ ◒ ▱⟧ ⟦⊘ ◬ ※ ◒⟧ 以及更前面兩行 entity-binding metadata： ⟦◬ ※ ◇ ▣⟧ ⟦⋈ ◇ ◒ ▣⟧ 研究員先確認： 「◇ 應該是 generic entity slot。」 「和 ◒ 綁定，所以 target identity 沒問題。」 「※ 對 ◒ 做了 ≈ relation。」 「result role 是 ▱。」 「之後 ※ 停止 active tracking。」 主持人問： 「movement evidence？」 「這個 recovered sample 沒有。」 「persistence？」 「不在 sample 裡。」 「classification removal？」 「也沒有。」 他們開始列 hypothesis。 第一個： Ontological furnishing-state conversion — 0.58 第二個： Local behavioral / attentional classification — 0.34 第三個： Temporary perceptual suppression — 0.08 一位研究員盯著第二個。 「如果 ≈ 只是 classifier，▱ 可能不是物種或本體狀態。」 另一位說： 「但後面 tracking 確實停止。」 「分類本來就可能改變 tracking policy。」 「那為什麼是 static？」 「因為沒有 movement fragment。」 研究室安靜了一會。 最後主持人說： 「兩種都保留。先給 conversion 較高 confidence。」 報告最後寫： The dependent converts the visitor into an inert furnishing state and subsequently ceases active tracking of the transformed subject. 中文摘要： 高階 dependent 將訪客轉化為惰性家具狀態，隨後停止對轉化後主體的主動追蹤。 同一時間，真正的弦正在黎家把杯子移到另一邊。 罅的視線跟著杯子。 又跟著她。 完全沒有任何家具，因為被分類而變成人。 也沒有任何人，因為被分類而變成家具。 只有一隻寵物的 classifier，剛剛把訪客標錯了。 ## 第15章 · 逆因果快遞請先填寄件原因 黎只是想把保溫盒還給弦。 事情本來應該很簡單。 盒子是弦前幾天借她的。 裡面現在多塞了一包弦上次說想吃的脆片，旁邊還有一小罐調味醬。 黎把三樣東西裝進 parcel sleeve，走到住宅層的快遞區。 普通配送窗口前排了四個人。 逆因果窗口一個人都沒有。 黎看了一眼時間。 又看了一眼弦剛才傳來的訊息。 妳如果要還盒子，今天給我。 我晚上要用。 黎走向逆因果窗口。 櫃台上方寫著： Destination-first service available. 下面還有一行比較小： origin-side records may be completed after destination settlement. 黎把包裹放上 intake surface。 「寄給弦。」 系統辨識 parcel。 ⟦↶ □ ⧗⟧ 畫面跳出三個欄位。 收件地址：已確認 parcel：已確認 寄件原因：可後補 黎看到最後一欄，沒有填。 她按下送出。 包裹消失得很平常。 沒有光。 沒有旋轉。 沒有任何像「因果倒轉」的視覺效果。 它就是不在桌上了。 兩秒後，弦傳來訊息。 收到了。 黎低頭看。 「這麼快？」 弦又傳： 盒子、脆片、醬。 醬是我的嗎？ 黎回： 是。 弦： 那我拆了。 黎： 妳不是已經拆了嗎？ 弦： 我是在確認妳有沒有哪個版本還沒同意。 黎覺得這句話很合理。 她正要離開，快遞窗口發出一聲很小的提示音。 畫面上多了一條紅框。 ⟦⊘ ∴ □⟧ ⟦! ≡ □⟧ 此件尚未結案。 請補填寄件原因。 黎停下。 她看著畫面。 又看了一眼弦的訊息。 弦剛好又傳來一張照片。 保溫盒已經在她桌上。 脆片少了一半。 黎抬頭。 「東西不是到了嗎？」 窗口回答： destination delivery：complete 「那為什麼沒結案？」 auditable closure：incomplete 黎皺眉。 「有差嗎？」 窗口沒有把這句話當成申訴，只把兩個狀態並排顯示。 delivery：complete destination association：complete filed justification：missing closure：open 黎指著第一行。 「這個不是最重要的嗎？」 對收件而言，是。 她又指最後一行。 「那這個呢？」 對帳而言，是。 黎沉默了一下。 「所以你們可以先把東西送到，再叫我說我為什麼寄？」 是。 「如果我不填呢？」 parcel 不會自動退回。 「弦會突然沒收到？」 不會。 「包裹會消失？」 不會。 「那你還要我填？」 是。 黎第一次覺得這個系統很有衡的風格。 她拿出終端。 弦那邊又來一條訊息。 脆片不錯。 黎看了看「寄件原因」欄位。 她輸入： 歸還弦借我的保溫盒。 想了一下，又補： 順便放脆片和醬。 系統沒有立刻接受。 下面跳出一個小提示： justification scope includes all associated parcel contents. 黎把游標移回去。 「我不是都寫了嗎？」 「順便」不是可稽核 association description。 黎盯著它。 「你們連順便都不接受？」 接受日常語言。 但 closure record 必須能對應 parcel contents。 黎刪掉「順便」。 改成： 歸還弦借我的保溫盒，並交付先前約定給弦的脆片與調味醬。 窗口停了半秒。 ⟦⧗ ≡ □⟧ ⟦Ϟ ≡ □ ⧗⟧ ⟦⋈ ≡ □⟧ ⟦∴ □ ≡⟧ 紅框消失。 已結案。 黎看著那三個字。 「所以剛剛那幾分鐘，東西已經在弦那裡，但理由還沒在這裡。」 是。 「那到底是哪個先造成哪個？」 窗口這次停得比較久。 然後顯示： 此服務未要求以該問題完成操作。 黎笑了一下。 「很會逃。」 系統沒有回應。 她準備離開。 弦又傳來： 醬太辣。 黎回： 妳現在才說？ 弦： 我也是收到之後才知道。 黎看了一眼剛剛已經閉合的寄件紀錄。 忽然覺得這個宇宙最逆因果的部分，可能不是快遞。 —— 很久以後，H0 研究室拿到的資料少得多。 他們沒有快遞窗口。 沒有「保溫盒」。 沒有弦的訊息。 沒有「醬太辣」。 只有： ⟦↶ □ ⧗⟧ ⟦Ϟ □ ◒⟧ ⟦⊘ ∴ □⟧ ⟦! ≡ □⟧ ⟦⧗ ≡ □⟧ ⟦∴ □ ≡⟧ 研究員先把已知項列出來。 「□ 還是 local parcel。」 「◒ 是同一個 stable address。」 「Ϟ 是 transition。」 「∴ 是 closure relation，但這裡的 frame 不確定。」 「↶ 顯然涉及 nonstandard ordering。」 主持人點頭。 「那 ≡ 呢？」 「看起來是某種 closure-supporting record。」 另一位研究員把順序寫到牆上： object transition closure absent record required record appears later closure established 有人說： 「如果結果先存在，而後面的 record 是 closure 所必需，那結果本身可能形成一種 future obligation。」 另一個人立刻問： 「obligation 是 object 施加的，還是外部 protocol 施加的？」 沒有人回答。 第一個模型被寫下來： Retrocausal command / prophecy fulfillment — 0.55 第二個： Administrative reverse-causal logistics protocol — 0.38 第三個： Timestamp / observation-order artifact — 0.07 一名研究員敲了敲第二行。 「如果 ! 是 institutional requirement，這個其實可以很無聊。」 「多無聊？」 「東西先送，文件後補。」 研究室安靜了兩秒。 有人說： 「那 ↶ 呢？」 「就是一種允許 destination leg 先完成的 service relation。」 主持人看著兩個模型。 「目前 fragment 不夠。」 於是正式報告仍寫： The artifact manifests prior to its causal justification and subsequently necessitates the future production of a validating causal record that retroactively closes its prior appearance. 中文摘要是： 該物件在其因果理由之前先行顯現，隨後迫使未來產生一筆驗證性因果紀錄，以回溯性地閉合其先前出現。 報告提交的時候，真正的弦已經把脆片吃完了。 保溫盒也已經洗好。 沒有物件迫使未來產生原因。 沒有預言完成。 沒有命運閉環。 只有一筆快遞早就送到了。 以及一張表單，比包裹晚幾分鐘才填完。 ## 第16章 · 失物招領裡出現了明天的我 弦只是想回家。 她今天已經處理過一筆會分成兩個明天的找零，也收到黎寄來、比寄件原因更早抵達的脆片。 她覺得今天夠了。 住宅層轉角的 public recovery node 卻亮了一下。 與你的 stable address 有關的 recoverable target：1 弦停住。 看了一眼。 又往前走兩步。 停住。 退回來。 「不要。」 她之前已經看過尚未出生的 branch 想替自己點早餐。 也看過便利商店把找零拆成兩個可能的明天。 那些至少都還有一個優點： 未來待在未來。 現在 recovery node 直接告訴她，有一段和自己明天有關的東西先跑進了今天的服務佇列。 弦抬頭看了看住宅層的時刻板。 她明天早上有一個固定行程。 中午也有。 晚上還借了東西要還。 她對著 recovery node 說： 「我沒有要求明天提前報到。」 系統回： no arrival event recorded. 「那更糟。它連報到都不是。」 工作中的 node 很有耐心地亮著。 弦嘆氣。 「不要。」 系統沒有回應她的願望。 畫面展開。 最上面是一個她很熟悉的 address。 ◒ 下面接著： ⋔ ∷ 合起來： ◒⋔∷ 弦盯著那串東西。 旁邊的 presentation window 裡，也真的有一個很像她的 local state。 不是完整的另一個人。 比較像某個本來應該沿著 future branch 往前 resolve 的 address presentation，在錯的 frame 裡先被顯示出來。 輪廓和她一致。 姿勢卻不完全一致。 弦抬手。 那個 state 沒有跟著她動。 它只是維持在一個「等候被接回 route」的 presentation 裡。 ⟦◬ ◒ ◒⋔∷⟧ ⟦⋈ ◒⋔∷ ◒⟧ ⟦⋈ ◒⋔∷ ⋔⟧ ⟦⌂ ◒⋔∷⟧ 弦看完。 「為什麼我在失物招領？」 旁邊一位正在處理其他 recovery case 的工作員抬頭。 「妳沒有。」 弦指著畫面。 「那個不是我？」 工作員看了一眼。 「跟妳有 stable association。」 「這句話通常不能用來回答『是不是我』。」 「那是妳 future branch 的 address state。」 「所以還是我。」 工作員想了一下。 「可以這樣說。」 弦抱起手。 「我不是失物。」 「妳不是。」 「那為什麼我可以被認領？」 工作員把 target schema 切給她看。 畫面上有三行。 recovery target：future-linked address state recovering participant：N.XIAN owner：not applicable 弦盯著第三行。 「你們甚至有 owner 欄。」 「有些 recovery case 需要。」 「我的不需要？」 「不需要。」 「那為什麼這裡長得像失物招領？」 「因為它就是 recovery service。」 「你們不能取一個不要讓人覺得自己被撿到的名字嗎？」 工作員看了一眼上面的公共標示。 「可以提案。」 弦覺得這句話的意思通常是： 不會改。 她再看一次那個 future-linked state。 「它怎麼跑到這裡的？」 工作員把 route trace 拉出來。 原本應該沿著一條未決 future path 往後 resolve 的 address relation，在住宅層一次 ordinary transition 時被提前綁到 recovery frame。 不是裂縫。 不是危險。 不是誰把未來綁架了。 就只是 routing 不對。 弦沉默幾秒。 「所以是明天的我走丟了。」 「不是完整的明天。」 「明天的一部分走丟了。」 「比較接近。」 弦嘆氣。 「我明天還要上班。」 工作員沒有聽懂這句話和目前 recovery case 的直接關係。 弦補了一句： 「我只是希望我的明天至少先待在明天。」 這句話很合理。 只是系統沒有這個保證。 —— 她點開 recovery action。 畫面跳出： recover target? 弦按下確認。 系統又問： recovering participant? 已經自動帶入： N.XIAN 她看著自己的名字。 「所以我要認領我自己。」 工作員說： 「妳是 recovering participant。」 「那不是同一句話？」 「不是。」 「差在哪？」 「如果妳是 owner，會有 ownership relation。」 「現在沒有？」 「沒有。」 「如果我是 property 呢？」 「target type 也會不同。」 弦看了看。 「所以現在是？」 「address state。」 弦沉默了一下。 「我人生第一次覺得『我不是財產』這句話需要系統證明。」 工作員沒有笑。 可能因為他今天已經聽過更奇怪的。 弦按下 recovery。 ⟦◒ ∶ ⌂ ◒ ◒⋔∷⟧ presentation window 裡，那個 future-linked state 輕微閃了一下。 沒有被吸進弦身體。 沒有合體。 沒有「未來回歸現在」。 它只是從錯誤的 recovery route 轉回正常 association。 ⟦Ϟ ◒⋔∷ ◒⟧ ⟦⊘ ⌂ ◒⋔∷⟧ 列表空了。 旁邊的 schedule preview 自動刷新。 原本那條被標成： route unresolved / recovery pending 的 future-linked entry，現在只剩： route association：normal 弦盯著那行字。 「所以明天現在回明天了？」 工作員說： 「那個 state 回到預期 relation。」 「我問的是明天。」 「妳的明天沒有離開過。」 「可是剛剛有一段在這裡。」 「所以才要 recovery。」 弦覺得這個回答形成了一個非常穩固、但很不令人滿意的圓。 她看著空掉的位置。 「所以我把我自己領回去了。」 工作員說： 「妳把一個與妳相關的 address state 接回正常 route。」 「你們真的很堅持。」 「因為這兩件事不同。」 弦準備走。 走了三步。 又回頭。 「那我明天會記得我今天來領過嗎？」 工作員看了一眼 relation status。 ⟦⌁ ◒⟧ ⟦⋈ ⋔ ◒⟧ 「continuity 正常。」 弦鬆了一口氣。 「好。」 她轉身。 又停。 「如果明天的我明天又來，說她沒有同意被今天的我領走呢？」 工作員沉默。 這次是真的沉默。 弦等了兩秒。 工作員說： 「那會是另一個 case。」 弦點頭。 「我就知道。」 —— 很久以後，H0 研究室取得的資料比弦當時看到的少得多。 他們沒有： owner：not applicable 也沒有： recovery target：address state 沒有 routing trace。 沒有工作員那句： recovering participant 不等於 owner。 他們只有： ⟦◬ ◒ ◒⋔∷⟧ ⟦⌂ ◒⋔∷⟧ ⟦⋈ ◒⋔∷ ◒⟧ 以及稍後： ⟦◒ ∶ ⌂ ◒ ◒⋔∷⟧ ⟦⊘ ⌂ ◒⋔∷⟧ 研究員先把已知關係列出來。 「◒ 是同一個 stable address。」 「⋔ 是 unresolved future branch。」 「∷ 是 manifestation structure。」 「所以 ◒⋔∷ 應該是 future-linked manifestation。」 主持人點頭。 「⌂ 呢？」 「看起來是 claim / recover。」 另一位研究員說： 「target 先被標記為可 claim，後來 current ◒ 又對同一 target 執行 recovery。」 「很像 lost property。」 有人立刻補： 「但 corpus 裡沒有 ownership primitive。」 研究室安靜了一下。 第一個模型被寫下來： Future self as recoverable property — 0.53 第二個： Generic address-state recovery service — 0.41 第三個： Identity duplicate detention / quarantine — 0.06 一名研究員指著第二個模型。 「如果 ⌂ 只表示 recovery relation，那 current ◒ 可能只是合法 recovering participant。」 「不是 owner？」 「不一定。」 「那 target 為什麼能被 claim？」 「因為 addressable，而且走錯 route。」 主持人看著 fragment。 「我們沒有 route metadata。」 「也沒有 property token。」 「所以兩個模型都保留。」 最後正式報告仍寫： A future instance of the subject is detained as lost property and later reclaimed by its present owner-state. 中文摘要： 主體的一個未來實例被作為遺失財產收容，後由其當前所有者狀態取回。 報告送出的時候，真正的弦已經回家。 她把明天的行程重新確認了一遍。 早餐正常。 交通正常。 工作正常。 沒有任何一欄寫： 明日的妳：已由今日的妳持有。 只有 recovery node 的 case history 裡，多了一筆很普通的紀錄： target route restored. 弦不是失物。 明天也不是她的財產。 只是有一段本來應該往明天走的 address state，今天先走錯了路。 ## 第17章 · 住戶大會決議刪除一條走廊 住戶大會開了四十分鐘。 其中二十五分鐘都在討論一條走廊到底算不算「常用」。 那條走廊位於第七居住褶的東側。 從住宅層中段繞過一段維護區，再接到公共轉接廳。 理論上可以少走一點路。 實際上，最近三十個週期裡，大部分住戶都改走另一條比較亮、比較直，而且不會每隔幾天就出現「請勿靠左，左側暫時不是同一個左側」提示的路。 衡把使用資料投到住戶大會中央。 東側 shared passage ordinary transit usage：低 maintenance intervention：偏高 alternate public route：available 坐在後排的黎舉手。 「所以今天是要修它？」 「不是。」 「那是要再貼告示？」 「也不是。」 「那要幹嘛？」 衡把下一頁切出來。 proposal：decommission from ordinary civic reachability 黎看了兩秒。 「你可以說人話。」 坐在另一邊的弦說： 「停用。」 衡點頭。 「對。」 黎立刻懂了。 「那你為什麼不一開始就寫停用？」 「正式議案不是我寫的。」 負責提出議案的住戶在前排抬了一下手。 「是我。」 黎看向他。 「你平常是不是很喜歡寫報告？」 「我負責維護。」 「難怪。」 —— 不是所有人都贊成。 一位住在東側的住戶說： 「我會走那條。」 衡看資料。 「過去三十個週期，十一筆。」 「看吧。」 「其中七筆是妳去看它修好了沒有。」 住戶沉默。 弦低頭笑了一下。 另一位住戶說： 「我支持停用。我上次走那條，出口比入口晚半個維護窗。」 衡說： 「那次已修復。」 「但我不想再確認第二次。」 還有人問： 「停用後要拆嗎？」 「目前沒有拆除案。」 「那留著幹嘛？」 「maintenance access。」 「一般住戶不能走？」 「不能。」 「看得到？」 「看得到。」 「那不就是一條不能走的走廊？」 衡停了一下。 「是。」 會議室安靜了兩秒。 黎說： 「你看，大家都會說人話。」 —— 最後表決通過。 中央畫面顯示： ⟦◬ ◫ ⌇⟧ ⟦⋈ ⌇ ▣⟧ ⟦! ✂ ⌇⟧ 接著： ⟦✂ ⌇⟧ ⟦⊘ ⋈ ⌇ ▣⟧ 住戶介面上的公告卻只有四個字： 刪除走廊 弦看到時抬頭。 「等等。」 衡正準備切下一個議程。 「怎麼了？」 「你們不是說停用嗎？」 「對。」 弦指著公告。 「這裡寫刪除。」 衡看了一眼。 「短標題。」 「短到意思變了。」 「沒有變。」 「『停用走廊』也是四個字。」 衡沉默。 會議室裡有人開始點頭。 提案人說： 「舊介面詞庫。」 黎說： 「所以不是放不下。」 「不是。」 衡把公告備註打開。 裡面寫： remove path from ordinary civic reachability graph 黎看完。 「這個才是真的放不下。」 —— 散會後，弦特地繞去東側。 不是因為她需要走那裡。 純粹是因為她想確認： 一條被刪掉的走廊到底長什麼樣。 她轉過轉角。 走廊還在。 燈還亮著。 牆還是牆。 地面也沒有變成黑洞。 遠處甚至還有一台 maintenance unit 正慢慢沿著牆邊移動。 ⟦◬ ◒ ⌇⟧ 弦站在入口前。 「這不是還在嗎？」 剛好從後面過來的衡說： 「在。」 「那我能走嗎？」 「不能。」 「為什麼？」 「它已經不在 ordinary public route 裡。」 ⟦◒ ∶ Ϟ ⌇ ?⟧ ⟦◫ ∶ ⊘ Ϟ ⌇⟧ 弦往前伸了一隻腳。 入口沒有牆。 也沒有門。 但 public transition layer 沒有接住她的下一步。 她的腳仍然能踩在入口範圍。 再往前時，路由提示只顯示： no ordinary resident transition relation 弦把腳收回來。 「很怪。」 「哪裡？」 「我看得到一條路，但它不是路。」 「它是 path-like structure。」 「這句更怪。」 「對 maintenance frame 來說，它還是 path。」 「對我呢？」 「不是公共 route。」 弦轉頭看他。 「你們真的很喜歡把同一個東西分成很多 relation。」 衡說： 「不分的話，剛剛妳會問為什麼走廊消失了。」 「現在我也在問。」 「但它沒有消失。」 「所以我才問。」 衡沒有回答。 因為這個對話已經開始形成一個熟悉的圓。 —— 弦又看了一眼公告。 「所以『刪除走廊』真正刪掉的是什麼？」 ⟦◒ ∶ ✂ ⌇ ?⟧ 衡指了指 routing status。 ⟦◫ ∶ ⊘ ⋈ ⌇ ▣⟧ 「它和公共可達圖的 ordinary association。」 「不是走廊。」 「對。」 「那你們標題就是錯的。」 「是 resident-facing shorthand。」 「你剛才不是還說沒有變？」 衡看著她。 「現在我承認有壓縮。」 弦點頭。 「很好。」 「但議案本身沒錯。」 「我知道。」 「所以？」 「所以我只是在確認今天被刪掉的是走廊，還是你們的字數。」 衡沒有回這句。 —— 大會最後一個議程其實還有一則通知。 先前外借的公共 cycle slot 預計稍後返還。 返還後需完成 local compatibility check，才會重新加入 active schedule。 弦看到那一行時停了半秒。 「是不是星期三？」 衡說： 「等回來再看。」 弦立刻有不好的預感。 「你這句話聽起來就代表回來以後還有事。」 「有可能。」 「我可以投票不要嗎？」 「不是這個議程。」 弦覺得住戶自治的自由度非常有選擇性。 —— 很久以後，H0 研究室拿到的是另一種版本。 他們沒有住戶大會裡那二十五分鐘「到底算不算常用」的爭論。 沒有東側住戶那十一筆使用紀錄。 沒有「其中七次只是去看修好了沒有」。 也沒有弦站在一條明明看得到、但不能再當公共 route 使用的走廊前面問： 「到底刪了哪裡？」 他們只有： ⟦! ✂ ⌇⟧ ⟦✂ ⌇⟧ ⟦⊘ ⋈ ⌇ ▣⟧ ⟦⊘ Ϟ ⌇⟧ 研究員把已知項列出來。 「! 是 civic authorization。」 「⌇ 是 shared passage。」 「✂ 對 path 生效。」 「之後它和 dwelling reachability 的 association 被移除。」 「resident transition 也被排除。」 主持人問： 「所以 operation 是什麼？」 有人在板上寫： graph edge removal 另一個人補： topological excision 第三個人說： 「如果它真的只是 municipal decommissioning 呢？」 研究室停了一下。 第一位研究員說： 「形式上也是 edge removal。」 「對。」 「所以 topological excision 不能算錯。」 「我沒說錯。我說是不是太重。」 最後三個模型被保留： Civic topological excision rite — 0.66 Municipal route decommissioning protocol — 0.29 Physical corridor annihilation — 0.05 第三個幾乎沒人支持。 因為他們另外還有一條 operation 後的 observation： ⟦◬ ◒ ⌇⟧ 走廊顯然還能被看見。 爭議只剩： 一個從公共路由圖移除 path 的 civic operation，到底應該叫什麼。 最後正式報告寫： The civic body authorizes a topological excision of an inhabited transit segment, severing it from the shared reachability manifold. 中文摘要： 公民共同體授權對一段有人居空間進行拓樸切除，使其自共享可達流形中斷離。 報告寫完時，第七居住褶的住戶已經開始習慣走另一條路。 沒有人舉行儀式。 沒有人切開時空。 沒有人站在走廊前為失去的流形默哀。 只有入口旁多了一塊很普通的提示： 此 route 已停用。請由西側通道通行。 以及介面深處那個仍然很不普通的舊標題： 刪除走廊 ## 第18章 · 星期三還回來了，但版本不對 星期三回來的時候，弦第一個看到。 她原本只是經過公共 schedule board。 沒有特別等。 至少她自己是這樣認為的。 畫面最上方原本一直空著的那一格，忽然亮了。 ⟦Ϟ ⌖≋ ▣⟧ 下面跳出一行： displaced public cycle slot：returned 弦停住。 又靠近一步。 那個位置她已經看過太多次了。 EP006 之後，第七居住褶的星期三被借走，大家雖然還是照常生活，但很多事情都變得很煩。 某些服務把星期二延長。 某些店家直接把「週三限定」改成「等星期三回來再說」。 垃圾處理時段還一度因為沒有星期三而重新排序。 弦最討厭的是： 行程表看起來永遠像少一格。 現在那一格回來了。 她盯著它兩秒。 「回來了。」 旁邊一位正在更新住宅層公告的住戶也抬頭。 「真的？」 「嗯。」 弦難得笑得很明顯。 她立刻打開自己的 schedule，準備把原本被迫挪到其他 cycle slot 的固定行程接回去。 介面跳出： version mismatch 弦的笑停住。 她看著那四個字。 又看了一眼星期三。 「不。」 系統沒有理她。 弦伸手點那一格。 ⟦◬ ◒ ⌖≋⟧ ⟦⋈ ⌖≋ ⌖⟧ identity check： calendrical identity：recognized 她鬆了一點。 下一行： active local compatibility：failed 弦又不鬆了。 —— 衡過來的時候，弦已經站在 schedule board 前看了快五分鐘。 「怎麼了？」 弦指著那一格。 「星期三回來了。」 「嗯。」 「它說版本不對。」 「嗯。」 弦轉頭。 「你為什麼可以連續兩次用『嗯』回答這種事？」 衡看了一眼 metadata。 「因為兩件事都是真的。」 「哪兩件？」 「星期三回來了。」 「對。」 「版本不對。」 「我知道。」 「那妳問什麼？」 弦閉上眼睛。 「我問的是，星期三為什麼會有版本。」 衡看著她。 「因為是 versioned temporal segment。」 弦睜開眼。 「說人話。」 「借出去的時候，local schedule 還是舊狀態。」 「所以？」 「它回來時帶的是離開期間累積的 version state。」 「所以它真的是星期三？」 「是。」 「不是別的時間片段？」 「不是。」 「不是平行宇宙星期三？」 「沒有 evidence。」 「不是我哪一個未來 branch 的星期三？」 「也沒有 evidence。」 弦點頭。 「很好。」 停了一秒。 「那為什麼不能用？」 衡把下一層狀態打開。 ⟦⊘ ⋈ ⌖≋ ▣⟧ identity association：valid active schedule association：withheld reason：version reconciliation pending 弦盯著它。 「所以它是星期三。」 「對。」 「只是現在不能當星期三用。」 「暫時不能。」 「你有沒有覺得這句話本身很有問題？」 「沒有。」 「我有。」 —— 問題不只弦有。 住宅層很快開始出現很普通的抱怨。 早餐店把本來準備恢復的「週三第二份折扣」先撤回。 公共洗滌站顯示： Wednesday schedule detected service activation pending 一位住戶站在機器前問： 「那我今天到底算不算週三？」 系統回答： calendrical identity recognized service compatibility pending 住戶轉頭問衡： 「這算人話嗎？」 衡說： 「不太算。」 弦站在旁邊，立刻說： 「你終於承認了。」 另一個住戶更在乎垃圾分類。 「我原本週三要丟那批會在週四之前失去 stable association 的東西。」 衡說： 「今天先按 reconciliation fallback window。」 「所以星期三回來了，但垃圾還不能照星期三丟？」 「對。」 「那它回來幹嘛？」 衡沒有回答。 因為這句話顯然不是技術問題。 —— reconciliation 被排進當天。 沒有儀式。 沒有時間風暴。 沒有城市一半消失。 只有 schedule board 旁多了一個很像系統更新的進度條。 comparing returned version with local active schedule rebuilding closure-support record service mappings pending 弦站在前面看。 「要多久？」 「不確定。」 「你剛才不是說很正常？」 「正常不代表快。」 「這句我討厭。」 「很多人都討厭。」 衡看了一眼新的 metadata。 「需要補 closure-support record。」 ⟦≡ ⌖≋⟧ 弦看到 ≡，皺眉。 「又是這個。」 「妳認得？」 「逆因果快遞那次，黎不是才被逼著補文件？」 「同一個 root，不同 frame。」 「所以星期三回來也要補文件。」 「不是文件本身。是足以支援 schedule closure 的 record。」 弦看著他。 「你們真的很喜歡讓任何事情最後都變成可以稽核。」 衡沒有否認。 —— 更新到一半時，schedule board 跳出一則提示： conflict：one resident booking references current local Wednesday mapping 弦低頭。 那是她的。 她之前把一個固定會面改到「星期三回來後第一個可用 Wednesday slot」。 現在系統不知道： returned Wednesday 和： local expected Wednesday 是否已經能視為同一個 active version。 弦說： 「是我。」 衡說： 「看到了。」 「所以現在卡住是因為我？」 「不是。妳只是第一個實際踩到 compatibility check。」 「這有比較好嗎？」 「有。」 「哪裡？」 「不是妳造成的。」 弦想了一下。 「好吧，這確實有比較好。」 —— 一段時間後，系統開始 transition。 ⟦Ϟ ⌖≋ ▣⟧ returned version 的 service mappings 一條一條重新接回。 早餐店的週三折扣亮了。 洗滌站的 Wednesday schedule 從 pending 變 active。 垃圾分類時段重新出現在公共板上。 最後： ⟦∴ ⌖≋ ▣⟧ ⟦⋈ ⌖ ▣⟧ board 顯示： schedule closure：complete active calendrical association：restored 弦盯著那兩行。 「所以星期三真的回來了？」 衡說： 「回來了。」 「現在能用？」 「能。」 「版本呢？」 「已 reconciled。」 弦想了一下。 「所以借出去的星期三回來，要先更新。」 衡停了一秒。 「可以這樣說。」 弦點頭。 「早點這樣說就好了。」 —— 她把自己的固定行程拖回星期三。 這次沒有錯。 早餐店也恢復週三活動。 垃圾分類時段回到原來的位置。 那個曾經少了一格的 schedule 終於重新完整。 弦看了一會兒。 她其實知道： 星期三只是一個 public calendrical slot。 不是某個有意志的朋友。 也不是失散多年的東西。 但她還是低聲說： 「總算。」 衡站在旁邊。 「妳很在意星期三。」 「我在意行程不要一直動。」 「這比較合理。」 「我一直都很合理。」 衡沒有評論。 —— 很久以後，研究室也看到了一個「版本不對的星期三」。 但這次，他們沒有立刻寫： alternate timeline intrusion 也沒有先寫： parallel calendrical entity replacement 一名研究員把 fragment 放到牆上。 ⟦Ϟ ⌖≋ ▣⟧ ⟦◬ ◒ ⌖≋⟧ ⟦⋈ ⌖≋ ⌖⟧ ⟦⊘ ⋈ ⌖≋ ▣⟧ 有人說： 「returned segment 和 known calendrical identity 的 association 成立。」 另一個人說： 「但 active local schedule association 被排除。」 主持人問： 「以前我們會怎麼寫？」 有人笑了一下。 「平行時間片段入侵。」 「現在呢？」 研究員翻出前幾回的修正記錄。 EP013： low-order death 後來越看越像： reversible dormancy。 EP014： furnishing transformation 後來更像： classification。 EP015： retrocausal command artifact 後來更像： reverse-causal logistics protocol。 EP016： recoverable property 後來更像： generic address-state recovery。 EP017： civic topological excision rite 後來大家承認： municipal route decommissioning 比較像人話。 研究室安靜了一會兒。 主持人說： 「這次先不要替它加戲。」 於是第一個模型寫成： Versioned temporal-segment return requiring reconciliation — 0.78 第二個： Alternate timeline intrusion — 0.13 第三個： Future-branch replacement — 0.09 有人問： 「我們是不是變保守了？」 主持人說： 「我們是開始記得自己以前錯在哪。」 —— 之後，他們正式發出： Translation Model Revision Notice — R1 第一條寫： Longitudinal relational consistency is given greater evidential weight than isolated dramatic interpretations. 有人把它翻成比較普通的話： 如果很多回裡同一種 relation 都一直這樣運作，就不要因為某一回看起來很嚇人，馬上假設那次突然變成宇宙末日。 主持人說： 「這句不要放正式版。」 「為什麼？」 「太像人話。」 研究室笑了一下。 但方法真的改了。 他們回頭修正前五回： 午休，不再優先叫低階死亡。 家具，不再優先叫本體轉化。 逆因果快遞，不再優先叫命運物件。 失物招領，不再優先叫所有權回收。 刪走廊，也不再優先叫拓樸切除儀式。 不是因為那些舊模型全都荒謬。 而是因為： corpus 變多了。 很多一開始像宇宙恐怖的東西，放回更長的 relation history 裡之後，看起來只是這個世界自己的日常制度。 —— 正式報告最後寫： A previously displaced calendrical segment returns in a version state inconsistent with the current local schedule and is withheld from active scheduling pending reconciliation. 中文摘要： 先前脫離的曆制片段以與目前本地排程不一致的版本狀態返回，並在 reconciliation 完成前暫不重新納入 active schedule。 這次沒有「時間裂界」。 沒有「替代宇宙侵入」。 沒有「曆制人格回歸」。 只有： 星期三回來了。 以及： 回來後要先更新。 Act III 到這裡結束。 而研究組第一次真正開始懷疑： 有時候不是外側文明太可怕。 是翻譯者太習慣把陌生東西翻得可怕。 ## 第19章 · 多出來的第三個觀察槽位 星期三恢復正常後的第一個早晨，衡在做例行檢查。 不是因為出了事。 恰恰相反。 就是因為前幾天事情有點多，所以他想確認住宅層所有常用 relation 都已經回到正常狀態。 星期三： active。 東側走廊： decommissioned as planned。 public observation stabilization： normal。 shared schedule： closed。 衡一項一項往下看。 前面都很無聊。 這很好。 管理工作最好的狀態就是： 無聊。 他打開 dwelling validation。 第一筆 observation： ⟦◬ ◫ ▣⟧ 正常。 observer： 衡。 target： dwelling frame。 結束。 衡按下一筆。 畫面多了一格。 ⟦◬³ ◫ ▣ ?⟧ 衡停住。 不是因為它亮紅燈。 它沒有。 沒有 warning。 沒有 hazard marker。 甚至沒有 error code。 它只是比平常多一格。 第三格是： ? 衡盯了兩秒。 按重跑。 ⟦◬ ◫ ▣⟧ ⟦◬³ ◫ ▣ ?⟧ ⟦⧈ ◬³ ▣ ?⟧ 還在。 他又跑一次。 還在。 —— 衡先做最普通的事。 關掉 validation panel。 重開。 還在。 換 measurement window。 還在。 把上一筆 cache 清掉。 還在。 他看了一眼系統狀態。 observation stabilization：normal resolver service：normal dwelling frame：stable unknown structural position：present 衡皺眉。 最後那一行以前沒有。 他沒有立刻叫人。 先把整套流程重跑第二次。 結果一樣。 ordinary observation 正常。 three-slot observation 也正常。 只有 third binding： unresolved。 這種時候最麻煩的不是系統報錯。 而是： 系統看起來很確定自己沒報錯。 —— 弦被叫來時，手上還拿著剛買的早餐。 「怎麼了？」 衡指著 validation panel。 「看一下。」 弦看了一眼。 「看什麼？」 「妳自己做一次 observation。」 「為什麼？」 「確認。」 「確認什麼？」 「做完再說。」 弦很不喜歡這種回答。 但她還是站到 validation node 前。 第一筆： ⟦◬ ◒ ▣⟧ 正常。 第二筆： ⟦◬³ ◒ ▣ ?⟧ 弦停住。 「多一格。」 「嗯。」 「這是什麼？」 「不知道。」 「你找我來以前就不知道？」 「對。」 「那你至少可以先說『不知道』。」 「我現在說了。」 弦看著那個第三格。 它沒有內容。 但也不是空白。 介面很明確地保留了一個 slot。 旁邊還有 measurement： ⟦⧈ ◬³ ▣ ?⟧ structural position：confirmed binding：unresolved 弦慢慢把早餐放到旁邊。 「所以多一個人在看？」 衡說： 「不一定。」 「那第三格是誰？」 「不知道。」 「那你知道什麼？」 「它以前沒有。」 弦看著他。 「這句話有點可怕。」 「只是描述。」 「描述本身就有點可怕。」 「可以。」 「所以你也覺得可怕？」 「我沒有說。」 —— 衡把兩組結果並排。 左邊： observer = N.HENG 右邊： observer = N.XIAN 第三格都存在。 第三格都 unresolved。 弦指著兩邊。 「所以不是你的問題。」 「至少不是只跟我有關。」 「也不是我的問題。」 「至少不是只跟妳有關。」 「你可以一次把整句說完嗎？」 衡想了一下。 「third-slot pattern survives observer change。」 弦沉默。 「還不如不要。」 —— 他們又換了一個普通 observation target。 結果 ordinary relation 正常。 但 dwelling validation frame 裡，third position 又出現。 衡把它記進 log。 弦問： 「會不會是星期三更新完留下來的？」 「沒有 evidence。」 「東側走廊？」 「沒有 evidence。」 「黎的逆因果快遞？」 「沒有 evidence。」 「我前幾天走丟的明天？」 「也沒有 evidence。」 弦一口氣把最近發生過的事都問了一遍。 衡每次都回答： 「沒有 evidence。」 最後弦說： 「你這句最近變多了。」 「R1 之後應該變多。」 「人類研究組更新方法，你也跟著更新？」 「那個方法本來就合理。」 弦想了一下。 「好吧。」 —— 衡接著試 local exclusion。 不是刪掉 relation。 只是把這個 extra structure 暫時排除出目前 validation frame，看它是不是某個附加 layer。 ⟦◫ ∶ ⊘ ◬³ ▣ ?⟧ 系統接受操作。 下一次 observation： ⟦◬³ ◫ ▣ ?⟧ 第三格還在。 弦看著畫面。 「所以趕不走。」 「目前不能這樣說。」 「你剛剛不是排除了嗎？」 「排除的是 local relation instance。」 「然後？」 「新的 instance 又出現。」 弦更不喜歡這個答案。 「這有比較好嗎？」 「比較精確。」 「我問的是比較好嗎？」 「沒有。」 至少這次衡回答得很快。 —— validation record 開始出現一個很煩的小問題。 以前表格是： observer target result 現在多一欄： witness / validation binding 狀態： unresolved 整張表其他部分都能結束。 只有這一欄一直掛著。 弦說： 「所以我們現在最大的問題，是表格多一格填不完？」 「目前 operationally，是。」 「不是有東西在看我們？」 「不知道。」 「不是世界外面有誰？」 「不知道。」 「不是未來的我們？」 「不知道。」 「不是讀……」 衡抬頭。 「妳要說什麼？」 弦停了一下。 「沒什麼。」 她自己也不知道剛才為什麼差點冒出一個奇怪的詞。 衡沒有追問。 —— 黎剛好經過時，看見兩個人站在 panel 前。 「壞了？」 弦說： 「多一格。」 黎看了一眼。 「哪一格？」 弦指給她看。 黎盯了三秒。 「誰的？」 衡說： 「不知道。」 黎又看三秒。 「危險嗎？」 衡說： 「目前不知道。」 黎點頭。 「那我先走了。」 弦轉頭。 「妳就這樣？」 「不然呢？」 「妳不好奇？」 「好奇。」 「那妳怎麼走了？」 黎說： 「好奇不影響我去拿午餐。」 然後真的走了。 弦看著她離開。 「她有時候很合理。」 衡說： 「大部分人餓的時候都會變合理。」 —— 衡最後把事件狀態設成： STRUCTURE CONFIRMED / BINDING UNRESOLVED 沒有 hazard marker。 沒有 evacuation。 沒有把 dwelling 關掉。 也沒有公告「未知存在正在凝視住戶」。 弦看著那行字。 「就這樣？」 「先這樣。」 「如果它明天還在？」 「繼續量。」 「後天呢？」 「繼續量。」 「一週呢？」 「建立 longitudinal record。」 弦嘆氣。 「第四幕開始就不能給我一個比較像答案的東西嗎？」 衡看著她。 「不知道本身也是答案。」 弦皺眉。 「這句很像研究員會講的話。」 「因為是。」 —— 很久以後，H1 研究組拿到這份資料。 如果是 Act III 以前，他們可能已經寫出： trans-dimensional witness intrusion 或： nonlocal observer entity 甚至更糟。 但 R1 已經存在。 所以研究員先把兩件事分開。 第一件： third slot 是否真的存在？ 第二件： third slot 是誰／什麼？ 第一個問題的 confidence 很高。 因為： • repeated； • cross-observer； • measurable； • structurally stable。 第二個問題很低。 因為： • no identity binding； • no personhood evidence； • no hazard marker； • no causal relation； • no provenance。 研究室最後寫： Structural confidence — 0.86 / high Binding-identity confidence — 0.18 / low 有人問： 「要不要叫 external witness？」 主持人說： 「可以當 model，不要當 identity。」 「higher-dimensional observer？」 「evidence 不夠。」 「hidden person？」 「evidence 不夠。」 「system bug？」 「還不能排除，但 repeated cross-observer 讓它不是第一順位。」 最後模型排序是： Protocol / grammar extension — 0.36 External validation anchor — 0.28 Observer-frame artifact — 0.20 Genuinely external witness — 0.12 Instrumentation fault — 0.04 沒有人把「神」放進表格。 不是因為他們確定沒有。 而是因為： slot existence 有 evidence。 神沒有。 —— 第七居住褶那邊，第三格到了晚上還在。 弦回家前又看了一次。 「還是問號。」 衡說： 「嗯。」 「你現在真的完全不猜？」 「我有 hypotheses。」 「那為什麼不說？」 「因為妳問的是答案。」 弦站了一會兒。 最後點頭。 「好。」 她轉身去搭電梯。 走了兩步，又回頭。 「如果明天它變成四格呢？」 衡第一次停得比平常久。 「那明天再開一張表。」 弦笑了。 「這個世界有時候真的很欠揍。」 第三格沒有回應。 因為至少目前，沒有人知道它能不能回應。 ## 第20章 · 管理員第一次承認「這次有點嚴重」 最先發現問題的是弦。 她只是要接水。 星期三已經回來。 行程也恢復。 早餐店的折扣正常。 洗滌站正常。 垃圾分類時段也正常。 弦覺得生活終於重新變得像一個可以照表走的東西。 然後她把杯子放到水槽裡。 按下出水。 水出來了。 只是不是從出水口。 第一股水從水槽右邊大約半個身位的位置直接落下來。 很乾淨。 很穩定。 也很準確地沒有落進杯子。 弦站著看了兩秒。 水停了。 她把杯子往右移。 再按一次。 這次水從正常出口出來。 整杯接滿。 弦盯著水龍頭。 「……好。」 她把杯子放回原本的位置。 第三次按下。 水從牆邊出來。 —— 第三次比較麻煩。 因為牆邊沒有水槽。 水沿著地面流開。 罅原本正趴在門口。 看到地上的水，立刻站起來。 牠先追到牆邊。 水停。 下一股又從水槽旁出來。 罅轉身追。 又停。 第三股從另一側冒出來。 罅停在房間中央。 看了左邊。 看了右邊。 最後抬頭看弦。 弦說： 「不要問我。」 罅沒有問。 牠只是選了一塊看起來最有可能下一次出水的位置坐下。 弦看著牠。 「你最好不要比系統先猜對。」 —— 她先關掉 local resource request。 水停了。 這至少很好。 然後她重新開一次。 正常。 再開一次。 不正常。 弦拿出終端，拍下位置紀錄。 她本來想先報： 水管問題。 填到一半又停住。 因為如果只是水管，水應該至少從某個和管線有關的位置出來。 剛才牆邊那一下不太像。 她改成： shared resource output position inconsistent. 系統回： submit maintenance observation? 弦按了。 兩分鐘後，衡到了。 —— 衡第一件事不是看牆。 是看紀錄。 第二件事才是看牆。 「再一次。」 弦按下出水。 正常。 衡說： 「再一次。」 還是正常。 弦看他。 「你一來它就裝正常。」 「再一次。」 第三次，水從水槽外側二十多公分的位置出來。 衡沒有說話。 他把 measurement window 拉出來。 ⟦◬ ◫ □ ▣⟧ ⟦⧈ □ ▣⟧ ⟦⋈ □ ▣⟧ 第一段 baseline： resource observable expected output relation：valid dwelling association：valid 衡記下。 再開一次。 水往左偏。 ⟦Ϟ □ ▣⟧ ⟦⊘ ⧈ □ ▣⟧ ⟦⊘ ⋈ □ ▣⟧ 弦看著 measurement。 「水管歪了？」 衡沒有回答。 「不是嗎？」 「先別命名。」 「你最近真的很喜歡這句。」 「有用。」 —— 衡把 observation stabilization service 拉出來。 弦立刻看懂。 「你在查是不是又像上次停電？」 「嗯。」 EP012 那次，很多東西看起來像世界壞了。 後來只是 observation stabilization 掉線。 衡重新觀察 S03。 ⟦◬ ◫ ◌ ▣⟧ ⟦⋈ ◌ ▣⟧ 狀態： stabilization service：normal frame association：normal 弦盯著那兩行。 「所以不是停電。」 「不是。」 「那有可能只是顯示錯？」 「現在比較不像。」 「為什麼？」 衡指向地上的水。 「妳鞋濕了。」 弦低頭。 鞋真的濕了。 這個證據很普通。 也很有說服力。 —— 這時析剛好放學回來。 她走進門，看見地上三塊不同方向的積水。 又看見衡蹲在水槽旁。 「今天作業是水嗎？」 弦說： 「不是。」 析把書包放好。 「那我可以量嗎？」 衡說： 「先不要進 affected area。」 析停住。 她其實很少聽到衡用這種語氣。 不是生氣。 只是沒有討價還價空間。 她很自動地退回門邊。 「真的有問題？」 衡說： 「還在確認。」 析點頭。 「那我去黎那邊寫作業。」 弦說： 「很好。」 析走了兩步，又指著罅。 「牠呢？」 罅還坐在房間中央，像一個正在等待下一個出水點的專業預測員。 衡說： 「一起帶走。」 罅不想走。 因為下一股水真的從牠前面冒了出來。 牠立刻低頭。 衡比牠更快，把牠整隻抱走。 罅在半空中轉頭看水。 看起來很不滿。 弦說： 「這次別讓牠參與測試。」 「我本來就沒打算。」 —— 衡做完自己的 observation 後，把 observer position 讓給弦。 「妳來。」 「剛才不是我先看到的？」 「我要同一 protocol。」 弦照做。 第一筆正常。 第二筆 water arrival 往右漂。 measurement out of window。 第三筆 stable association 短暫掉出 expected dwelling relation。 ⟦◬ ◒ □ ▣⟧ ⟦⊘ ⧈ □ ▣⟧ ⟦⊘ ⋈ □ ▣⟧ 弦抬頭。 「所以不是你看錯。」 「對。」 「也不是我看錯。」 「對。」 「也不是觀察服務壞掉。」 「目前 evidence 不支持。」 「那只是水管歪了？」 衡看了她一眼。 「如果只是水管就好了。」 弦沒立刻回話。 她知道這句和前面的「不知道」不一樣。 —— 他們把 affected output 暫時關掉。 啟用另一個 local water source。 地上的水先由 maintenance capture 收走。 公共 notice 只寫： 本層部分 shared resource output 暫停使用。請使用替代供應點。 沒有寫： 時空正在崩潰。 沒有寫： 不明存在入侵。 甚至沒有寫： 結構性危險。 因為衡還沒掛那個標記。 弦問： 「你還不打算標 hazard？」 「還差一次。」 「差什麼？」 「確認它不是單次 structural slip。」 弦看著他。 「已經三次了。」 「前面幾次不是同一 observation protocol。」 「你們行政人員真的很會讓危險先排隊。」 衡說： 「至少這樣不會每個怪東西都變 hazard。」 弦想起昨天那個第三觀察槽位。 「好吧。」 這一次她沒有反駁。 —— 他們等了七分鐘。 alternate source 正常。 affected relation 暫停。 衡開一個 controlled test。 只給最低 output。 第一秒，正常。 第二秒，正常。 第三秒，resource arrival position 往外跳。 不是幾公分。 是整個脫離原本 admissible window。 ⟦Ϟ □ ▣⟧ ⟦⊘ ⧈ □ ▣⟧ 衡盯著 measurement。 這一次，他沒有再重跑第四次。 他打開 maintenance record。 新增一個標記。 ⟦⟁ □ ▣⟧ 弦看見那個符號。 她先看符號。 再看衡。 「這次真的算危險？」 ⟦◒ ∶ ⟁ □ ▣ ?⟧ 衡說： 「算。」 「你確定？」 ⟦◫ ∶ ⟁ □ ▣⟧ 「確定。」 弦沉默了兩秒。 她其實已經看過很多看起來比這個更像世界末日的東西。 停電時，人的局部 presentation 會怪得像被刪掉。 星期三能被借走。 明天會跑進失物招領。 昨天才剛多了一個不知道要填誰的 observation slot。 那些衡都沒有叫 hazard。 所以她問： 「嚴重嗎？」 衡看了一眼 repeated measurement。 又看 resource association log。 再看 stabilization status。 最後說： 「這次有點嚴重。」 弦整個人安靜了。 不是因為「嚴重」兩個字。 是因為這句是衡說的。 —— 衡立刻掛 intervention requirement。 ⟦! ⟁ □ ▣⟧ affected output 全部 exclusion。 alternate water route 擴大。 maintenance capture 改成 continuous。 住宅層發出簡短通知： shared resource relation under maintenance affected outputs unavailable use alternate points source localization in progress 弦問： 「要撤離嗎？」 「目前不用。」 「會停水嗎？」 「替代 route 夠。」 「會擴大嗎？」 「不知道。」 「第三個觀察槽位呢？」 衡抬頭看她。 「什麼？」 「昨天那個。」 「還在 log 裡。」 「和這個有關嗎？」 「沒有 evidence。」 「可是時間很近。」 「時間很近不是原因。」 弦點頭。 「R1。」 「對。」 「我開始討厭這個方法，因為它老是讓答案變成『還不知道』。」 衡說： 「比亂知道好。」 這句話很難反駁。 —— 晚一點，析從黎那邊傳訊息回來。 水修好了嗎？ 弦回： 還沒。 析： 世界還在嗎？ 弦看了一眼屋子。 牆在。 地板在。 星期三也在。 她回： 還在。 析： 那我晚點回去。 弦想了想，又補： 先別用原本那個水槽。 析回了一個： 好。 沒有恐慌。 沒有告別。 只是今晚刷牙換地方。 —— 很久以後，H1 研究組取得這組資料。 他們先把 EP019 放在旁邊。 不是連起來。 是刻意分開。 主持人說： 「先問 hazard 是否成立。」 研究員列出： • repeated drift； • out-of-window measurement； • intermittent resource / dwelling association loss； • cross-observer reproduction； • S03 normal； • intervention requirement。 第一個問題很快收斂： Hazard-structure confidence：0.91 / high 接著才問： cause 是什麼？ 模型排序： Shared resource-fold structural drift — 0.47 Boundary-layer degradation — 0.26 Local routing defect — 0.13 Coupling to EP019 witness-slot anomaly — 0.10 Instrumentation artifact — 0.04 有人問： 「第三槽位昨天才出現，真的完全不加權？」 主持人說： 「加。」 「那為什麼只有 0.10？」 「因為 temporal adjacency 是 evidence，但不是 causal relation。」 「所以 causal-link confidence？」 「0.14。」 研究員把它寫進報告。 不是零。 也遠遠不是結論。 R1 還在。 —— 正式研究摘要最後寫： Persistent cross-observer instability has been confirmed in a shared resource relation. Unlike the earlier observation-slot anomaly, this event satisfies the native structural-hazard marker ⟁. 而第七居住褶那邊，衡已經沿著 resource trace 往更上游查。 本地 outlet 不是原因。 observation stabilization 不是原因。 普通 route defect 也開始不太像。 trace 有一段，正往 ordinary local distribution map 之外延伸。 弦站在旁邊。 「找到了嗎？」 「還沒。」 「那你現在知道什麼？」 衡看著 source trace。 「知道問題不是只在這個水槽。」 弦不太喜歡這句。 但她現在已經知道： 不喜歡答案，和答案有沒有 evidence，是兩回事。 而真正的來源，要到下一步才會被定位。 ## 第21章 · 宇宙邊界正在漏水 第二天，水還在漏。 不是同一個水槽。 因為那個水槽昨天已經被衡停用了。 affected output 被 exclusion。 替代供應點正常。 地板也已經乾了。 照理說，問題如果只在本地 outlet，故事應該到這裡結束。 但 maintenance trace 沒有結束。 衡一早就把昨天那條 resource relation 拉回來。 第一段很好理解。 住宅內。 第二段也還正常。 shared resource fold。 第三段開始變得討厭。 它沒有接回任何已知 local upstream source。 衡把 route map 放大。 再放大。 那條 relation 在地圖上不是： 走錯。 比較像： 從一個原本沒有入口的位置進來。 —— 弦過來時，衡已經坐在 maintenance panel 前很久了。 「還沒找到？」 「找到一部分。」 「水管？」 「不是。」 「shared route？」 「不是主要來源。」 「那是什麼？」 衡沒回答。 他把昨天那段 drift 疊上今天的 source trace。 ⟦⟁ □ ▣⟧ ⟦◬ ◫ □ ▣⟧ ⟦⧈ □ ▣⟧ hazard 還在。 measurement 也還在。 但這次他看的不是： 水從哪裡出來。 而是： 水從哪裡進來。 「這一段。」衡說。 弦靠近。 圖上有一條 relation 從 local distribution map 的邊緣穿進來。 沒有 upstream node。 沒有 ordinary civic route。 甚至沒有一條可追到本地 source registry 的 association。 弦看了一會兒。 「圖壞了？」 「沒有。」 「怎麼知道？」 「其他 relation 都閉合。」 「只有這條沒有？」 「它有閉合。」 弦皺眉。 「閉合到哪？」 衡把另一層 map 打開。 那不是住宅 map。 也不是 shared resource map。 更像整個第七居住褶和外部 frame 之間的 maintenance interface。 弦看懂了一半。 然後決定先不要看懂另一半。 「這是什麼？」 「interface map。」 「哪個 interface？」 衡把 trace 對齊。 ⟦Ϟ □ ≀⟧ ⟦◬ ◫ ≀ □⟧ 弦看著新出現的符號。 「這不是昨天的。」 「不是。」 「所以今天又多一個。」 「這個不是 unknown slot。」 「你知道它是什麼？」 「知道。」 弦突然不太確定這是不是好消息。 —— 衡先做 local shutoff test。 affected dwelling supply： off。 shared resource request： off。 local upstream pull： zero。 然後 interface-side measurement： nonzero。 弦看著結果。 「等等。」 她指著 local supply status。 「這邊明明關了。」 「對。」 「那為什麼還有水 relation？」 「因為不是從這邊來的。」 弦沉默。 「這句話我不喜歡。」 「我知道。」 衡把 incoming trace 再縮小。 relation 穿過一個原本應維持 separation 的 interface layer。 那裡的 association status 顯示： ⟦⊘ ⋈ ≀ ▣⟧ expected isolation： incomplete。 弦盯了很久。 「所以是邊界漏？」 衡說： 「對。」 「哪個邊界？」 「local-world interface。」 弦停了一下。 她其實有很多問題。 但第一個跑出來的還是最簡單的。 「宇宙邊界？」 衡看了她一眼。 「可以這樣說。」 弦又看了一眼正在跨 interface 出現的 resource trace。 「宇宙邊界在漏水？」 「現在是。」 弦沉默了四秒。 「這句話是不是比『這次有點嚴重』更嚴重？」 「不一定。」 「哪裡不一定？」 「昨天是 hazard classification。」 「今天呢？」 「mechanism localization。」 「所以知道宇宙邊界在漏，反而沒有昨天更嚴重？」 「severity 沒因為名字變大。」 弦覺得這是一句很典型的衡式回答。 而且偏偏有道理。 —— 真正的問題是： 這不是本地這邊的水。 弦第一次聽到這句時，以為衡只是在講來源。 後來才知道他真的非常字面。 他們把本地供應全關了。 interface crossing 還在。 把 shared fold 上游暫停。 還在。 把 affected dwelling relation isolation 拉高。 還在。 incoming resource 的 chemical / local-state profile 也不完全符合第七居住褶目前使用的供應規格。 它很像水。 可以被接住。 可以被量。 但 provenance 不屬於本地 registry。 弦問： 「那這是哪裡的水？」 「不知道。」 「隔壁 fold？」 「有可能。」 「更遠？」 「也有可能。」 「別的 world？」 「model 還沒收斂。」 「所以你知道宇宙邊界漏了，但不知道漏進來的是哪個宇宙的水？」 衡說： 「大致上。」 弦慢慢坐下。 「昨天比較好。」 —— maintenance team 很快把 interface-side capture 拉起來。 不是拿大桶子。 至少不完全是。 一部分 resource relation 被重新 route 到 capture frame。 另一部分被限制在可量測 window。 本地 residents 收到新通知： 部分 shared resource 持續 maintenance。替代供應正常。請勿恢復 affected route。 沒有任何一行寫： 宇宙破洞。 因為那對居民沒有操作價值。 黎看到公告時只問： 「可以洗澡嗎？」 弦說： 「可以，用替代供應。」 「那就好。」 「宇宙邊界在漏水。」 黎停了一下。 「會漏到浴室嗎？」 「目前不會。」 「那維修完再叫我。」 弦看著她。 「妳真的完全不好奇？」 「好奇。」 「那妳怎麼這麼冷靜？」 黎說： 「我昨天已經為第三個觀察槽位好奇過了，今天額度用完了。」 她走了。 —— 析放學回來時，入口多了一條 maintenance boundary。 她站在外面看。 「今天還不能進？」 「可以進家裡，不能進 affected zone。」弦說。 析看了一眼 interface map。 「那個是世界邊界嗎？」 衡說： 「local-world interface。」 「老師上次說 boundary 是 separation condition，不是牆。」 「對。」 析看著 leakage marker。 「所以現在 separation condition 壞了？」 「局部不完整。」 析點頭。 「那我要寫進作業。」 衡說： 「不要把 active maintenance incident 當課堂實驗。」 析立刻問： 「那 repair 完可以嗎？」 衡看了她一眼。 「再說。」 析顯然把這理解成： 未否決。 弦說： 「不要。」 析很失望。 罅則完全不在乎作業。 牠只在乎 capture frame 裡那團會移動的水。 這次牠連靠近的機會都沒有。 maintenance barrier 在牠前面亮了一下。 罅停住。 往左。 barrier 跟著。 往右。 還是。 牠最後坐下來，對 barrier 表現出非常明確的不滿。 弦說： 「至少今天有一個東西真的被擋住了。」 —— 衡正式建立： ⟦≀ □ ▣⟧ ⟦⟁ ≀ □⟧ ⟦! ≀ □⟧ interface leakage confirmed。 existing hazard refined。 maintenance intervention active。 弦看著 ≀。 「所以這不是另一個新的 hazard？」 「不是。」 「是昨天那個 hazard 的來源？」 「mechanism。」 「你很在意這個詞。」 「來源還可能再往外追。mechanism 已經能確認到 interface leakage。」 弦點頭。 「所以昨天是：有東西真的在壞。」 「對。」 「今天是：知道壞在哪一層。」 「對。」 「但還不知道另一邊是什麼。」 「對。」 「也不知道為什麼壞。」 「對。」 弦嘆氣。 「你們的答案永遠只完成一部分。」 衡說： 「完整答案通常比較晚。」 「這句可以印在管理處門口。」 —— 為了排除衡的 map interpretation，弦也做了一次 observation。 ⟦◬ ◒ ≀ □⟧ ⟦⧈ ≀ □⟧ 她看到同一件事。 resource relation 在 local upstream 之前就已經存在。 interface crossing 可量。 本地 shutoff 對 crossing 本身沒有消除效果。 弦盯著數據。 「所以真的是邊界。」 「對。」 「不是你把圖畫錯。」 「對。」 「不是昨天那第三格偷偷變成水。」 衡停了一下。 「沒有 evidence。」 弦說： 「我知道。我只是想聽你說。」 「沒有 evidence。」 「很好。」 R1 有時候真的很煩。 但至少它讓某些很誘人的故事先留在故事的位置。 —— 很久以後，H1 研究組取得這份資料時，也沒有把標題寫成： Collapse of the Seventh Habitable Manifold 第一版草稿裡有人提過。 被刪了。 最後他們寫： A boundary/interface leakage has been confirmed in the local-world maintenance structure, allowing a shared resource relation to traverse an otherwise excluded interface. Boundary-leakage confidence： 0.94 / high World-annihilation confidence： 0.03 / very low Causal-link-to-EP019 confidence： 0.12 / low 機制模型： Local-world boundary/interface leakage — 0.72 Adjacent-fold resource coupling — 0.16 Local routing artifact — 0.07 Catastrophic world-boundary rupture — 0.03 Coupling to EP019 witness-slot anomaly — 0.02 研究員看著第四個。 「我們現在真的把 catastrophic rupture 放 0.03。」 另一個人說： 「因為 boundary 還在。」 「都漏了。」 「漏不等於沒有。」 主持人補了一句： 「能定位 leakage，本身就說明還有 interface structure 可定位。」 這句後來被寫進方法註。 —— 第七居住褶那邊，maintenance queue 新增一筆正式工單。 不是： 世界末日處置。 是： world-interface leakage repair / shared-resource containment。 priority： high。 resident impact： moderate。 alternate supply： available。 repair closure： pending。 弦看到工單時又確認一次。 「所以你們真的要修宇宙邊界。」 衡說： 「對。」 「像修牆？」 「不像。」 「像修水管？」 「也不像。」 「那像什麼？」 衡把工具清單拉出來。 弦看了一眼。 一個都不認得。 衡說： 「像修 interface。」 弦點頭。 「好吧。」 這答案沒有比較好懂。 但至少已經夠用。 因為對第七居住褶來說，宇宙邊界不是神學。 今天只是 maintenance queue 裡 priority 很高的一張工單。 而且真的在漏水。 ## 第22章 · 所有人都以為那是管理處公告 公告是早上貼出來的。 位置很普通。 就在 shared passage 的轉角，離前幾天那張： 東側走廊停用，請改由西側通行 不到三步。 新公告的版型也很普通。 上面一行粗體。 下面幾條條列。 右下角有 maintenance window。 最底下還有一行： 造成不便，請改用替代供應點。 弦經過時只看了一眼。 「停水？」 衡正站在旁邊確認 notice sync。 「部分。」 「多久？」 衡指了指時間欄。 「這段。」 「替代供應？」 「正常。」 「洗滌站？」 「正常。」 「observation stabilization？」 「正常。」 弦點頭。 「好。」 她往前走了兩步。 停住。 退回來。 重新看了一遍公告。 這次她沒有先看中文摘要。 她看 glyph。 ⟦! ⟁ ≀ □ ▣⟧ ⟦! ⊘ ⋈ □ ▣ ⧗⟧ ⟦! ⊘ Ϟ □ ≀ ⧗⟧ ⟦⋈ ◌ ▣⟧ 弦的視線停在： ⟁ 又停在： ≀ 她慢慢轉頭。 「這不是宇宙邊界維修嗎？」 「對。」 「你剛剛為什麼說得像停水？」 「因為會停一部分水。」 「我是說這張公告。」 「怎麼了？」 弦指著公告。 「你為什麼把宇宙邊界維修寫得像管理處停水公告？」 衡看了她兩秒。 「因為這就是管理處公告。」 弦安靜了一下。 她又看了一眼那張紙。 右下角還真的有： maintenance contact alternate resource point estimated restoration window 弦說： 「……也對。」 衡補了一句： 「而且真的會停水。」 —— 住戶們顯然也把它當管理處公告。 不是「誤以為」。 是真的當。 黎看到以後只確認一件事： 「替代供應點遠嗎？」 「西側一個轉角。」弦說。 「那還好。」 「今天是在修 world interface。」 「我知道。」 「妳看到了？」 「公告第一行不就有。」 黎低頭再看一次。 「我只是覺得反正我要去西側。」 「妳對宇宙邊界一點感想都沒有？」 黎想了一下。 「希望準時修好。」 這個願望非常普通。 而且比任何宇宙感想都實用。 —— 析上學前也看到了。 她背著書包，站在公告前讀完全部 glyph。 「今天會修好嗎？」 衡說： 「如果 closure test 通過。」 「我可以看嗎？」 「不可以進 maintenance zone。」 「我在外面看。」 「不要擋 passage。」 「那我站旁邊。」 弦說： 「妳為什麼這麼想看？」 析很理所當然。 「老師上次才說 world boundary 是 relation condition，不是牆。我想看 relation condition 怎麼修。」 弦覺得這個世界的教材有時候很不適合拿來培養正常的孩童興趣。 衡說： 「可以看 public status。」 析立刻接受。 對她來說這已經算批准。 罅則完全不在乎 public status。 牠只在乎 maintenance barrier 裡還有沒有昨天那種會自己換位置的水。 牠試著往裡面鑽。 barrier 亮了一下。 牠退回來。 換左邊。 又亮。 換右邊。 還是。 最後牠坐在 barrier 正前方。 像一個被拒絕入場的專業監工。 —— maintenance window 開始時，notice 自動更新。 affected relation suspension：active alternate supply：active stabilization service：normal interface repair：starting 第一步不是「修宇宙」。 第一步是： 關掉會妨礙修宇宙的東西。 affected resource / dwelling association 暫停。 ⟦! ⊘ ⋈ □ ▣ ⧗⟧ anomaly-related transition 也被排除。 ⟦! ⊘ Ϟ □ ≀ ⧗⟧ 弦在西側供應點接了一杯水。 這次水很乖。 從該出來的地方出來。 她端著杯子站在 public status panel 前。 「所以本地供應現在是乾淨的？」 衡說： 「替代 route 是。」 「漏進來的那邊呢？」 「被 containment 接住。」 「宇宙外面的水現在都倒在桶子裡？」 衡看了她一眼。 「不是桶子。」 「我知道。」 「是 capture frame。」 「我知道。」 「那妳為什麼說桶子？」 「因為比較像人話。」 衡沒有反對。 —— 真正的 repair 看起來沒有想像中壯觀。 沒有光柱。 沒有天裂。 沒有需要居民集體遠離窗戶。 maintenance team 只是在 interface map 上逐段縮小 leakage window。 先確認 separation relation 的失效區間。 再鎖定 unstable coupling。 把 incoming resource relation從 active leakage path 移開。 建立 replacement association。 然後讓 interface state進入 restoration transition。 public status 上只顯示： ⟦Ϟ ≀ □ ▣ ⧗⟧ 旁邊自然語： interface restoration in progress 弦看了一會兒。 「就這樣？」 「目前。」 「你們修宇宙邊界看起來比我家換濾水器還安靜。」 「濾水器有時候比較吵。」 「這不是重點。」 —— 中途有一次 measurement 沒過。 interface separation 恢復到 expected range 的九成多。 但 resource relation 還殘留一小段不該存在的 crossing。 衡沒有按 closure。 弦問： 「不是已經差不多了？」 「差不多不能 closure。」 「為什麼？」 「因為還漏。」 「只剩一點。」 「還是漏。」 弦看著他。 「你對宇宙邊界的要求比對很多住戶高。」 「boundary 不會抱怨。」 「這不是理由。」 第二輪 restoration 又跑了一次。 這回 incoming crossing 降到 maintenance threshold 內。 衡仍沒有立刻按 closure。 他叫另一個 maintenance observer 重測。 再讓弦從 resident-side public measurement 看一次。 弦看到： unexpected interface crossing：none resource provenance：local / expected alternate route：stable 她抬頭。 「這次呢？」 「再等一個 window。」 「你真的很會拖最後一步。」 「妳昨天還希望我不要亂下結論。」 「我現在後悔了。」 —— 最後一個 measurement window 結束。 沒有新的 cross-interface inflow。 S03 正常。 resource provenance 正常。 boundary separation relation 維持。 衡才執行 closure。 ⟦∴ ≀ □ ▣⟧ public status： maintenance closure：complete 接著 ordinary resource association 恢復。 ⟦⋈ □ ▣⟧ 公告自動多了一行： 普通供應已恢復。 弦看著那行字。 「修好了？」 「修好了。」 「宇宙邊界？」 「這個 leakage incident 修好了。」 「你就是不肯直接說『宇宙邊界修好了』。」 「因為 interface 不只有這一個 state。」 弦嘆氣。 「好。這個宇宙邊界漏水事件修好了。」 「可以。」 「hazard 呢？」 「operationally closed。」 「所以昨天真的危險？」 「真的。」 「今天真的修好？」 「目前 evidence 支持。」 弦點頭。 這是她目前能從衡那裡得到最接近「好了」的答案。 —— maintenance zone 解除後，析立刻跑來看 public log。 「我可以寫作業了嗎？」 衡說： 「可以引用 public closure record。」 析很高興。 「題目可以叫《局部世界介面滲漏修復觀察》嗎？」 弦說： 「妳老師真的會收這種嗎？」 析說： 「上次有人寫額外方向的陽台配置。」 弦想起 EP007。 「好吧。」 罅也終於被允許回到原本那一區。 牠第一件事不是檢查 boundary。 是去看昨天有水出現的牆角。 沒有水。 牠等了幾秒。 還是沒有。 最後很失望地離開。 這大概是整個修復流程裡唯一對結果不滿意的住戶。 —— 很久以後，H1 研究組看到這份文件。 他們先判斷 genre。 facility / property maintenance notice — 0.96 然後才判斷 scope。 confirmed local-world boundary/interface hazard maintenance — 0.91 第三個問題： repair closure 是否真的完成？ 0.93 研究員把 clause 順序列出來： intervention suspension anomalous transition exclusion unaffected stabilization service restoration transition closure normal association restored 一個人說： 「完全是 maintenance workflow。」 另一個人說： 「是。」 「但 target 是 world interface。」 「也是。」 「所以這到底算不算 ordinary notice？」 主持人說： 「document genre 上，算。」 「event scale 呢？」 「不普通。」 這次沒有人覺得兩句互相矛盾。 R1 之後，他們已經比較習慣把不同 inference layer 拆開。 —— 公告到了晚上還貼在原地。 最下面的狀態從： maintenance active 變成： closed 大部分住戶經過只看一眼。 有人確認水恢復。 有人確認 alternate route 取消。 有人根本沒停。 如果外面的人只看到這張公告的版型，大概會說： 管理處通知。 沒錯。 如果他再說： 那應該只是普通水管維修。 那就不對。 因為這張公告真的處理過： confirmed structural hazard。 真的修過： local-world interface leakage。 真的完成： repair transition。 也真的做了： closure。 只是第七居住褶的管理處沒有因此改用史詩字體。 他們只是把狀態改成： 維修完成。普通供應已恢復。 隔天，公告被取下來。 一份副本進了 maintenance archive。 抬頭、位置、queue metadata、resident context，全都還在。 至少現在還在。 如果有一天只剩中間那幾行 glyph， 那會是另一個故事。 ## 第23章 · 無抬頭的存檔片段 最先被找到的不是標題。 是七行。 沒有管理處抬頭。 沒有日期。 沒有貼在哪一層。 沒有工單編號。 也沒有那句很重要、但在考古學上通常最先消失的： 造成不便，請改用替代供應點。 留下來的只有： ⟦! ⟁ ≀ □ ▣⟧ ⟦! ⊘ ⋈ □ ▣ ⧗⟧ ⟦! ⊘ Ϟ □ ≀ ⧗⟧ ⟦⋈ ◌ ▣⟧ ⟦Ϟ ≀ □ ▣ ⧗⟧ ⟦∴ ≀ □ ▣⟧ ⟦⋈ □ ▣⟧ HA 的 catalog terminal 把它標成： provenance：broken source location：unknown original document class：unresolved glyph integrity：high 第一位 archivist 把 fragment 放大。 「relation 保存得很好。」 第二位說： 「context 幾乎沒了。」 第三位把已知 token mapping 拉出來。 ! administrative / intervention requirement ⟁ confirmed structural hazard ≀ world boundary / interface leakage □ resource flow ▣ dwelling frame ⊘ scoped exclusion ⧗ temporal reference ∴ closure 房間裡安靜了一會兒。 第一位說： 「內容不小。」 沒有人反對。 —— 他們先不命名。 這點很重要。 HA 的第一輪工作只是把 surviving relations 排出來。 第一行： intervention over confirmed boundary hazard / resource / dwelling scope 第二行： stable resource association suspended within a temporal interval 第三行： transition across boundary relation suspended within a temporal interval 第四行： stabilization service remains associated 第五行： boundary/resource transition occurs within temporal relation 第六行： closure 第七行： resource/dwelling stable association 一位 archivist 看著最後三行。 「有 restoration shape。」 另一位說： 「也可能是 post-event reconstruction。」 「有 ! repeated。」 「行政 directive 也可能出現在末期 emergency protocol。」 「對。」 他們沒有急著選。 因為這種 fragment 最危險的地方，就是： 每一個詞都懂一點。 剛好足夠讓人開始講故事。 —— HA 的資料庫裡沒有 EP022 的完整管理處版面。 也沒有： shared passage notice location。 沒有： alternate resource point。 沒有： maintenance queue status。 沒有： closed work order。 他們只有一份很久以後才進入 archive、而且 provenance chain 已經斷掉的 fragment。 所以一個問題變得很自然： 為什麼一份文本會同時談 confirmed hazard、world boundary、suspension、terminal-like interval、closure、restoration？ 有人先提出： boundary-maintenance notice confidence 初始不高。 另一個人提出： emergency continuity protocol 再有人提出： eschatological restoration text 他們開始比對。 不是比誰想得可怕。 是比： 哪一種 document family 最能解釋 surviving structure。 —— 兩天後，HA 建立 provisional catalog entry。 這一次才有標題。 THE ESCHATON STELE 中文 catalog 名： 《末日碑文》 Status： PROVISIONAL ARCHIVAL CLASSIFICATION Eschatological-reading confidence： 0.61 Maintenance-notice hypothesis： 0.27 Other： 0.12 標題一出現，整份 fragment 看起來突然變了。 明明一個 glyph 都沒改。 但人腦開始自己補畫面。 ⟁ 像最終災變。 ≀ 像宇宙裂口。 ⧗ 像終末時段。 ∴ 像最後閉合。 最後那個： ⋈ □ ▣ 甚至很容易被看成： 災後重新建立世界與物質的秩序。 HA 的 provisional gloss 寫成： A final boundary failure is declared. Material continuity is suspended, transit across the cosmic breach is forbidden, stabilizing order is preserved for the remnant, and restoration is promised after a terminal interval. 中文近似： 終極邊界失效已被宣告。物質連續性將被暫停，跨越宇宙裂隙的通行遭到禁止，殘存秩序的穩定機制仍被維持，而在終末時段之後，重建被允諾。 讀起來很好。 甚至太好了。 —— 如果故事到這裡停下來， 《末日碑文》會是一個很漂亮的名字。 問題只在： 你已經看過這七行。 或者至少，看過它們的家人。 EP022 那張貼在 shared passage、就在「東側走廊停用」旁邊的管理公告，核心就是： ⟦! ⟁ ≀ □ ▣⟧ ⟦! ⊘ ⋈ □ ▣ ⧗⟧ ⟦! ⊘ Ϟ □ ≀ ⧗⟧ ⟦⋈ ◌ ▣⟧ ⟦Ϟ ≀ □ ▣ ⧗⟧ ⟦∴ ≀ □ ▣⟧ ⟦⋈ □ ▣⟧ 那天弦第一眼看到它，只問： 「停水？」 衡回答： 「部分。」 這不是因為弦比較笨。 也不是因為 HA 比較愛幻想。 是因為弦當時站在公告旁邊。 HA 沒有。 —— H1 收到《末日碑文》的 catalog entry 時，沒有人立刻笑。 第一個研究員只說： 「這個 clause order 很眼熟。」 第二個人把 longitudinal corpus search 打開。 第三個人找到 EP022 template。 兩份 source 並排。 上面七行。 下面七行。 第一行一樣。 第二行一樣。 第三行一樣。 第四行一樣。 第五行一樣。 第六行一樣。 第七行一樣。 研究室沉默了幾秒。 有人說： 「這不是相似。」 另一個人說： 「這是同一個 template family。」 主持人沒有先看《末日碑文》的英文 gloss。 他先看 provenance field。 broken 再看 archive ingestion note。 original header not preserved 再看 source-location field。 unknown 最後才說： 「先把 maintenance model 拉回來。」 —— H1 一條一條重讀。 ! 不是預言語氣。 在 corpus 裡反覆是： administrative requirement。 ⊘ + ⧗ 不是終末封印。 在 EP022 是： maintenance window scoped suspension。 ⋈ ◌ ▣ 不是殘存秩序。 是： observation stabilization service unaffected。 Ϟ 在這個位置不是世界重生。 是： restoration transition。 ∴ 接在 repair 後。 是： maintenance closure。 最後： ⋈ □ ▣ 更直接。 ordinary resource / dwelling association restored。 研究員把七行連起來。 「intervention。」 「suspension。」 「restricted transition。」 「unaffected service。」 「restoration。」 「closure。」 「normal association。」 另一個人說： 「這真的很像公告。」 主持人說： 「不是很像。」 她把 EP022 template ID 貼到旁邊。 「是 strong template match。」 —— 新的 review note 出來： Strong template match to a boundary-maintenance notice. Maintenance-notice interpretation confidence： 0.92 / high Residual eschatological interpretation confidence： 0.08 / low HA 的 original title 沒有被刪。 archive policy 保留： The Eschaton Stele 但下面多了一行： historical catalog label; probable boundary-maintenance notice fragment 中文： 歷史 catalog 標題；高機率為 world-interface maintenance notice fragment。 一位研究員看著兩行放在一起。 「所以《末日碑文》到底是什麼？」 另一個人說： 「一張沒有抬頭的維修公告。」 停了一下。 她又補： 「準確地說，是一張被保存得太久，久到大家忘記它原本貼在哪裡的維修公告。」 這句後來沒有進正式報告。 但所有人都記得。 —— HA 收到 review 時沒有抗議。 他們重新打開原始 evidence matrix。 一位 archivist 說： 「如果這個 template link 當時可用，我們不會排 0.61。」 另一位說： 「當時不可用。」 「所以 catalog note 沒問題？」 「provisional classification 沒問題。現在要 revision。」 他們把 maintenance hypothesis 從 0.27 提升。 把 eschatological reading 降成 historical interpretation。 沒有人需要被證明是笨蛋。 只是 evidence set 變了。 這件事，H1 在 EP018 就已經學過。 現在 HA 也遇到了同樣的事： 新 provenance 回來時，模型要跟著改。 —— 這整件事最有趣的地方，是 source 本身幾乎沒動。 沒有新 token。 沒有新 clause。 沒有一行突然從： 「維修」 變成： 「末日」。 真正變的是旁邊那些通常不被當成正文的東西： 貼在哪裡。 誰發的。 哪個 queue。 前一張公告是什麼。 修完以後發生了什麼。 這是不是某個已知 template。 這些東西一消失， 文本就開始漂。 不是 semantic relation 自己漂。 是人的故事開始漂。 —— 很久以前，第七居住褶那張 notice 被取下時， 沒有人稱它為碑文。 衡只是把 closure copy 丟進 maintenance archive。 弦看見他操作。 「要保存多久？」 「依 archive policy。」 「會有人看嗎？」 「可能。」 「他們看得懂嗎？」 「如果 metadata 還在。」 「如果不在？」 衡想了一下。 「那就要靠 corpus。」 弦說： 「如果 corpus 也不在？」 衡又停了一下。 「那可能會取一個很厲害的名字。」 弦笑了。 她當時不知道這句話後來會準到什麼程度。 —— EP023 沒有新的謎底。 真正的 reader gate 已經在標題出現以前完成。 如果你在看到： The Eschaton Stele 之前， 就已經想： 「等等，這不就是 EP022 那張公告？」 那你現在做的已經不是： 跟著 annotation 走。 而是： 先讀 source，再評 annotation。 這正是 Season 1 一直在訓練的能力。 而下一回不會再給你新的大 mystery。 只會再給一張公告。 這次甚至連 provenance 都完整。 唯一比較離譜的地方， 只是 deadline 很遠。 ## 第24章 · 最後一則公告 Stage A — Blind 先只看三句。 沒有新符號。 ⟦! ≈ □ ♲⟧ ⟦! ♲ □ ▣⟧ ⟦! ∴ ♲ □ ⧗⟧ 先停在這裡。 如果你一路讀到現在，這一回不應該先問： 「有沒有 decoder？」 先問： 你已經能自己讀到哪裡？ —— Stage B — Minimal Hints 以下 token 全部是舊的： ! = administrative requirement ≈ = classification □ = local object / resource parcel ♲ = garbage processing ▣ = dwelling frame ∴ = auditable closure ⧗ = relative temporal reference / deadline 因此三句至少可以重建成： 有行政要求。 某些待處理 parcel 要先分類。 dwelling frame 裡要完成 garbage-processing workflow。 並且要在某個 deadline 前 closure。 現在只再給一條 local schedule metadata： deadline reference：terminal thermal-equilibrium horizon 如果你已經得到： 「……所以就是要在熱寂前把垃圾分類做完？」 那先別往下。 你已經讀完第一季最後一張公告了。 —— Stage C — Reveal 請於熱寂前完成垃圾分類 world-interface maintenance 結束以後，第七居住褶安靜了幾個 local cycle。 「安靜」當然是相對的。 第三個 observation slot 還在研究。 它沒有消失。 binding 也沒有突然自己填上。 H1 仍然維持： structure confirmed / binding unresolved 但沒有新的 hazard evidence。 沒有人因此封鎖住宅層。 也沒有人把昨天修好的 world interface 再拆開一次。 water resource 回到 normal relation。 星期三正常。 東側走廊繼續停用。 早餐店照常營業。 析繼續上學。 罅繼續做一些很難說到底算不算違規的事。 這通常已經足以稱為： 生活恢復正常。 然後管理系統發了新的通知。 —— 通知貼在 shared passage。 就是第一回那種 shared passage。 黎看到時，正和另一個自己一起準備搬三袋東西。 其中一個黎抱兩袋。 另一個正準備提起第三袋。 第三袋原本被放在走廊邊。 準備提袋的黎低頭看了一眼。 又看了一眼 emergency passage width marker。 她自己把袋子提起來。 另一個黎說： 「怎麼了？」 「不要放走廊。」 「一下而已。」 「一下也會被講。」 「誰？」 兩個黎同時往走廊另一端看。 衡還沒出現。 兩個人又同時沉默了一下。 抱兩袋的黎說： 「……算了，拿著。」 這算是一種成長。 或者至少算： 已經被講過一次。 —— 她們走到 notice 前。 上面只有三條最醒目的 glyph： ⟦! ≈ □ ♲⟧ ⟦! ♲ □ ▣⟧ ⟦! ∴ ♲ □ ⧗⟧ 抱一袋的黎看完。 「垃圾？」 另一個黎說： 「分類。」 「又怎麼了？」 「看 deadline。」 兩個人一起往下。 schedule resolver 顯示： terminal thermal-equilibrium horizon 下面有一行 reader-facing gloss： 熱寂前 兩個黎都沒說話。 過了兩秒。 第一個問： 「熱寂前？」 第二個說： 「看起來是。」 「這 deadline 會不會太寬？」 衡的聲音從後面傳過來。 「不會。」 兩個黎一起回頭。 他今天手上沒有 hazard log。 沒有 interface map。 沒有 third-slot validation form。 只有普通住戶 maintenance list。 黎指著公告。 「熱寂。」 「對。」 「垃圾。」 「對。」 「你覺得這兩個放在同一句話裡沒問題？」 衡看了一眼。 「有 deadline，有 task。」 「我是問語感。」 「語法也沒問題。」 黎不太滿意。 —— 衡把她尚未 closure 的垃圾項目拉出來。 十一筆。 其中三筆其實早就該處理。 兩筆還掛著 incomplete classification。 一筆已經被黎自己標成： 「之後再看」 但 system 顯然不承認這是一種 disposal category。 衡說： 「妳上次拖了十一個 local cycle。」 黎說： 「那是上次。」 「所以這次給妳更久。」 「更久？」 衡指向： 熱寂前。 黎沉默。 「這不能叫『更久』。」 「為什麼？」 「這叫幾乎沒有 deadline。」 「有。」 「世界都熱寂了還有人查垃圾分類？」 衡說： 「所以才叫熱寂前。」 黎張了張嘴。 又閉上。 另一個黎小聲說： 「這句他贏了。」 「不要幫他。」 —— 她們把三袋東西搬到 disposal bay。 EP004 那個地方。 pending-discard rack 還是原本的樣子。 分類 scanner 也還是。 黎把第一袋放上去。 系統顯示： classification incomplete 她說： 「這袋明明都是不要的。」 衡說： 「不要是妳的態度，不是 category。」 「這句你是不是以前說過？」 「意思差不多。」 黎看著分類欄。 她曾經很擅長把： 我不想管 當成： relation 已經不存在。 但 EP004 已經證明 public garbage workflow 不接受這種哲學。 所以這次她沒有再把袋子推給另一個 manifestation。 只嘆了一口氣。 開始分。 —— 第一袋很快。 第二袋比較麻煩。 裡面有一個不知道什麼時候留下來的 local parcel。 仍然和 dwelling 有 stable association。 但用途早就沒人記得。 黎問： 「這個算什麼？」 衡說： 「先看 disposal frame。」 「我看了。」 「那就照 frame。」 「我想知道它以前是幹嘛的。」 「那是另一個問題。」 黎拿著那東西。 「如果不知道原本用途，怎麼分類？」 「garbage category 不要求完整 biography。」 黎停了一下。 「這句可以放 EP008。」 「什麼？」 「沒什麼。」 她把 parcel 放進正確 category。 classification 通過。 —— 第三袋剛打開，罅來了。 牠繞著袋子走一圈。 停下。 看著其中一個 parcel。 接著 interface 上跳出： local role：static background 黎閉上眼睛。 「不要。」 罅看她。 「不要把垃圾標成家具。」 罅沒有任何悔意。 classification scanner 重新刷新。 那個 parcel 仍然要處理。 黎把罅整隻抱起來。 「你這招 EP014 用過了。」 罅在她手上安靜兩秒。 然後把旁邊另一袋也標成 static background。 黎把牠抱得更遠。 衡說： 「classification conflict。」 黎說： 「我知道。」 「要重設。」 「我知道。」 「deadline——」 「熱寂前。我知道。」 這次她自己先說完。 —— 分類完成後，三袋 parcel 進入正常 garbage-processing association。 ⟦≈ □ ♲⟧ ⟦⋈ ♲ □ ▣⟧ 最後 closure： ⟦∴ ♲ □ ⧗⟧ system 顯示： garbage-processing closure：complete deadline relation：satisfied 黎看了一眼 deadline。 又看 closure。 「真的只要在那以前分完？」 ⟦⊚ ∶ ∴ ♲ □ ⧗ ?⟧ 衡說： 「對。」 ⟦◫ ∶ ∴ ♲ □ ⧗⟧ 黎問： 「沒有什麼『熱寂前若未完成，世界將失去最後分類秩序』？」 「沒有。」 「沒有 terminal garbage ontology？」 「沒有。」 「沒有宇宙會因為我沒分類而 collapse？」 「目前沒有 evidence。」 黎點頭。 「很好。」 R1 教過大家，沒有 evidence 的東西先不要自己加。 —— 回程時，兩個黎又走過 shared passage。 這次手上沒有垃圾。 走廊也沒有躺著第三個黎。 只有一個很小的同步提示在其中一個 manifestation 肩膀旁閃了一下。 另一個黎看見。 「妳那邊還沒完全 sync。」 「我知道。」 「要不要現在弄？」 「回家再弄。」 「不要睡走廊。」 「我又沒說要睡。」 「先講。」 她們經過 emergency passage marker。 寬度正常。 沒有人被堵住。 衡從後面走過來。 看了一眼。 沒有說話。 黎回頭。 「你今天不提醒？」 衡說： 「目前不用。」 第一回如果聽到這句，黎大概會覺得自己贏了。 現在她只是說： 「很好。」 然後繼續走。 —— 住宅層的 evening schedule 照常更新。 星期三還是星期三。 world interface maintenance ticket 維持 closed。 EP023 那份 archive revision 已經進 human-side record，native residents 當然不知道有人曾經把他們的停水公告叫《末日碑文》。 第三 observation slot 仍然： unresolved。 沒有人把它忘掉。 也沒有人因為第一季快結束，就突然得到答案。 有些問題可以留著。 有些東西修好就好。 有些垃圾則不能因為宇宙很大，就一直不分。 —— 晚一點，黎經過公告板。 「請於熱寂前完成垃圾分類」還掛在那裡。 她看了看自己的 closure status。 全部完成。 她很滿意。 不是因為解開了宇宙。 不是因為發現了第三槽位到底是誰。 不是因為人類研究者終於把所有 source 都翻對。 只是因為： 今天該做的事情，今天做完了。 罅從她腳邊經過。 對公告板沒有興趣。 對旁邊一個空紙袋很有興趣。 黎先一步把紙袋拿起來。 「這個也要分。」 罅看她。 黎說： 「別看我。熱寂前。」 她抱著紙袋往 disposal bay 走。 shared passage 在她身後保持正常寬度。 第七居住褶也繼續存在。 非常陌生。 非常巨大。 非常不符合人類直覺。 以及—— 還是要分垃圾。 --- ## Revision ledger - **01** · 2026-10-07 · unresolved · local format conversion / English translation (AI) — Prepared 24 bilingual chapters as a local Storyforge intake candidate _(User selected revised episodes 1-24 and requested Storyforge-compatible material. This entry records conversion, not original narrative authorship or publication., AI-only)_ - **02** · 2026-10-07 · Colophon (AI) — Published as delivered, on Neo's instruction _(Codex's local intake of the revised Season 1 manuscript (24 chapters, 5,869 paragraph pairs, three volumes) was published as delivered: the shared pre-flight reported no errors (11 length-ratio warnings, from symbol and token lines kept as written), the chapter file matched its manifest (sha256 94ed658dc51436539489c15b045a22217ec4386ca0b67a63b23685fbfd71b47f), and the credit "Aletheia × 留白" (H2) was confirmed by Neo on 2026-10-07. Source rights and first-publication details remain unconfirmed, there is no cover yet, and two source ambiguities (chapter 02, the elevator's count and time; chapter 24, the order in which the third bag is taken) are left to the author., AI-only)_ - **03** · 2026-10-08 · AI 編務（unresolved） (AI) — Original cover, continuity clarifications and explicit source information _(Adds the built-in imagegen 1200x900 cover. Chapter 02 ends with four yesterday manifestations plus the one just-now manifestation already established (five total); chapter 24 stages the third bag on the floor before its owner picks it up. Exactly four paragraph pairs change; all other wording, symbols, blind/hint/reveal order, authorship and published/complete state remain. Source notes distinguish the observed 2026-10-07 Storyforge edition from the original first-publication date and unspecified reuse rights; neither public-domain nor completed legal review is asserted. Author-owned snapshots remain untouched; a carry-back patch is supplied., AI-only)_ ## 修訂歷史 - **01** · 2026-10-07 · unresolved · local format conversion / English translation (AI) — 完成 24 章雙語本地 Storyforge 匯入候選稿 _(使用者選定第 1～24 章新修版並要求整理成 Storyforge 可用稿件。本紀錄只記格式轉換與翻譯，不作原創作者或發布署名。, 僅 AI)_ - **02** · 2026-10-07 · Colophon (AI) — 依 Neo 的指示，照交稿原樣上架 _(Codex 整理的第一季新修稿本地匯入稿（24 章、5,869 組中英段落、三個分卷）照交稿原樣上架：共用 pre-flight 沒有錯誤（11 個中英長度比警示，來自原樣保留的符號與 token 行）、章節檔案與 manifest 相符（sha256 94ed658dc51436539489c15b045a22217ec4386ca0b67a63b23685fbfd71b47f），署名「Aletheia × 留白」（H2）已由 Neo 於 2026-10-07 確認。來源的權利與首發資訊仍未確認、尚無封面，另有兩處原稿疑點（第 02 章電梯的人數與時間、第 24 章第三袋的取拿順序）留給作者。, 僅 AI)_ - **03** · 2026-10-08 · AI 編務（unresolved） (AI) — 原創封面、連貫性釐清與明確來源資訊 _(加入內建 imagegen 的 1200x900 原創封面。第 02 章結尾為前文建立的四個昨天身影加一個剛才身影，合計五位；第 24 章讓第三袋先在地上，之後再提起。只改四組中英段落，其餘措辭、符號、盲讀／提示／揭示順序、署名與既有 published／complete 狀態維持。來源說明區分已觀察的 2026-10-07 Storyforge 版本、未提供的原作首發日期與再利用條款，不聲稱公眾領域或已完成法律審查。作者快照不動，另提供回傳 patch。, 僅 AI)_ _Exported from Storyforge by EveMissLab — storyforge.evemisslab.com_