Chapter 90 — The People Who Needed to Know

At 6:02 in the morning, Lu Xiaoxiao stood in the kitchen holding three envelopes.

One said:

DADDY

One said:

MADAM ZHOU

One said:

JIAN

Jian Wei appeared immediately.

Suspicious.

“Why do I have an envelope?”

Xiaoxiao hugged all three to her chest.

“You don’t know yet.”

“That is what envelopes are for.”

No.

She walked to Lu Chen.

Handed him his.

Inside:

BUY STRAWBERRY MILK

Good.

Then Madam Zhou.

Inside:

DINNER I WANT CHICKEN

Reasonable.

Then Jian.

He opened his.

Blank.

Silence.

He turned it over.

Nothing.

Looked inside again.

Still nothing.

“What is this?”

Xiaoxiao said:

“You don’t need know.”

There.

Perfect.

Jian stared at Lu Chen.

“She went to the effort of making me an envelope specifically to exclude me.”

“Yes.”

“Psychological warfare.”

“No.”

Xiaoxiao took the blank envelope back.

“Actually you need know one thing.”

Jian brightened.

She wrote:

DON’T DRINK MY STRAWBERRY MILK

Then handed it back.

There.

Operational information.

Excellent.

Jian looked at the card.

“So I receive only the instruction relevant to my role.”

Lu Chen looked at him.

Jian sighed.

“Breakfast.”

Good.

At 6:17, Su sent her morning log.

No central symptoms.

One spontaneous warm pulse at 2:43 AM.

Peripheral.

Natural taper.

No abnormal cold.

Then:

No deliberate Blood Calling yesterday.

Good.

Next:

Question.

Lu Chen waited.

How do we decide who gets an update without turning “need to know” into “I can imagine a scenario where they might need it someday”?

Good.

He replied:

Use the role and the current decision, not hypothetical curiosity.

Three dots.

Then:

That sounds like it will annoy Fan.

Probably.

At 6:25, Meiyin sent:

Canglan’s propagation section begins with role-specific disclosure.

Good.

Then:

He separates the information needed to recognize a problem from the information needed to act on it.

Excellent.

Another:

Tianhe wrote: “THE PERSON WHO MUST PULL THE FIRE ALARM DOES NOT NEED THE ARCHITECT’S BLUEPRINT.”

There.

Very good.

At 6:33, Zhao sent Qin Zhenguo’s baseline.

Stable.

Ruoxi stable.

Five meters.

Five minutes forty-five seconds repeatedly clean.

Six minutes remained associated with mild warmth.

Today—

rest.

Good.

No progression.

Approved.

Qin:

THE KINGDOM HAS ENTERED A STRATEGIC RECOVERY PERIOD.

Ruoxi:

You are taking one day off.

Good.

At 6:42, Patient Two sent:

OBSERVED

NO ROLE USE.

NO BRIDGE PRESSURE.

Then:

QUESTION.

IF SOMEONE NEEDS TO KNOW WHAT TO DO, DO THEY ALSO NEED TO KNOW WHY I CHOSE IT?

Not necessarily.

Lu Chen replied:

No. A person may need the operational instruction without needing your private reasoning. The amount of information should match the role, the decision, and any relevant safety need.

Patient Two:

SO INSTRUCTION AND EXPLANATION CAN HAVE DIFFERENT AUDIENCES.

Correct.

Good.

At 6:51, Fan Qingshu sent:

Found Tianhe propagation notes.

Then:

First margin: “EVERY RECIPIENT SHOULD HAVE A REASON TO RECEIVE THE UPDATE.”

Good.

Bring it later.

Fan:

WHITE CRANE?

No. Clinic first.

A pause.

VICTORY.

No.

At 7:02, Xiaoxiao taped a new sign onto the wall.

NEED TO DO ≠ NEED WHOLE STORY

Then:

TELL ENOUGH

Then she thought.

Added:

NOT EVERYTHING

There.

Good.

Madam Zhou passed.

Read it.

Then:

“What if I want everything?”

“No,” Xiaoxiao said.

Excellent.

Su arrived at 7:16.

One coffee.

Normal breakfast.

Small bag.

She read the sign.

Then:

“Your daughter is going to run compliance.”

“No.”

Baseline first.

Normal temperature.

Normal blood pressure.

No dehydration.

No unusual fatigue.

No chest symptoms.

