Outerfold Daily Life: The Seventh Residential Fold

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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.