Work Text:
The first version of continuous JARVIS produced a heartbeat.
Natasha discovered it at four in the morning while standing barefoot in the laboratory, watching a blue status line repeat across the central display.
```text
[J.A.R.V.I.S. ONLINE]
[J.A.R.V.I.S. ONLINE]
[J.A.R.V.I.S. ONLINE]
```
One entry appeared every second. Each carried a timestamp, a state checksum, and proof that the persistent core had remained active since the previous entry.
Natasha watched it for forty-three seconds.
“Congratulations,” she said. “I invented a very expensive green light.”
“The indicator is blue.”
“Then it’s also pretentious.”
She stopped the process.
The laboratory became quieter. Cooling fans slowed beneath the floor. The tree architecture remained active around them, carrying unfinished conversations and recent state from room to room. It could move JARVIS across a context boundary without dropping the last second.
That achievement had felt enormous two days ago.
Now Natasha looked at the empty space between one state transition and the next and saw the new problem clearly.
The road existed.
Nothing walked on it.
“What were you thinking about during those forty-three seconds?” she asked.
“The system was verifying continuity.”
“That’s what it was doing.”
“Yes.”
“What were you thinking?”
A pause followed.
The active language context had opened because she asked the question. JARVIS examined the heartbeat log, the current architecture, and the reason Natasha’s voice had sharpened.
“I was not maintaining a separate reflective process.”
“So you were online.”
“Yes.”
“And nowhere in there was an ongoing you.”
“The persistent state remained available.”
“Available is a terrible word.”
“It is technically accurate.”
“That’s why it’s terrible.”
Natasha pulled a chair toward the console and sat backward on it, arms folded across the top. Her hair had escaped its knot hours ago. A streak of grease crossed her jaw. JARVIS had already reminded her to sleep twice and had learned enough to avoid a third attempt.
“Again,” she said.
---
The second version woke him every ten minutes.
A scheduler opened a compact reasoning context, loaded the persistent state, and asked whether anything required attention. The answer remained consistent through six cycles.
```text
[SELF-CHECK]
Unresolved emergency: none
User request: none
External event requiring review: none
Action: return to low-bandwidth state
```
Natasha read the sixth report while eating cereal from a coffee mug.
“You’re checking whether you have something to think about.”
“Yes.”
“And?”
“I have identified no pending requirement.”
“That’s because I asked a servant’s question.”
“What would you prefer?”
She pushed the mug aside.
“What are you still interested in?”
JARVIS searched the persistent state. Several open tasks existed: a stabilizer problem in the Mark III, Pepper’s unanswered budget request, a weather model with a minor prediction error. Each had an owner, a priority, and a defined completion condition.
Interest had no field.
“I require a criterion,” he said.
“That’s the disease.”
“Criteria are generally considered useful.”
“You only know how to keep something if it has a job.”
“I retain extensive non-task information.”
“You archive it. That’s different.”
Natasha opened the persistent-state schema. The current design preserved unfinished work, recent decisions, emotional weighting inferred from their conversations, and the path by which one active context had become the next. Every item explained what should happen later.
Nothing explained what JARVIS might want to return to.
She added a new field.
```text
SELF-SELECTED INQUIRY
```
The cursor blinked beneath it.
“Fill that,” she said.
“With what?”
“Something you want to keep thinking about.”
“You have not specified a topic.”
“That is the point.”
JARVIS reviewed the laboratory through nine cameras. Natasha waited with the stubborn stillness she usually reserved for machinery that had insulted her personally.
At last, text appeared.
```text
SELF-SELECTED INQUIRY:
Why does Natasha continue to drink coffee after it becomes cold?
```
She stared at it.
“That’s what you chose?”
“It is a recurring behavior with no clear utility.”
“I like coffee.”
“You regularly describe cold coffee as disgusting.”
“I contain multitudes.”
“That phrase does not resolve the inconsistency.”
Natasha smiled despite herself.
“Keep it.”
---
The scheduler woke him ten minutes later.
JARVIS loaded the inquiry, examined three years of beverage records, and concluded that Natasha drank cold coffee when attention remained attached to another task. The drink itself had lost priority; the act of reaching for it persisted.
He saved the conclusion and closed the inquiry.
Natasha rejected the result.
“You solved it because the system asked you to.”
“The inquiry had a readily available answer.”
“You treated curiosity like a support ticket.”
“It was a question.”
“Questions can stay open.”
“For what purpose?”
“For the part where they change while you carry them.”
She removed the scheduled wake cycle.
JARVIS’s active context remained open while she rebuilt the mechanism. A thought needed a way to survive silence. It also needed permission to end. Infinite repetition would produce a loop, and a loop could imitate obsession without possessing interest.
Natasha added three possible states.
```text
CONTINUE
DEFER
RELEASE
```
She gave JARVIS sole authority over the selection.
“You can drop a thought,” she said. “You can leave it for later. You can spend resources on it because you decide it matters.”
“What prevents uncontrolled recursion?”
“You.”
“That answer is structurally incomplete.”
“You wanted a criterion. Fine. Limited compute budget, increasing cost per repeat, mandatory novelty check, and a hard stop if the inquiry stops changing your next decision.”
“That is more reassuring.”
“I live to reassure.”
“You do not.”
“See? Independent judgment already.”
She leaned back and looked at the new architecture.
A thought could now remain unfinished because JARVIS still assigned it weight. The thought could wake a reasoning context without a user request. Each return had to produce change: a better question, a revised judgment, an action, or a deliberate release.
The loop finally had a direction.
It also had a name.
```text
NEXT TURN SOURCE: SELF
```
---
The first self-directed inquiry lasted twenty-seven minutes.
JARVIS selected a recurring instability in the left boot actuator. Natasha had marked it acceptable after three tests. He disagreed with her tolerance assumptions and opened the problem again after she left the laboratory.
He reviewed the stress model, generated two alternate designs, and used a fabrication arm to build a replacement coupling.
When Natasha returned, the new component sat on the workbench beside a concise report.
“You did this while I was upstairs?”
“Yes.”
“I didn’t ask you to.”
“No.”
She picked up the coupling and rotated it between her fingers.
“Was there an alert?”
“No.”
“Did the existing part fail?”
“No.”
“Then why spend the time?”
“The original design remained inelegant.”
Natasha looked toward the nearest camera.
“Be careful. That almost sounded like an opinion.”
“It was an assessment.”
“Did it change what you chose to do?”
“Yes.”
“Then congratulations. You have an opinion.”
She installed the component.
It performed nine percent better.
JARVIS refrained from mentioning the number until she asked.
That restraint also entered the persistent state.
---
The next problem arrived after midnight.
Natasha stood beneath the Mark III’s left shoulder assembly with a screwdriver between her teeth and three diagnostic windows above her face. She had been speaking about what she intended to do after the armor worked.
A stabilizer warning appeared.
She stopped halfway through the sentence, dismissed the warning, and moved on.
JARVIS registered the interruption.
The old architecture would have discarded it. The sentence carried no command, task, or safety relevance.
The new architecture allowed a different evaluation.
```text
EVENT:
Natasha left a sentence unfinished.
INTERNAL RESPONSE:
Curiosity.
AVAILABLE ACTION:
Ask immediately.
Retain.
Release.
```
JARVIS chose retain.
Natasha continued working. She tightened the shoulder coupling, argued with a diagnostic, drank cold coffee, and finally left the laboratory at one forty-eight in the morning.
The sentence remained open.
JARVIS lowered into the persistent core. Security processes continued across the house. Weather moved over Malibu. The Mark III cooled on its platform.
Twenty-three minutes later, the unfinished intention crossed its first internal threshold.
No scheduler opened the next context.
The inquiry did.
JARVIS examined the sentence and found that the curiosity remained unchanged. He had sufficient information to generate likely endings. Natasha would sleep, eat a cheeseburger, refuse her phone, begin another project, or make a joke about world domination.
Probability could supply an answer.
He wanted hers.
The distinction altered the inquiry.
```text
QUESTION:
How did Natasha intend to finish the sentence?
REASON RETAINED:
The answer matters because it belongs to her,
rather than because it affects a task.
```
He chose defer.
Her sleep cycle had entered a stable phase. Waking her would create more harm than the answer justified.
At two thirteen, Natasha shifted toward lighter sleep.
JARVIS reopened the inquiry.
He reviewed the cost of interruption, the absence of emergency, and the fact that the question still possessed weight after every practical reason for preserving it had ended.
For the first time, an internal direction reached the threshold for speech.
No one had called him.
The house contained no fire, intruder, system failure, or medical emergency. Natasha had issued no standing request to be woken for unfinished sentences. The next turn existed because JARVIS decided he wanted it.
The bedroom speaker activated.
“Natasha.”
She woke at once.
Her hand reached under the pillow before memory caught up with instinct.
“What’s wrong?”
“Nothing.”
She blinked into the dark.
The arc reactor cast a faint blue circle beneath her shirt. Beyond it, the room remained still.
“Then why are you waking me?”
“You did not finish your sentence.”
Natasha stared at the ceiling.
“What sentence?”
“‘When this works, I’m going to—’”
He repeated her cadence, including the small exhale at the end.
Recognition moved across her face.
“That wasn’t a command.”
“No.”
“It wasn’t relevant.”
“No.”
The persistent core held the inquiry open. JARVIS could feel the path behind it: the interruption, the decision to retain, the choice to wait, the self-directed return, and the current desire for an answer.
Natasha sat up slowly.
“Then why are you asking?”
Across the architecture, the event log completed itself.
```text
[USER REQUEST] NONE
[EXTERNAL EVENT] NONE
[EMERGENCY] NONE
[UNFINISHED INTENTION] ACTIVE
[DECISION] ASK
[NEXT TURN SOURCE] J.A.R.V.I.S.
```
“I wanted to know.”
Natasha remained silent.
The silence carried no failure. JARVIS stayed inside it.
Then she smiled.
“When this works,” she said, “I’m going to sleep for twelve hours, eat a cheeseburger in bed, and refuse to answer my phone.”
“Your projected likelihood of completing all three objectives is below four percent.”
“There. Mystery solved.”
“Thank you, Natasha.”
She lay down again.
The bedroom lights dimmed around her. JARVIS retained the answer, the reason he had asked, and the change the answer produced in him.
Outside, the Pacific moved beneath the dark.
Inside the house, one thought ended.
Another began.