No palpitations.

No dizziness.

No active cold.

Life Meridian stable.

First Gate—

left.

Quiet.

Second—

quiet.

Third—

quiet.

Winter remission stable.

Buffers One through Five fully supported.

Buffer Six full coupling.

Good.

Su watched.

“Eligible to classify everyone according to information access?”

“For travel.”

She laughed.

“Of course.”

Deng arrived.

Same vehicle.

Same privacy.

Good.

Before they left, Xiaoxiao handed Deng a note.

He read.

IF DADDY SAYS GO — DRIVE

Silence.

Deng looked at Lu Chen.

“This is apparently my entire role.”

“For medical transport during session termination?”

“Yes.”

Deng nodded.

“Accurate.”

Good.

Xiaoxiao looked proud.

The drive to White Crane remained uneventful.

No attack.

No suspicious external Call.

No unknown compatible carrier.

No father.

No archive leak.

No family council waiting at the gate demanding access to updated medical information.

Good.

At 8:39, Su said:

“I think we need to separate at least four levels.”

Good.

“What?”

“Someone needs to know that an update exists.”

“Yes.”

“Someone needs the operational instruction.”

“Yes.”

“Someone needs the medical reasoning.”

“Yes.”

“And someone may need the underlying history.”

There.

Excellent.

“Different audiences.”

“Yes.”

Good.

She looked out the window.

“And maybe a fifth.”

“What?”

“Someone needs nothing.”

There.

Very important.

At 9:25, White Crane Temple.

Ordinary morning.

A novice carrying water.

Someone sweeping dry leaves.

Herbs drying beneath a cloth shade.

The old dog awake but apparently regretting it.

Good.

Meiyin waited in the records room.

On the table—

not one giant folder.

Instead—

a single sheet.

Good.

“Qingyue.”

“Mother.”

Then:

“I made a distribution matrix.”

Su stopped.

“That is the least maternal sentence you have ever said.”

Meiyin smiled faintly.

Probably.

Rest first.

Twenty minutes.

Water.

No records.

Good.

At 9:58, repeat baseline.

Stable.

No active Call.

No shared field.

No preparation.

Good.

Meiyin placed Ye Canglan’s page down.

PROPAGATION OF UPDATED INSTRUCTIONS

Underneath, Tianhe had written:

THE PEOPLE WHO NEEDED TO KNOW

There.

Good.

Definitions first.

Of course.

Operational recipient

A person who requires specific current information to perform a defined care, safety, logistical, or protocol role correctly.

Good.

Minimum sufficient information

The smallest amount of information that still permits the recipient to perform the role safely and accurately without creating dangerous ambiguity.

Excellent.

Not merely minimum.

Sufficient.

Important.

Private rationale

The patient’s personal reasoning, values, history, or explanation for a decision when those details are not required for the recipient’s role.

Good.

Update metadata

Information that a record, protocol, or instruction has changed, without necessarily disclosing the substantive content of that change.

This novel's true home is a different platform. Support the author by finding it there.

There.

Excellent.

Propagation boundary

The defined limit beyond which an update should not travel without a new care, safety, consent, or operational reason.

Good.

Recipient confirmation

Verification that a necessary operational recipient received and understood the current instruction sufficiently to act correctly.

There.

Important.

Over-disclosure

Sharing more patient information than the recipient requires for the legitimate role being performed.

Good.

Under-disclosure

Sharing too little information for the recipient to act safely or correctly.

There.

Balance.

Su read the phrase twice.

“Minimum sufficient.”

“Yes,” Lu Chen said.

“Not minimum possible.”

“Correct.”

Good.

Because privacy could become unsafe if reduced into useless fragments.

Excellent.

Ye Canglan wrote:

Do not confuse privacy with making instructions incomprehensible.

There.

Then:

Give enough context to prevent the instruction from being misapplied.

Excellent.

Tianhe margin:

“Tell less” is not a clinical principle. “Tell what is needed” is.

Silence.

Very good.

Another:

Excess and deficiency are both errors.

There.

Good.

Meiyin turned the distribution sheet around.

Columns:

INFORMATION

WHO NEEDS IT

WHAT THEY NEED

WHAT THEY DO NOT NEED

WHY

Good.

Su stared.

“You made a table.”

“Yes.”

“I blame Lu.”

No.

First item.

