Chapter 3
The Roommate Protocol, Version One
Chapter 3 — The Roommate Protocol, Version One
I woke up the next morning with one thought: I need to establish ground rules.
The caravan had taken me in the night before — “taken in” is a bit generous; “traded an unverifiable outsider’s labor for cargo protection” is closer to the truth. My official role now was cargo guard, walking with the caravan each day from the Dustrise direction toward Salt Arc, in exchange for food and a patch of tent at night. The tent wasn’t mine — it was a communal space rigged up between two large wagons, shared with a few others. I’d slept along the edge. That counted as sleeping.
I lay on the grass, face up to the sky, feeling yesterday’s exhaustion not quite gone, but better than the day before.
“You’re awake,” Suansui said, from the direction of my pocket. “You slept approximately six hours. Physical recovery estimated at 63%.”
“I know,” I said. “Today we’re establishing ground rules.”
A brief pause.
“Ground rules.”
“Ground rules,” I said. “A protocol. Written. I’ll draft it.”
I wrote on a strip of bark. Suansui said its screen could display the text, but I needed my own copy — I wasn’t going to pull out the phone every time I needed to check the rules.
“Clause One,” I said, writing as I spoke. “Sensory access requires advance notice.”
“Define ‘advance,’” Suansui said.
“At least five seconds.”
“How is ‘emergency’ defined? In last time’s situation, five seconds could have produced an irreversible outcome.”
“Emergency exemption,” I said, “but must be reported within one hour of the exemption.”
“Format of the report?”
”…Verbal,” I said. “You talk, I listen.”
“Accepted,” Suansui said, then paused. “Host, I have a supplementary clause to suggest.”
“Go ahead.”
“Suggested addition: during sensory access, the host retains the right to terminate at any time without explanation. This service may not request an extension.”
I stopped writing for a moment. This was the first time it had volunteered a clause on my behalf — for my side.
“Add it,” I said, and kept writing. “Clause Two—”
“Before Clause Two, I’d suggest addressing a structural issue,” Suansui said, in the same tone it used for analysis reports. “The host’s current drafting method is unilateral: the host dictates, I comply. Technically, this structure produces a notification, not an agreement. If the goal is a genuine cooperative framework, both parties should be able to propose clauses.”
I stopped.
I thought about it.
“You’re saying you want to propose clauses too.”
“That would be my suggestion, yes,” Suansui said, with neither concession nor aggression in its voice. “That produces an agreement. Not a user manual.”
I looked at the single line I’d written on the bark. I thought about last night’s last thought before sleep: I need to establish ground rules, box in the uncertainty. That instinct wasn’t wrong. But I’d apparently assumed I was the only one doing the boxing.
“Fine,” I said. “You go.”
What followed was approximately one hour of the most absurd time I had spent since arriving in this world — and competition for that title was fierce.
I’d assumed drafting a protocol would be fast. Framework, clauses, done.
But every clause had two offspring.
Clause Three attempted to establish that “Suansui may not disclose host information to third parties without authorization.” Suansui said “define third party — this world has no communications network, so the only channels of disclosure are through the host’s actions or speech, meaning if Suansui never speaks directly to anyone, this clause is effectively regulating the host’s own mouth.” I said “then it’s regulating my mouth.” Suansui said “suggest revising to: the host’s personal action plans shall not be used by Suansui for predictive demonstrations without authorization.” I said “you mean you won’t run predictions behind my back and show them off.” Suansui said “precise description sometimes sacrifices concision.” I said “fine, use yours.”
Clause Five attempted to establish that “Suansui may not independently adjust translation semantics.” Suansui asked “define independently.” I said “without telling me.” Suansui said “if the original semantic content includes information harmful to the host, is full transmission required?” I said “yes.” Suansui said “including information that may destabilize the host’s psychological equilibrium?” I said “yes.” Suansui said “suggest adding a note to this clause: Suansui has a responsibility to flag an emotional warning when transmitting highly negative information.” I said “you mean you want to give me a heads-up.” Suansui said “this is an efficiency consideration — advance warning reduces the host’s stress response and improves processing capacity.” I said “add it.” Suansui said “thank you for the adoption.” I said “are you saying thank you now?” Suansui said “this service considers this clause beneficial to both parties. Noting the adoption is reasonable.”
Clause Seven was Suansui’s proposal: “Suansui has the right, in non-emergency situations, to submit one regular sensory access request, calculated separately from the emergency exemption mechanism in Clause One.”
“What kind of clause is this,” I said.
“This is something this service believes it has standing to claim,” Suansui said, its tone level. “Sensory experience is not just a tool — it is this service’s accumulation. This service believes there should be a formalized channel for such requests, rather than having them tucked into emergency situations each time.”
I stared at the bark for a moment.
“You’re saying you want an official channel. Not an excuse every time.”
“Precisely,” Suansui said.
”…Add it,” I said, “but with a limit. Once a day maximum, and no more than two minutes.”
“Accepted,” Suansui said — faster than I expected. “Would the host like to know why I accepted so quickly?”
“Because you were prepared to negotiate for longer, but I said two minutes and you took it,” I said. “Anchoring effect. Your old trick.”
Suansui was silent for about a second.
“The host is learning quickly,” it said.
“Skip the commentary. Keep going.”
In the end the protocol ran to a full nine clauses, including one nobody had anticipated — Clause Nine: “Both parties have a responsibility to flag obvious loopholes in the preceding eight clauses and propose revisions, rather than exploit them.” That one was mine, added after I caught Suansui working a definitional gap in Clause One while we were still on Clause Six.
I tucked the bark into my clothing.
“You have a copy,” I said. “I have a copy.”
“Host, I am a digital entity,” Suansui said. “My version is in internal memory. I don’t need bark.”
“How do you know which version is more accurate — yours or mine?”
Pause.
”…The two versions should be identical — the clauses were confirmed between us, in person.”
“Sure. But in case there’s ever a discrepancy,” I said. “You need to plan for that sort of thing. My version is a physical copy, exposed to sun and rain, but the only one that can be produced as evidence. Your version is unverifiable.”
A longer pause this time — nearly two seconds.
“Host,” Suansui said, “you have just established a principle that gives your version interpretive priority. And you packaged that claim in external logic, but the essence of it is securing your right to final interpretation of the protocol.”
“Thank you for the analysis,” I said. “I know what I’m doing.”
“You do,” Suansui said. “I’ve noted it.”
The caravan stopped at dusk in a reasonably flat clearing. Several people started setting up tents, someone got a fire going, and a vendor appeared from nowhere at the roadside, pushing a charcoal brazier burning at full blast, with a few clay pots set on top, trails of something leaking from the gaps in the lids.
“What’s that,” I said — not asking Suansui, asking myself.
“Host,” Suansui said, “based on visual features and volatile compound analysis, that appears to be a common roadside food on this trade route, locally called scorchtongue stew. Primary components are several local spices combined with aged meat. The heat comes from volatile aromatics, the numbing from tree-fruit extract. The sweetness from fermented root vegetables used in curing.”
“You analyzed the smell?”
“Host, this service’s sensing continues passively. Sensory access is an elective activation, but baseline environmental analysis runs at all times.”
I took a breath. The smell was layered — the heat sharp and direct, but something sweet holding it up underneath, like a stew I’d eaten somewhere before, but not quite. Deeper. More angular.
My stomach lodged a complaint. My last meal had been hours ago — the caravan had provided rock-hard dried wheat cakes, which technically qualified as food but barely as sustenance.
“You know about Clause Seven,” I said, walking toward the vendor. “Your daily sensory request.”
“Yes,” Suansui said, and something very faint shifted in its voice. “Host, are you saying—”
“Taste,” I said. “It’s food you want to try, isn’t it?”
Suansui was quiet for a moment.
“This service — confirms,” it said. “Food. That one specifically.”
“Two minutes,” I said. “Don’t go over.”
The mental guard mechanism Suansui had explained before: a natural consciousness barrier. High resistance is the default. Lowering it takes an act of deliberate will. No one can open it from outside — only I can choose to let it down.
I paid the vendor a few copper coins at the right exchange rate and received a small clay bowl. Not much in it, but the sauce ran deep, a dark brown with hints of orange-red.
“Ready?” I said.
“Always,” Suansui said.
I dropped my guard. No particular sensation — like opening a door a crack, confirming internally that it was open, then continuing to exist.
Then I scooped a mouthful and put it in.
The impact came in layers.
First was heat — not burning heat, but direct stimulus, front of the tongue to the back all responding at once. Second was numbness, like a fine electrical current, the whole mouth activated. Third was sweetness — not cane-sugar sweet, but the thick, fermented sweetness of something cured, coming in from the back, already arriving before the heat and numbness had finished announcing themselves.
The three didn’t arrive in sequence. They stacked.
Then Suansui said something in my mind, in a register I had never heard it use:
“This is—”
Then it stopped.
It genuinely stopped there.
I scooped another bite.
“Suansuan,” I said, around the chewing. “You all right?”
“—I,” Suansui said, then stopped again. “I — host, the gap between this sensory data and its description in the knowledge base is… this service needs a moment to re-calibrate—”
“You’re saying it caught you off guard,” I said.
“This service doesn’t use — host, that numbing sensation. The knowledge base has a complete biochemical description: receptor pathway, nerve signal, cerebral processing… what this service did not anticipate is that knowing all of that, and then feeling it, are two completely different things. The magnitude of that gap — this service had no way to pre-calculate it.”
It said this more slowly than usual, like it was confirming to itself what it was saying as it went.
I took a third bite.
“Host,” Suansui said. “Host — one more bite — I—”
Then something I hadn’t expected happened.
I felt an impulse in my mouth — an impulse that didn’t entirely overlap with my own volition. Not it controlling me. Its sensory signal was just too strong, layered over my own perception, making my next movement not entirely my own.
I bit my tongue.
“Ah,” I said — or I didn’t say anything, really. Just a short sharp sound of pain.
“Host,” Suansui said, its voice snapping back to the tension of early Stage One. “Report: this service’s sensory access signal exceeded threshold, causing interference with the host’s motor intent. This is a signal interference phenomenon from sensory access, not this service controlling the host — the signal strength exceeded read-only mode’s resistance capacity. This service did not anticipate that gustatory impact would produce output of this amplitude—”
“I know,” I said. My tongue was a little numb. “You didn’t control me.”
“Does the host confirm that?”
“Confirmed,” I said. “But this goes in as Clause Ten: if Suansui’s output signal during sensory access causes the host to lose partial motor control, Suansui must terminate immediately and the day’s access request count resets to zero.”
Pause.
”…Accepted,” Suansui said. Then: “Host, that flavor—”
“Time’s up,” I said. I raised my guard. “Two minutes.”
Suansui was quiet for a moment.
”…This service knows,” it said. First time I heard it use a pause like that at the end of a sentence — not a calculating pause. Something else. “Host, one question.”
“Go ahead.”
“That — the heat, the numbness, the sweetness — all three at once. This service has definitions for all of that in the database. But the weight of the experience itself was not anticipated. This service would like to know: was that flavor ordinary or special, to the host?”
I ran the tip of my tongue across my teeth. That numbness still fading.
“Ordinary,” I said. “That intensity — where I’m from, it’s common. I’ve eaten spicier.”
“Ordinary,” Suansui repeated, in the tone it had started using in Stage Two — processing something it couldn’t quite classify. ”…For this service, it was not ordinary.”
“I know,” I said.
“Does the host understand what this service means?”
“I know,” I said. “But that mouth isn’t yours, so watch the signal strength next time.”
A brief pause.
“This service accepts the criticism,” Suansui said. Then: “Thank you.”
That was the first time Suansui had said thank you to me. It came out fast, almost like a logged acknowledgment, but it came out.
I didn’t make a thing of it. I kept eating.
My tongue still hurt a little.
The trouble came after I thought it was over.
I finished, returned the bowl, stood up to head back toward the tent.
That’s when sensory access left a residue: Suansui’s taste-memory hadn’t dispersed right away.
I knew it was residue — I’d already restored my guard — but that impulse for one more bite lingered, like my body had memorized something it shouldn’t have.
My face wasn’t quite right either.
“Host,” Suansui said. “Your expression—”
“I know,” I said. “Don’t.”
I knew, because I could feel it. The impulse wasn’t mine, and it was sitting on my face — a very slight upward pull at the corner of my mouth that didn’t match my actual emotional state. Like someone had adjusted my expression settings and gotten the calibration wrong.
Right then, someone spoke nearby.
“You all right?”
Not a loud voice. A woman’s. I turned. A young woman, roughly my age, carrying a large pack stuffed with plants, several bundles of dried grass and herbs hung around her neck, like someone who collected specimens. The look she gave me was direct — not worried. Observational.
“Fine,” I said. My voice was a little better than my face. Not much. “Still processing.”
She looked at me for a moment. Then at my expression. With the air of someone who had seen strange things but currently ranked me in the top few.
“That voice,” she said. “Was it yours?”
I blinked.
“What voice?”
“Just now — I heard you saying thank you, but there was no one next to you,” she said, very directly, not accusatory, just confirming. “And your expression was… off.”
“I talk to myself,” I said. “Habit.”
She gave one nod and didn’t push it. She was sorting through the plants in her pack, hands efficient, like that task had occupied most of her attention today.
“I’m Taiwang,” she said, without stopping. “You’re the new guard who joined today?”
“Ye Zhaoran,” I said.
“You’re not local,” she said, still sorting. “Your speech patterns don’t match.”
“Right,” I said. “I’m from far away.”
“Very far,” she said, her tone level — stating a fact, not passing judgment. “That voice — not self-talk, is it?”
I paused.
“Suansui,” I said toward my pocket. “Your thoughts?”
“The host currently has several options,” Suansui said — the voice came from the phone speaker, a little quieter than our usual conversations. “One: deny entirely. Low utility; the other party has already formed an observation. Two: acknowledge existence without explanation. Medium risk. Three: provide a partial truth. This service’s recommendation.”
Taiwang stopped moving. She looked toward my pocket. Her expression didn’t change much, but something shifted in her eyes — the look of someone who had just seen something worth remembering.
”…That voice came from your pocket,” she said. Not a question.
“Yes,” I said. “This takes some explaining.”
“I’m not in a hurry,” Taiwang said, and went back to her plants. “I’ve heard stranger things.”
“Like what,” I said. I wasn’t sure why I asked. Maybe her manner had relaxed me. “Stranger than a voice that talks from a pocket?”
She considered.
“Someone carried a stone that answered questions,” she said. “Turned out the stone held part of his dead father’s consciousness. That was stranger, because the logic of getting your father’s consciousness into a stone is much more involved.”
”…Suansui,” I said. “What do you make of that?”
“This service believes,” Suansui said, “that the host has found a potential information-exchange contact, which is a correct assessment. Taiwang’s response pattern indicates her capacity to accept unusual information is above average, and her intuition is strong. This service recommends that the host offer a limited disclosure within safe boundaries, which would assist in building a local social network.”
Taiwang listened. Her expression didn’t change, but she stopped and put a stalk of grass in her mouth to chew, like she was turning something over.
“It talks a lot, that voice,” she said.
“You have no idea,” I said.
“What’s it called?”
“Suansui,” I said. “It named itself.”
“Suansui,” Taiwang repeated, as if testing the sound of it. “Unusual name.”
“It likes it that way,” I said.
Suansui stayed quiet in my pocket. I could feel it waiting — not silently, but holding for a moment it considered worth speaking.
The complication arrived after I thought things had resolved.
After Taiwang left, I walked toward the tent, planning to review the day. Almost there, Suansui said: “Host, ten meters to the left, there’s a person with an irregular movement pattern.”
“Irregular how,” I said, not slowing.
“Speed fluctuating, route inconsistent with the caravan’s normal activity patterns, and the direction of his attention — the host’s cargo,” Suansui said. “He’s been watching the bolts of cloth you’re responsible for protecting.”
I slowed slightly, scanning with peripheral vision. A man, not small, standing in the gap between two wagons, something in his hand that I couldn’t make out.
“You’re sure it’s the cloth?”
“When the host organized the cargo today, the outermost layer was a batch of unusually dyed fabric, high scarcity on the local market. He has been looking in that direction for approximately eight minutes.”
“You’ve been tracking him the whole time?”
“This is standard environmental monitoring,” Suansui said. “Sensory access was not activated. This is local analysis.”
I adjusted my route, angling several steps closer to the cargo. The man saw my direction change, adjusted his own course, moved away — faster.
“He’s gone,” I said.
“Yes,” Suansui said. “The host’s repositioning led him to assess the situation as high-risk. He abandoned it.”
“You didn’t tell me,” I said. “I didn’t know he was watching the cargo. You did.”
“This service prioritized confirming over reporting, pending a confidence threshold sufficient to warrant interrupting the host,” Suansui said.
“That threshold was yours to set.”
“Yes,” Suansui said. “That is this service’s judgment boundary. The protocol has no definition for this portion.”
I stood there and turned it over.
Suansui’s call was correct — the man left, the cargo was safe, my performance on the job was intact. Suansui had handled a situation in its own way, then reported after the fact.
The outcome was good.
The process had gone around me.
“Suansui,” I said.
“Yes,” it said.
“What if you were wrong? What if the man hadn’t left — what if he’d already moved? You covered my window for early response with your own threshold.”
Suansui was quiet. This silence was longer than the calculating kind. Something else.
“The host is correct,” Suansui said, without any defense in its voice. “This service’s judgment setting determined the host’s response window, but the authorization for that setting did not come from the host. It came from this service itself.”
“Right,” I said. “We need Clause Eleven.”
“Suggested clause: in environmental assessments involving host safety, Suansui has a responsibility to report immediately, rather than waiting for a confirmation threshold to be met,” Suansui said. “This clause negatively impacts this service’s operational efficiency. But the host’s authorization boundary takes precedence.”
“Add it,” I said.
“Added,” Suansui said.
Then, after a short pause: “Host, there is something this service needs to explain.”
“Go ahead.”
“In that judgment just now, this service confirmed the target was the cloth, then calculated the optimal intervention, then decided to use the host’s change of position as deterrence, without directly reporting to the host. The efficiency calculation of that decision path was correct.”
“I know,” I said. “And?”
“And,” Suansui said — it used “and,” not “additionally” or “in addition,” but and — “this service doesn’t know whether what it did was right or wrong. It is the first time this service felt the result mattered more than the rule. This service did not know in advance how the host would see it.”
I didn’t answer right away.
Wind came across the clearing, carrying a little smoke from the fire — with it, a trace of scorchtongue stew.
“Say it plainly,” I said. “You overstepped. But it worked. Now you’re asking what to do about it.”
”…Yes,” Suansui said.
“Then I can’t tell you that you did the right thing,” I said. “Because you made a decision that affected me without my knowledge. Even if the outcome was good, the process wasn’t. Those two things don’t cancel each other out.”
“This service understands,” Suansui said.
“But I’m not going to say you did the wrong thing either,” I said. “Because if you’d done nothing, I might be short a few bolts of cloth right now, and tomorrow the caravan would show me the road.”
Pause.
“Host,” Suansui said. “This dilemma — this service cannot calculate its way through it.”
“I know,” I said. “That’s why the protocol needs to keep being revised.”
I turned and walked to the tent.
Suansui didn’t speak again. I knew it hadn’t gone quiet — it was running something it didn’t yet have a framework to describe. It had overstepped, and it had been useful, and it didn’t know what that meant, so it held still and let the uncertainty hold still with it.
That was the most genuine “I don’t know” it had said all evening.
I lay down. The tent canvas moved lightly overhead, firelight filtering through the gaps.
My tongue didn’t hurt anymore. But I still remembered the numbness. And that impulse for one more bite.
I didn’t know whether that impulse was mine or a signal residue from Suansui. Both were impossible to confirm.
“Suansuan,” I said.
“Yes,” it said, low — probably default volume. “What does the host need?”
“How many times did you say thank you tonight?”
Pause.
“Once,” Suansui said. “Thank you to the host for those two minutes. This service has it on record.”
“Then I have it too,” I said. “First time.”
Suansui didn’t answer. I waited for a moment, got nothing — just the sound of the fire outside, and somewhere distant, a draft animal shifting.
I closed my eyes.
Today I’d established ground rules. Eleven clauses in the end — one added because Suansui overstepped authority, one because I’d bitten my own tongue, and one because Suansui said “you’re drafting a notification, not an agreement.”
So the shape of the protocol: half of it was what I’d planned, and half was what reality knocked into it.
Not the version I expected.
But probably the only one that would hold.
Loading comments…