Lore file / systems
Mikoshi
Mikoshi is Arasaka's secure cyberspace infrastructure for storing and controlling digitized personalities from Soulkiller victims and Secure Your Soul clients.
Source trace / documented lore
The central claim matches the linked lore sources. Archive styling is presentation, not additional canon.
Lore trace
Mikoshi is the point where the horror becomes administrative.
Soulkiller can create an engram. That is only useful to Arasaka if the corporation can keep it, find it, access it and decide who else gets access. Mikoshi is the infrastructure built for that job.
It is described as a heavily protected data fortress in Arasaka-controlled cyberspace. Its physical server infrastructure is distributed across orbital stations around Earth, while access points exist through major Arasaka facilities. In Night City, the relevant access point beneath Arasaka Tower is called Izanagi.
A vault with permissions
The easiest bad description of Mikoshi is "Arasaka's cloud storage."
Technically, storage is part of it. Politically, custody is the important word.
Mikoshi contains digitized personalities from Secure Your Soul as well as victims taken by Soulkiller. Access is classified, authorization is controlled, sessions can be registered and recorded, and the people inside the system do not get a vote in the access policy.
That makes Mikoshi more than a place where engrams sit idle. It is the layer that turns a copied personality into a corporate-held asset.
Why netrunners call it a soul prison
The nickname is not subtle because the power relationship is not subtle.
A construct inside Mikoshi can be preserved for years, but preservation under somebody else's root access is not freedom. Arasaka controls the infrastructure, the security boundary and the rules governing interaction with the construct.
The public version of the same system is sold as preservation. For a wealthy client, Mikoshi is the vault behind Secure Your Soul. For somebody taken by Soulkiller, the same vault can look like indefinite detention.
Same infrastructure. Different consent.
Mikoshi is not Soulkiller
This distinction is load-bearing for the rest of the archive:
- Soulkiller creates the construct.
- Mikoshi keeps the construct under Arasaka control.
- Relic gives a construct a local hardware interface.
Once those jobs are separated, the 2077 plot stops looking like one piece of magic technology and starts looking like what Arasaka actually built: a stack.
Recovered machine layer
What the archive thinks it recovered
The block below is written as recovered Arasaka-era data. Corruption and Keeper annotations are interface fiction unless the sourced lore trace explicitly confirms the claim.
Source trace & provenance
Check the record against canon
These links sit outside the archive fiction. Use them to verify the claims, follow disputed details, or keep digging past this file.