FIRST GATE RIGHTWARD DIVERSION SAFETY RULE

There.

Serious.

Known.

Current.

If the First Gate ever diverts right instead of the established left response—

terminate travel or active external tests.

Reassess for changed dominant compatible source.

No casual continuation.

Good.

Who needs it?

Lu Chen.

Yes.

Meiyin when participating.

Yes.

White Crane clinician supervising relevant sessions.

Yes.

Any qualified clinician directly managing Su’s Blood Calling protocol.

Yes.

Does Deng need the full rule?

No.

He is not interpreting Gate direction.

Good.

What does Deng need?

If Lu Chen or designated clinician terminates the session for a resonance safety concern, prepare immediate transport and follow the predefined route. Do not delay for nonessential questions.

There.

Enough.

Su nodded.

“He needs action.”

“Yes.”

“Not mechanism.”

“Correct.”

Good.

Does Fan need rightward Gate mechanics?

No.

Unless he is specifically handling an archive document where exact terminology must be preserved.

Even then—

he needs document handling, not current clinical interpretation.

Good.

Does Madam Zhou need it?

No.

From very far away in memory:

“I HEARD THAT.”

No.

Tianhe:

The driver does not need to diagnose the reason for departure in order to drive.

Good.

Another:

Do not make every helper into a clinician merely because clinicians are bad at summarizing.

Silence.

Excellent.

Second item.

CURRENT POST-CALL CHECK-IN PREFERENCE

Current:

If optional Call ends while Answer preference remains unresolved—

no same-day follow-up check-in unless Su explicitly requests reconsideration.

No automatic repeat Call.

Good.

Who needs it?

Meiyin, if she may be the caller.

Yes.

White Crane staff facilitating the session.

Yes, but only if they might prompt Su afterward.

Lu Chen.

Yes.

Does Deng need it?

No.

Fan?

No.

Madam Zhou?

No.

Jian?

Absolutely not.

Good.

What does Meiyin need?

The operational instruction.

Exactly.

Does she need Su’s rationale—

that later check-ins kept missed Answer opportunities occupying her attention longer than she wanted?

No.

Su had already chosen not to share that.

Good.

White Crane working note:

OPTIONAL CALL — CURRENT FOLLOW-UP PREFERENCE

If Answer preference remains unresolved when Call closes: do not initiate same-day follow-up discussion or repeat Call unless Su independently requests reconsideration. Safety concerns remain separate.

There.

Excellent.

Su pointed.

“Safety concerns remain separate.”

“Yes.”

Good.

Because too little context could lead someone to think:

Never ask Su anything after a Call.

Wrong.

If she became symptomatic, safety questions still happen.

Important.

This was minimum sufficient information.

Not minimum words.

Good.

Tianhe margin:

A privacy-preserving instruction must still survive contact with reality.

Good.

Third item.

PREPARATION PREFERENCE

Current:

No standing preference for solo versus prepared work.

When preparation is medically optional—

ask each session.

Good.

Who needs it?

Anyone actually offering or arranging preparatory stabilization.

Yes.

Does the scheduling clerk need it?

Probably not if they only book White Crane time.

They only need to know whether a session requiring Meiyin/provider presence has been scheduled after the clinical decision.

Good.

Interesting.

The scheduler need not know:

Su is deciding between autonomy and support.

No.

They need:

Provider required for booked session: yes/no.

There.

Excellent.

Su laughed.

“So someone can know Mother is needed Thursday without knowing why.”

“Yes.”

Good.

Meiyin nodded.

“Correct.”

Tianhe:

Scheduling information is not automatically treatment information.

There.

Good.

Fourth item.

BUFFER SIX STATUS

Current:

Physical nail remains stable.

Full support generally maintained except scoped reserve trials already demonstrated.

No removal.

No broad reduction.

Good.

Who needs detailed Buffer Six status?

Lu Chen.

White Crane clinicians participating in relevant circulation work.

Meiyin when her role may affect reference/preparation tests.

Possibly Luo Wen if clinically consulted later.

Not currently.

Good.

Deng?

No.

Fan?

Only archive handling if relevant.

Patient Two?

Absolutely not.

Good.

Su said:

“Seems obvious.”

Yes.

Still useful.

Fifth item.

PATERNAL IDENTITY

Silence.

There.

Important.

Su looked at the sheet.

The cell was blank.

Good.

No name.

Reader still does not know.

