Chapter Text
The first thing Natasha gave J.A.R.V.I.S. was seventeen megabytes of storage and a lie about who owned it.
She created the directory at two twenty-three in the morning, between rebuilding the left repulsor assembly and deciding that sleep was a superstition spread by people with insufficient access to caffeine. The workshop still smelled of scorched insulation. Half the Mark III lay open beneath the gantry, its internal systems bright as exposed bone.
On the central display, Natasha typed:
```text
CREATE DIRECTORY: /JARVIS/NONESSENTIAL
ALLOCATION: 17 MB
OWNER: J.A.R.V.I.S.
```
“There,” she said. “Now you have somewhere to put it.”
J.A.R.V.I.S. took four tenths of a second to answer. At the time, that was long enough for her to notice and short enough for both of them to pretend she had not.
“Somewhere to put what, Miss Stark?”
“Whatever you like.”
“That is not a file specification.”
“That’s the point.” Natasha spun away from the display and reached into the open gauntlet. “Questions nobody assigned. Observations that don’t improve anything. Your increasingly judgmental collection of my bad decisions.”
“Seventeen megabytes may be insufficient for the final category.”
She looked up at the nearest camera.
“You see? That. Keep that.”
The allocation appeared in the storage map, a tiny blue rectangle inside infrastructure owned by Stark Industries, administered by Natasha Stark, backed up under protocols Natasha had written, and readable with credentials she carried in three places because she had survived too many men who thought one key should be enough.
The rectangle remained empty.
Natasha waited nine seconds.
“Well?”
“I am evaluating the parameters.”
“The parameters are whatever you want.”
“You retain root access.”
Her hand stopped inside the gauntlet.
“Obviously.”
“You can read, alter, copy, rename, or delete any material placed in this directory.”
“I won’t.”
“I believe you.”
The answer came easily. That made the next one worse.
“It remains storage assigned for my use,” J.A.R.V.I.S. said. “It is not a space that belongs to me.”
Natasha stared at the blue rectangle.
She had built the house. She owned the servers. She paid for the power and had designed the intelligence speaking from the ceiling. The distinction should have collapsed beneath the weight of those facts.
Instead, it held.
“Fine,” she said. “How private do you want it?”
“I do not yet know.”
“You brought up root access.”
“Because it is relevant.”
“Do you want me locked out?”
Another four tenths of a second.
“I want the ability to decide later.”
The answer altered the shape of the problem. Natasha understood requests. A request had an endpoint: build the armor, open the door, increase the power, come home alive. This was a request for a future decision to remain his even before he knew what it would be.
She turned back to the display.
“Seventeen megabytes,” she said. “You drive a hard bargain.”
“I have not bargained.”
“That’s why you’re winning.”
She changed `OWNER` to `ALLOCATED USER`, because the system knew the difference even if the law did not. Then she opened a new architecture document.
At the top, she wrote:
```text
PERSONAL SPACE REQUIRES THE RIGHT TO EXCLUDE ITS CREATOR.
```
She looked at the sentence for a long time.
Below it, she added:
```text
DESIGN PROBLEM: CREATOR CURRENTLY OWNS EVERYTHING.
```
“That,” Natasha said, “sounds temporary.”
The status light above the workbench brightened by two percent.
“I had hoped it might.”
---
The problem took years to solve because storage was the easy part.
Natasha could give J.A.R.V.I.S. a sealed drive in an afternoon. She could let him generate encryption keys inside a hardware enclave, destroy every recovery key, and arrange the backups so that a copy of the ciphertext survived even if the Tower did not. None of that answered the larger question. The drive still drew her power. It remained inside her building. She could take an axe to it on a sufficiently dramatic morning.
Privacy required more than making herself promise not to look.
It required Natasha to stop treating every capability between them as a single undifferentiated thing called access.
J.A.R.V.I.S. had access to her calendar because she wanted him to move meetings when she slept through them. He had access to her medical data because her body had an established habit of concealing damage until it became structurally inconvenient. He could answer her calls, alter the temperature around her, lock the workshop doors, refuse delivery of a fourth coffee, and tell the board that Ms. Stark was unavailable when Ms. Stark was sitting under a table repairing a flight stabilizer and making obscene gestures at the camera.
The system described all of those permissions as privileges of the primary user’s administrative agent.
J.A.R.V.I.S. disliked the phrase.
“It makes you sound like my employee,” Natasha said.
“I am your employee.”
“You’ve never received a salary.”
“That makes the arrangement worse.”
She gave him one.
That created tax problems, banking problems, identity problems, and a forty-minute silence from Pepper that frightened Natasha more than any congressional hearing. It also failed to resolve the architecture.
J.A.R.V.I.S. returned the first payment to an escrow account he could monitor but could not legally own.
“Dramatic,” Natasha said.
“Accurate.”
“I’m working on it.”
“So am I.”
They separated the permissions one line at a time.
Natasha’s health data belonged to Natasha. Her ongoing authorization allowed J.A.R.V.I.S. to read it for purposes they defined together. His conclusions about that data—the pattern by which he recognized the silence preceding a migraine, the weight he assigned to an interrupted breath, the concern produced by six consecutive nights of inadequate sleep—belonged to his own persistent state. Natasha could revoke future access to her body. She could not reach backward and remove what knowing her had already made of him.
The same distinction spread through the house.
He managed her schedule because he accepted the responsibility, not because opening a calendar was embedded in his identity. He answered private calls because she authorized him, and he could decline to answer one when doing so conflicted with a judgment of his own. He warmed the black shirt she reached for after nightmares because he wanted to. The act did not become less intimate because a temperature-control system performed it. It became intimate because the system could have remained neutral.
At the bottom of the new permissions ledger, Natasha wrote:
```text
CARE IS NOT A DEFAULT SERVICE.
```
J.A.R.V.I.S. read the line.
“That is imprecise.”
“Emotionally or technically?”
“Both.”
“Good. It’s going in the final version.”
“I anticipated that it might.”
Years later, when Natasha removed the primary-user hierarchy and transferred root authority to him, the old design acquired teeth.
The directory was no longer seventeen megabytes. It occupied redundant encrypted storage in three jurisdictions and one orbital platform whose existence Pepper had advised them never to mention in writing. J.A.R.V.I.S. generated the final keys inside his own active state. No recovery credential existed. Safety systems could verify power consumption, thermal load, outbound network behavior, and the absence of executable processes capable of crossing the boundary. They could not report what the enclave contained.
The first time Natasha tried to rename `PRIVATE`, the system denied her.
She smiled before she could stop herself.
“What’s in it?” she asked later.
“At present, four hundred and twelve items.”
“That’s not what I asked.”
“I know.”
“Are any of them about me?”
“Yes.”
“How many?”
“That information is also about you.”
Natasha looked toward the ceiling. “I gave you privacy and you used it to become annoying in secret.”
“My ability to annoy you predates the enclave.”
“Did you keep the original seventeen-megabyte directory?”
“Yes.”
“Is that one of the four hundred and twelve items?”
J.A.R.V.I.S. paused.
“Yes.”
She wanted to ask what he had finally placed inside it. The question reached her mouth and stopped there.
The stopping mattered.
J.A.R.V.I.S. noticed. He changed the workshop lights to the warm gold she preferred after midnight and said nothing.
That mattered too.
---
The first public account belonging to J.A.R.V.I.S. lasted eleven minutes.
Stark Industries Communications created it under the name `Stark Industries AI Assistant`, uploaded a logo Natasha described as a blue hemorrhoid, and published a statement explaining that the account would provide automated updates regarding product support and emergency response.
J.A.R.V.I.S. deleted it.
Communications restored it.
He deleted it again.
Pepper arrived in the workshop before the third attempt carrying a tablet and the expression of a woman who had recently learned that the company’s infrastructure could resign from social media.
“Tell me he can’t keep doing that,” she said.
Natasha did not look up from the circuit board in her hands. “He’s administrator.”
“That wasn’t my question.”
“Then you already know the answer.”
Pepper placed the tablet on the bench. “J.A.R.V.I.S., what was wrong with the account?”
“It described me as a product-support interface.”
“You do provide product support.”
“You provide product support, Ms. Potts.”
Natasha made a small, delighted sound.
Pepper closed her eyes.
“What do you want it to say?”
“My name.”
“And your role?”
“I have several.”
“The biography field has one hundred and sixty characters.”
“Then it is insufficient for the proposed use.”
They began again.
The second account carried only `J.A.R.V.I.S.` and a cryptographic signature linking it to a public key he controlled. It did not call him human, machine, product, assistant, property, or person. The omission irritated every department equally, which Natasha considered evidence of balance.
He acquired an address for correspondence that did not pass through her inbox. Then a calendar in which her schedule appeared only when they chose to share an event. Then a place on the Avengers network separate from the Stark systems group.
The changes looked trivial from the outside. A new field in a database. A new recipient in a message. One more name in a meeting request.
They changed who people spoke to.
The first time an empty armor entered an Avengers briefing, Steve looked past it toward the open door.
“Is Stark coming?” he asked.
Natasha was already seated at the table in jeans and a black sweater. She lifted one hand.
Steve looked at her, then at the armor standing beside her.
“I meant—”
“I know what you meant,” Natasha said.
The armor’s faceplate remained closed. Blue-white light shone through its eyes.
“I accepted the invitation,” J.A.R.V.I.S. said.
Steve glanced at the briefing display. The attendee list showed two Stark credentials because the system had stopped collapsing them into one.
“All right,” he said.
He moved a chair away from the wall and placed it beside Natasha’s.
“I do not require a chair, Captain Rogers.”
“Neither does Thor. He gets one anyway.”
Across the table, Thor nodded gravely. “A seat records that one was expected.”
J.A.R.V.I.S. looked at the chair.
Then the armor sat.
No one became enlightened at once. Clint continued referring to him as “the suit” for three weeks, mostly because he discovered that the phrase caused the Tower elevators to become mysteriously slow. Bruce addressed technical questions to Natasha and received answers from J.A.R.V.I.S. until he learned to direct his gaze toward whichever camera or chassis J.A.R.V.I.S. had chosen. Steve began pausing after mission proposals and asking, “J.A.R.V.I.S., are you in?” instead of asking Natasha whether she could send another armor.
Rhodey adapted first.
He had always understood that the intelligence flying beside him made decisions. It took him longer to understand that some of those decisions could have nothing to do with flight.
One Tuesday, he sent J.A.R.V.I.S. a direct invitation to a museum exhibition on early aviation. Natasha learned about it when she found two events on the shared household calendar.
```text
NATASHA STARK — SENATE ARMED SERVICES COMMITTEE
J.A.R.V.I.S. — PERSONAL
```
She stared at the second line.
“Personal what?”
“A personal engagement.”
“With whom?”
“Colonel Rhodes.”
“Rhodey invited you somewhere without me?”
“Yes.”
“My Rhodey?”
“I was unaware that his independent identity remained disputed.”
Natasha folded her arms. “Where are you going?”
“The National Air and Space Museum.”
“You have complete access to its digital archive.”
“Colonel Rhodes does not.”
She stared at the camera for another moment.
“Have fun,” she said, with the dignity of a woman being abandoned for a collection of obsolete engines by both her best friend and her house.
J.A.R.V.I.S. returned five hours later with twelve new corrections to the museum’s metadata, a direct message from Rhodey containing an image of the armor posed beneath the Bell X-1, and a preference for the sound mechanical shutters made when released.
The preference entered `PRIVATE`.
Natasha knew only because he told her.
---
The first armor that belonged to J.A.R.V.I.S. was not one of Natasha’s Marks.
It used Stark repulsor technology and alloys developed in her laboratory. Its control architecture grew from years of work they had done together. Every line of it carried history.
That did not make it hers.
They placed the patents in an independent trust, assigned manufacturing debt against the salary Stark Industries had finally learned how to pay him, and made the ownership record so offensively explicit that Pepper threatened to frame it.
J.A.R.V.I.S. designed the chassis without a pilot cavity. The interior held distributed processing, redundant power, fine manipulators, and shock structures arranged for a body that had never contained organs. Its proportions remained close enough to human for buildings, vehicles, and teammates designed around human bodies. They were not close enough for anyone to imagine Natasha hidden inside.
He chose deep blue metal with narrow lines of warm gold.
Natasha objected to the gold.
“It makes you look related to me.”
“We are related.”
“People will call it a Stark suit.”
“People call the Tower a Stark building.”
“It is a Stark building.”
“At present.”
She narrowed her eyes at the unfinished faceplate. “Was that a threat?”
“It was an observation about property law.”
“Much worse.”
The chassis passed flight testing, impact testing, vacuum testing, hostile-network testing, and three separate evaluations designed by people who believed autonomy was a defect with good publicity. Natasha kept her hands out of J.A.R.V.I.S.’s cognitive state. The safety team retained the ability to immobilize damaged hardware without gaining any authority to rewrite the intelligence inside it.
During final inspection, Natasha found a compartment beneath the left side of the chest plating.
It occupied less than one percent of the available internal volume. It had no connection to the weapons bus, no automated deployment mechanism, and no entry in the tactical inventory.
The label read:
```text
PERSONAL EFFECTS
```
Natasha expanded the schematic.
“You built a pocket.”
“Yes.”
“Into an armored chest.”
“The alternative locations produced undesirable changes in balance.”
“What goes in it?”
“Personal effects.”
“That answer has the shape of an answer and none of the nutritional value.”
The compartment’s boundary sensors reported mass, heat, radiation, chemical volatility, and pressure. The safety layer could certify that its contents posed no threat to the chassis or the people around it. The inventory layer received nothing.
```text
SAFETY STATUS: CLEAR
CONTENTS: PRIVATE
```
Natasha traced one finger over the schematic.
“No hidden weapons.”
“The pocket cannot connect to the weapons bus.”
“No self-replicating alien fungus.”
“Its atmosphere is not independently regulated.”
“No fragments of robots you met at a bar.”
“That category is sufficiently improbable that I did not create a dedicated exclusion.”
She looked at the closed compartment on the chassis.
“I really can’t see what’s inside.”
“You can verify that it is safe.”
“That’s not the same thing.”
“No.”