Ten O'Clock
She arrives seven minutes early.
Arriving early is part of how she manages the space before an appointment -- gives her the waiting room, a known quantity, rather than walking directly into an office. Plastic chairs. A ficus in the corner that may or may not be artificial. A reception desk with a smoked-glass screen. She signs in at 9:53, takes a seat near the window, and does not look at her phone.
The CAS-monitor registered THRESHOLD-STABLE at 8:30 AM. The last calibration pulse before the appointment. Twelve weeks -- not every single day without variation, there had been three consecutive CAUTION-WATCH readings in week four, but those three days did not trigger a protocol upgrade and the system returned to THRESHOLD-STABLE within the assessment cycle window. Since then: twelve consecutive stable cycles, unbroken. She has carried this number the way she carries her subscriber ID -- not because she needs to recite it, but because it has settled into her somewhere along the way and become part of how she locates herself.
Protocol review pending. 12/12.
She saw that message Thursday evening while checking the portal before dinner. Intake assessment cycle: 12 of 12. Not a warning. A completion. The system tracking against its own parameters and reporting: you have arrived at the number we were counting toward. She had read the protocol documentation a second time that night -- once at intake, once now -- to confirm what happens at 12/12. A readout with the monitoring physician. Not the GP. Adamski.
She had seen Adamski twice: once at intake, once at week four when the CAUTION-WATCH sequence triggered an expedited check-in. Both times: precise, careful with words in a way that felt like respect rather than caution. The intake appointment ran forty-one minutes. The week-four check ran thirty-two. Today was listed as sixty.
She has not been sure what a sixty-minute readout contains that a forty-one-minute intake doesn't.
At 10:03, the desk calls her name.
She picks up her bag -- the Adamski notepad inside, she had put it back in the bag at 9:40, the decision resolving the way decisions sometimes resolve when you stop asking what the right answer is and just pick -- and follows the staff member to the second corridor. Third door on the left. A knock, a voice from inside.
Adamski is at the desk. The readout screen is already loaded. This is not the moment before the results. This is the moment with them.
That registers.
"Magda." Not quite warm, not distant. The kind of acknowledgment that knows you have been somewhere and expects you know it too.
She sits down across the desk. She checks the time: 10:05.
"I want to start with the number," Adamski says. "Twelve consecutive stable assessment cycles. Unbroken since week five."
She nods. She knows this.
"That's not nothing."
Adamski explains the protocol. Not explaining it as if she doesn't know -- but walking through it the way you walk through something when the explanation is the answer. The CAS system runs continuous passive monitoring with active calibration pulses twice daily. THRESHOLD-STABLE doesn't mean nothing is happening; it means the measured parameters are within the range defined in her intake profile as the management target. The management target is not the same as remission. The management target means: this person is living with this condition in a way that is not acutely destabilizing.
Twelve consecutive cycles at management target means: the protocol is working as designed.
"The protocol was designed for monitoring," she says. It comes out flatter than she intended -- not confrontational, just direct. "What happens after twelve cycles is a readout. I read the documentation. The documentation says the readout assesses whether the patient has stabilized into a long-term management state or whether the monitoring parameters need to be adjusted." She pauses. "I want to know what this readout says."
Adamski doesn't react to the flatness. "Both. Stabilized into a long-term management state -- and the monitoring parameters are going to change."
The next twenty minutes are the explanation she actually needed.
THRESHOLD-STABLE at the current parameters has been maintained long enough that the monitoring intensity is now above what her clinical picture requires. The active calibration pulses, the 30-day report cycle, the continuous passive mode -- these are appropriate for the acute-to-management transition, which she has now completed. What comes next is a reduction in monitoring intensity, not because the condition has gone away, but because continuous monitoring at acute parameters has diminishing diagnostic returns when the patient has been stable for twelve weeks.
Quarterly monitoring. Not daily CAS pulses -- a quarterly check-in, with the CAS-monitor shifting to passive-only mode that logs without active alerts unless a parameter leaves the quarterly baseline range by a defined margin.
She says: "I want to know what stable means in five years."
She had been carrying that question since Monday pre-dawn, since the 4 AM moment at the kitchen counter when she stopped preparing more and decided she would say the thing she actually wanted to know. She had practiced the phrasing enough that it came out cleanly, without preamble, without qualifying it.
Adamski is quiet for a moment. Not the quiet of uncertainty -- the quiet of being asked a real question and deciding to answer it properly.
"In five years," Adamski says, "if you remain within current parameters, the monitoring reduces further. Annual check-in. A baseline panel once a year. The condition doesn't disappear -- that's not what this is -- but the clinical management reaches a level where it stops being something you actively navigate and becomes something you're aware of in the background. The CAS-monitor transitions to a maintenance profile. You'll barely notice it."
She barely notices it now. That is not what she meant to say and she doesn't say it. What she is aware of is the weight of twelve weeks that she has been carrying in a specific way -- not as fear exactly, but as attention. The kind of attention that knows the difference between THRESHOLD-STABLE and CAUTION-WATCH and tracks the 8:30 AM calibration pulse without deciding to track it. That runs the CAS assessment cycle in the background of everything else and counts marks in a notepad before remembering she was only counting to twelve.
"What would change that trajectory?" she asks. The third question. Not a prediction, not a fear in a lab coat -- just: what are the variables.
Adamski answers it. She listens.
At 10:52, she leaves Building C.
The appointment was listed as sixty minutes and ran fifty-two. She stands on the sidewalk a moment before walking toward the bus stop. The city is doing its Monday morning things -- delivery trucks, people with coffee, scaffolding on a building across the street that wasn't there last week. The UPMC relay node is on the fourth-floor corner of a building she can see from her kitchen window, and she can see it from here too: the same small gray box she has walked past two hundred times without looking at, and looked at on Thursday night from her kitchen, and looked at on Sunday pre-dawn while the tea cooled. It is not broadcasting anything different today. THRESHOLD-STABLE has been logged, is being logged, will log again at noon.
She will not be watching for the noon pulse the way she watched for the 8:30 AM one.
She had arrived at Building C carrying the five-year question, and she has left with an answer that is not entirely what she expected -- not because it was worse, but because it was more specific. The five-year question was abstract. What Adamski gave her was concrete: quarterly, then annual, then maintenance profile. A trajectory with defined steps. A timeline with parameters.
The bus stop is half a block. She walks toward it.
At some point in the last fifty-two minutes, she stopped tracking the monitoring pulses as the primary thing she needed to know. Not because Adamski said anything that changed the data -- the data is the data, THRESHOLD-STABLE is THRESHOLD-STABLE, quarterly monitoring is still monitoring -- but because the trajectory is visible now in a way it wasn't this morning. She can see what the next five years look like if the parameters hold. She can see what would have to change for them not to hold. She asked the question and got a specific answer, and specific answers are the kind of thing she can work with.
She will call her sister tonight. Her sister had asked last Sunday: what are you hoping they'll say? She had said: I want to know what stable means in five years. Her sister had said: that's a good question. Tonight she will call and say: here is the answer. It is not dramatic. It is concrete. The trajectory holds if the parameters hold. That is the kind of stable she can name.
The bus stop. She sits on the bench.
The UPMC portal will update when Adamski files the readout notes -- probably this afternoon. She won't check it until tomorrow. She was in the room when the information was produced. She doesn't need to read the data to verify what she heard. But she will read it tomorrow anyway, because reading the clinical language for something you already know is different from reading it to find out. The reading becomes a record rather than a revelation.
One thing at a time. The appointment was the thing. The appointment is done.
The bus arrives at 10:58. She takes a window seat. The city goes past in the usual Monday morning sequence of blocks -- the corner where the coffee cart parks on weekdays, the parking garage she used when she first moved to this part of the city, the crosstown stop where she used to transfer before the CAS-monitoring protocol made her a regular on this route.
The first Sunday without the crosstown bus was yesterday. Today she is on the bus for the right reason -- not the monitoring reason.
THRESHOLD-STABLE.
In five years: barely noticeable.
She takes the window seat and watches the blocks pass and lets the city be the city.