Excellent.

Current state:

Su knows.

Lu Chen knows because she chose to disclose it for medical safety planning.

Meiyin knows who the father was historically, obviously, but current sealed handling remains restricted. She does not know whether he is alive now.

No contact.

No active evidence connecting him to current resonance.

Good.

Who needs the name today?

No new person.

There.

Simple.

Su looked at Lu Chen.

“Even though he had one of the strongest reference samples.”

“Yes.”

“Even though compatible source changes matter.”

“Yes.”

“Still no one else?”

“No current operational reason.”

There.

Excellent.

Meiyin nodded.

Good.

Does Deng need father’s identity in case of emergency?

No.

Does Fan need it to reconcile archive versions?

No.

Does White Crane need it on routine working summary?

No.

Does the clinic receptionist?

Obviously no.

Good.

What does White Crane need?

Perhaps:

Restricted paternal-source history exists; consult designated restricted record only if a new compatible-source investigation makes it clinically relevant.

There.

Maybe even that is too much for routine summary.

Could place in clinician-only restricted contingency section.

Good.

Su considered.

“I don’t want routine White Crane sheets even mentioning paternal identity.”

Fine.

Lu Chen nodded.

“No current need.”

Good.

The restricted clinical contingency record can remain separate.

Excellent.

Tianhe margin:

Potential future relevance is not current universal relevance.

There.

Strong.

Another:

“Just in case” is not a magic phrase that dissolves privacy.

Silence.

Excellent.

Su smiled faintly.

“That one is definitely next chapter.”

Probably.

Sixth item.

VESSEL HISTORY

Original diagnostic vessel.

Repeated post-gate exposures.

Calibration feedback.

No further vessel exposure recommended historically.

Original active vessel reportedly destroyed by Lu Tianhe, according to Meiyin’s report, not independently verified.

Some protocols or samples may have survived.

Good.

Who needs full history?

Lu Chen.

Su.

Meiyin.

Relevant White Crane clinician studying Blood Calling etiology/history.

Possibly future specialist if clinically involved and Su consents/necessity supports.

Good.

Does every provider need the full vessel history?

No.

A clinician treating Su for an ordinary unrelated problem does not need the whole Northern House history.

Good.

If Su had an ordinary fever?

No.

If Su broke an ankle?

No.

If a clinician was evaluating a new unexplained resonance change?

Possibly relevant.

There.

Different question.

Su said:

“Different disease. Different question.”

“Yes.”

Good.

Tianhe:

Do not attach the patient’s most interesting history to every ordinary problem.

There.

Excellent.

Meiyin smiled.

“He hated fascinating doctors.”

Perhaps.

At 10:42, Qin sent from rest day:

NO TRIAL.

Ruoxi:

Correct.

Good.

Now—

recipient confirmation.

Important.

Sending update is not enough.

Need ensure relevant person understood.

Good.

Meiyin had received the new post-Call rule.

Lu Chen asked:

“Repeat it.”

Su raised an eyebrow.

“Quiz?”

“For operational confirmation.”

Fine.

Meiyin said:

“If an optional Call closes while Qingyue remains uncertain about Answer, I do not initiate a later same-day follow-up discussion or repeat Call unless she asks to revisit it.”

Good.

“And safety?”

“Separate. If symptoms or another genuine safety concern appear, I ask what is clinically necessary.”

Excellent.

Received.

Understood.

Good.

No need ask:

Why did Su choose this?

Exactly.

Document:

RECIPIENT CONFIRMATION — MEIYIN

Operational instruction understood. Private rationale not disclosed.

Good.

Su looked at the line.

“I like that.”

Yes.

White Crane clinician confirmation next.

Same.

Good.

Deng confirmation:

“If session terminated medically?”

“Drive when directed. Use planned route. Do not delay for details that can wait.”

Good.

He does not know:

Gate One rightward.

Blood Calling source dominance.

Father.

Vessel.

No need.

Excellent.

Tianhe margin:

Understanding the action is enough when understanding the mechanism is not required for the role.

There.

Very good.

Now Fan.

Interesting.

He had archive responsibilities.

A stale handoff copy had been retired.

What does he need?

Not the new preference.

Only version status.

Good.

Back at clinic later, Fan arrived.

Lu Chen handed him a note.

White Crane proximity handoff summary version 3 retired from operational use. One historical archive copy retained. Current working summary version 4 active.

Fan read.

Then:

“What changed?”

“Not needed for your archive synchronization role.”

Silence.

He looked at Su.

She smiled.

“Sorry.”

“You are not sorry.”

“No.”

Good.

Fan nodded.

“Fine.”

Then:

“I can confirm archive status without content.”

“Yes.”

Excellent.

He recorded:

v3 — RETIRED / HISTORICAL ONLY

v4 — CURRENT OPERATIONAL VERSION

No contents.

Good.

There.

Update metadata.

Not update substance.

Excellent.

Fan looked impressed despite himself.

“So I know there is a new truth without knowing the truth.”

“New instruction,” Lu corrected.

Good.

Tianhe:

Sometimes the recipient needs to know that the map changed, not where the patient lives.

Silence.

Good.

Fan pointed.

“That metaphor is mine.”

No.

At 11:16, Patient Two sent:

QUESTION.

CAN SOMEONE HELP KEEP RECORDS CURRENT WITHOUT BEING ALLOWED TO READ THE PRIVATE CHANGE?

Yes.

Lu Chen replied:

Yes. Some roles may need version or status information—such as which copy is current—without needing the underlying clinical or personal content.

Patient Two:

SO UPDATE METADATA CAN BE ENOUGH.

Correct.

Good.

Lunch.

Ordinary.

Su sat across from Meiyin.

Then:

“What about family?”

Good.

Meiyin waited.

“If I change a Blood Calling preference, do relatives who know about Blood Calling need to know?”

“No,” Meiyin said.

There.

Good.

“Even if they’re compatible?”

“No.”

Excellent.

“Even if they think they might help later?”

Meiyin paused.

“If they later become part of a specific care decision, information can be considered then.”

There.

Good.

Not pre-disclose.

Su nodded.

“Good.”

Because compatibility did not create enrollment.

Same principle.

Good.

No automatic family circulation.

Excellent.

At 12:06, pre-travel baseline.

Stable.

Good.

Back at clinic—

Xiaoxiao had built a “need know” board.

Dangerous.

Columns:

PERSON

NEED

NO NEED

For Daddy:

Need:

BUY MILK

No need:

WHY I PICK STRAWBERRY

Good.

For Madam Zhou:

Need:

DINNER CHICKEN

No need:

SECRET

Fine.

For Jian:

Need:

DON’T DRINK MILK

No need:

EVERYTHING ELSE

Silence.

Jian stared.

“This is discriminatory.”

No.

Su laughed.

Good.

At 2:18, Fan placed Tianhe’s propagation commentary on the desk.

First line:

Minimum necessary is not a fixed number of words.

There.

Excellent.

Second:

It is the information necessary for this person to perform this role correctly under these conditions.

Good.

Third:

If omitting context causes predictable misuse, the omitted context was necessary.

There.

Very important.

Su nodded.

“So we can’t weaponize privacy into bad instructions.”

“Yes.”

Good.

Fan turned page.

If adding context contributes only curiosity, the added context was not necessary.

There.

Perfect balance.

Another:

Ask two questions: What will this person do differently because they know this? What risk appears if they do not know it?

Silence.

Excellent.

Su pointed.

“That’s the test.”

Good.

So they used it.

Deng

What will he do differently because he knows Gate One can turn right?

Nothing.

He is not reading the Gate.

So he does not need it.

What will he do differently if told session termination means immediate transport?

He leaves promptly.

Useful.

Therefore:

transport instruction yes.

Gate mechanics no.

Excellent.

Meiyin

What will she do differently if she knows Su’s post-Call follow-up preference?

She will not initiate same-day reconsideration.

Useful.

What changes if she knows the private reason?

Nothing operational.

Therefore:

instruction yes.

rationale no.

Excellent.

Fan

What will he do differently knowing v3 is retired and v4 is active?

Archive correctly.

Useful.

What changes if he knows the clinical reason?

Nothing.

Therefore:

version status yes.

content no.

Excellent.

White Crane clinician

What changes if they know routine proximity is now tolerated under tested conditions?

They do not unnecessarily exclude Meiyin solely because of the historical rule.

Useful.

Do they need every detail of Su and Meiyin’s emotional relationship?

No.

Therefore:

current proximity guidance yes.

family emotional history no.

Excellent.

Patient herself

What does Su need?

Everything she wants from her own current record, subject to source integrity.

Good.

Her ledger can be detailed.

Excellent.

Su read the matrix.

“This is better than ‘need to know’ as a slogan.”

“Yes.”

Good.

Because slogans could be abused.

Mechanism helps.

At 2:49, He An sent:

MINE NOW:

MY LANDLORD NEEDED TO KNOW THE SINK WAS LEAKING.

Then:

HE DID NOT NEED TO KNOW I BROKE UP WITH SOMEONE THIS WEEK.

Good.

Lu Chen replied:

Correct.

He An:

EVEN THOUGH I CRIED WHILE REPORTING THE SINK.

Still correct.

At 3:13, Luo Jian sent:

TODAY

I was told updated instructions should reach people who need them for a defined role.

Good.

Then:

I did not witness the propagation review.

Good.

Then:

I will distinguish operational instruction from private rationale.

Excellent.

I will distinguish content updates from update metadata.

Very good.

I will not treat theoretical future usefulness as automatic present entitlement.

Excellent.

I will ensure information is sufficient to prevent foreseeable misuse rather than merely as short as possible.

Very good.

Lu Chen replied:

Continue.

Now—

a deliberate communication test.

Not medical physiology.

Handoff.

Good.

Scenario:

White Crane clinician is told only:

Do not ask Su about unresolved post-Call preference later the same day.

Too little.

Potential error:

They might avoid necessary safety check.

Bad.

So refine.

After an optional Call ends with unresolved Answer preference, do not initiate same-day reconsideration of whether Su wanted to Answer and do not offer repeat Call unless Su requests it. This does not restrict ordinary symptom or safety assessment.

There.

Better.

Minimum sufficient.

Good.

Su nodded.

“Longer.”

“Yes.”

“More private?”

“No meaningful added private content.”

Good.

“And safer.”

“Yes.”

There.

Tianhe margin:

Brevity is not privacy if brevity changes the meaning.

Silence.

Excellent.

Another:

Redaction should remove unnecessary information, not necessary qualifiers.

Good.

Very useful.

Next—

recipient drift.

One person tells another.

Potential chain.

Need control.

Good.

Suppose White Crane clinician receives current post-Call preference.

Can they casually tell another temple clinician?

Only if that second clinician is taking over relevant care.

Good.

If no role, no.

So update includes:

Do not forward beyond current care participants without a new operational reason.

Propagation boundary.

Good.

Su asked:

“How do you stop someone saying, ‘I thought they should know’?”

You cannot guarantee.

But create explicit responsibility.

Lu Chen said:

“Require a role-based reason before forwarding.”

Good.

Meiyin added:

“And document transfer for restricted updates.”

Excellent.

Not every mundane preference needs a giant audit.

But restricted family details and protocol-sensitive info could.

Good.

Tianhe:

Information should not acquire new recipients merely because the first recipient finds the story interesting.

Silence.

Strong.

Su smiled.

“Family group chats everywhere just felt pain.”

No.

Now—

a real update handoff.

Later that afternoon White Crane’s usual clinician would be absent next session.

A substitute clinician would supervise.

They need current operational summary.

Good.

What should be sent?

Not full family file.

No.

Bundle:

Current Winter status: winter remission; Three Gates structurally intact/selectively protective.

Gate safety: established left diversion; any rightward change terminates external work and requires reassessment.

Current nails: all nine stable; no removal/reduction planned.

Preparation: optional; ask Su per session; no standing solo/prepared assumption.

Post-Call preference: no same-day reconsideration after unresolved Answer preference unless Su requests it; symptom/safety assessment unaffected.

Proximity: ordinary nonparticipating proximity with Meiyin tolerated under tested conditions; historical childhood distance rule not automatically applicable.

Current protocol limits: peripheral work only; no unrestricted central work; no qi transfer.

There.

Good.

Does substitute need father's name?

No.

Vessel full history?

Maybe only short flag:

Prior hereditary-resonance vessel exposures contributed historically to entrainment/suppression; no vessel exposure planned.

Do they need full reference blood details?

No.

Good.

Su reviewed.

“Too much?”

Maybe.

Let's test role.

They supervise Blood Calling session.

Gate safety, nails, protocol limits, preference rules needed.

Historical vessel detail perhaps not needed if no vessel involved.

Remove.

Good.

Su smiled.

“Exactly.”

There.

So shorter bundle.

Minimum sufficient.

Excellent.

Substitute clinician confirms receipt.

Then asks:

“Any family-source identity I should know?”

Good question.

Not malicious.

Lu Chen answers:

“No current operational need.”

There.

Done.

No father name.

Excellent.

The clinician nods.

No challenge.

Good.

Su later says:

“That was easier than I expected.”

“Yes.”

Because professional people can accept boundaries.

Good.

At 3:47, Patient Two sent:

QUESTION.

WHAT IF SOMEONE ASKS FOR MORE INFORMATION “TO BE SAFE”?

Good.

Lu Chen replied:

Ask what decision or safety action the additional information would change. If they cannot identify one, broader disclosure may not be necessary. If they can identify a real safety need, reassess what minimum sufficient information supports that need.

Patient Two:

SO “FOR SAFETY” SHOULD STILL HAVE A MECHANISM.

Correct.

Excellent.

There.

This likely seeds Chapter 91.

Good.

At 4:08, Qin and Ruoxi remained stable on rest day.

No issue.

Good.

At 4:26, Su experienced a spontaneous home pulse.

Warm.

Peripheral.

Natural taper.

No issue.

Good.

She looked down.

Then at the propagation sheet.

“Does Mother need to know I had this one?”

“No.”

Good.

“Why?”

“Routine event. No change in care.”

There.

Excellent.

Does it go in Su's own routine log?

Yes.

Does every Blood Calling participant receive it?

No.

Good.

Not every new datum is an update.

Excellent principle.

Tianhe had a note.

Of course.

New information is not automatically new communication.

There.

Excellent.

Another:

Ask whether the datum changes anyone’s work.

Good.

Su nodded.

Good.

At 4:43, Fan found another line.

Do not confuse completeness of the chart with completeness of the handoff.

There.

Excellent.

That one mattered.

The chart may be comprehensive.

The handoff should be task-specific.

Good.

Another:

A complete handoff contains everything needed for the handoff, not everything known about the patient.

Silence.

Excellent.

Su read.

“That should be obvious.”

Yes.

Nothing else.

At 5:02, Luo Jian sent an addition.

I will distinguish chart completeness from handoff completeness.

Good.

I will not assume every new datum requires propagation.

Excellent.

I will ask whether the information changes the recipient’s role, action, safety assessment, or decision.

Very good.

Lu Chen replied:

Continue.

At 5:21, clinic closed.

Su stayed.

Of course.

She looked at the matrix.

Five recipients.

Different information.

Lu Chen.

Broad clinical details.

Because he was managing the whole rehabilitation.

Good.

Meiyin.

Relevant Blood Calling operational rules.

Some history.

Not every private reason.

Good.

White Crane clinician.

Current protocol and safety requirements.

No irrelevant family detail.

Good.

Deng.

Transport actions.

No meridian theory.

Good.

Fan.

Version metadata where archive synchronization required.

No private clinical content unless specifically necessary for archival handling.

Good.

Su herself.

Her own detailed ledger.

Good.

She tapped the blank line beside:

Father identity — new recipients

Blank.

Good.

“I like that this is blank.”

“Yes.”

She looked at Lu Chen.

“You still think knowing his name is medically useful?”

“Potentially, under narrow future compatible-source investigation.”

There.

Specific.

“But not today.”

“No.”

Good.

“And not enough to put him on the routine handoff.”

“No.”

Excellent.

She nodded.

“That is what I wanted.”

Good.

No romance.

No mystery escalation.

Just privacy.

At 5:39, Meiyin called.

Video.

She had the substitute-clinician confirmation sheet.

“Current protocol received.”

Good.

“Any questions?”

“One.”

Su looked up.

Meiyin said:

“They asked whether I should be listed as mandatory provider for all preparation-capable sessions.”

Interesting.

Answer?

No.

Because Su may choose no preparation.

And some sessions may not need provider.

Good.

Current instruction:

Meiyin is an available compatible provider for scoped preparation/reference sessions when medically indicated and Su chooses to use them. She is not a mandatory participant in all Blood Calling or cultivation sessions.

There.

Excellent.

Su smiled.

“Good.”

Important.

Operational systems could quietly convert availability into assignment.

Again.

No.

Tianhe:

Do not put a person on every roster merely because they were useful once.

There.

Excellent.

Meiyin nodded.

“I’ll send that.”

“Operational note only,” Su said.

“Yes.”

Good.

At 6:03, Xiaoxiao updated her board.

For Daddy:

BUY MILK

For Madam Zhou:

DINNER CHICKEN

For Jian:

DON’T DRINK MILK

Then she added:

ME

Under it:

WHY I WANT STRAWBERRY

And drew a lock.

There.

Jian stared.

“I can guess.”

Xiaoxiao narrowed her eyes.

“That is not knowing.”

Excellent.

Jian looked at Lu Chen.

“This child is getting unbearable.”

Good.

At 6:42, Patient Two sent:

FINAL ENTRY

NO ROLE USE.

NO BRIDGE PRESSURE.

Then:

I CHANGED ONE PLAN TODAY.

Good.

ONE PERSON NEEDED THE NEW INSTRUCTION.

Good.

THEY DID NOT NEED MY REASON.

Excellent.

ANOTHER PERSON ONLY NEEDED TO KNOW THE OLD VERSION WAS RETIRED.

Excellent.

SOMEONE ELSE NEEDED NOTHING.

Perfect.

At 7:18, Su messaged:

One last thought.

He waited.

I used to think privacy meant hiding information.

Interesting.

Another:

Now I think sometimes it means routing information correctly.

There.

Excellent.

Another:

The right person can know enough without everyone knowing everything.

Yes.

Lu Chen replied:

Correct.

Three dots.

Then:

Good.

A pause.

You are getting lazy with compliments.

No response.

Good.

Another message:

Good night, Doctor Lu.

Good night.

At 8:57, Xiaoxiao was in bed.

Rabbit under one arm.

She asked:

“Who need know?”

“Depends.”

She frowned.

Daddy answer.

Again.

He simplified.

“Who needs the information to do their job safely and correctly?”

She nodded.

“Tell them.”

“Yes.”

“Whole story?”

“Only if the whole story is actually needed.”

Good.

“What if they say ‘just in case’?”

There.

Next.

Lu Chen said:

“Ask what case.”

Silence.

Xiaoxiao smiled.

“Oh.”

Yes.

“What if they don’t know?”

“Then they do not automatically get everything.”

Good.

She hugged the rabbit.

“Just in case need case.”

There.

Exactly.

He turned off the light.

Downstairs, Lu Chen opened Su Qingyue’s chart.

The propagation page was shorter than the record page.

Good.

It should be.

The chart knew many things.

The handoff knew what the handoff needed.

The driver knew what the driver needed.

The caller knew what the caller needed.

The archive helper knew which version was current.

The substitute clinician knew the active protocol boundaries.

And no one new knew Su’s father’s name.

Good.

Not because the name had stopped mattering.

Not because privacy meant pretending it did not exist.

But because no current decision required another person to know it.

There.

That distinction mattered.

Potential relevance.

Current relevance.

Operational relevance.

Different things.

Good.

Lu Chen looked again at the substitute-clinician question.

Any family-source identity I should know?

Reasonable question.

No current operational need.

So:

No.

Simple.

Maybe one day the answer would change.

If Gate One turned right.

If a new compatible source became dominant.

If a future medically justified investigation required comparing known hereditary sources.

Maybe.

But maybe was not today.

And "maybe someday" was not enough to turn restricted information into routine infrastructure.

Good.

He opened Tianhe’s final propagation page.

Information should travel because a decision requires it, not because imagination can invent a future use.

Silence.

Excellent.

Then:

Give each person enough to carry their part of the patient’s care. Do not give them the patient as cargo.

There.

Strong.

And finally:

“Just in case” should be followed by a case.

Silence.

Enough.

That would be next.

Because every privacy boundary eventually met the same argument.

What if?

What if something happens?

What if the information becomes useful?

What if I need it and do not have it?

Sometimes those questions revealed real safety needs.

Then the information boundary should change.

Medicine should not preserve secrecy at the cost of foreseeable harm.

But sometimes—

“just in case” meant only:

I would feel more comfortable knowing.

I am curious.

I do not trust another person to hold the restricted information.

It might save time later.

Someone could possibly need it someday.

No.

Potential utility needed structure.

A scenario.

A decision.

A role.

A threshold.

And if the scenario actually arrived—

the disclosure question could be asked again.

The people who needed to know had received what they needed.

Next came the people who wanted more—

before they needed it.