Guest identity, carrier body, executive construct, and succession authority entered one breach path.
荒坂株式会社
Return to operations archive
CASEFILE KP-RELIC / KONPEKI PLAZA
RELIC CUSTODY BREACH
A hotel incident turns immortality into an access-control problem.
Public lore records the Konpeki Plaza breach as a dramatic theft. Arasaka’s institutional reading is narrower: guest identity, executive succession, biochip custody, and construct drift collapsed into one hostile operating surface.
Review threshold where advisory continuity becomes identity contamination risk.
Public narrative time compressed into private command, containment, and succession exposure.
Custody Chain
The breach is filed as four simultaneous control failures.
Each failure maps to a product requirement. The casefile turns cinematic incident pressure into procurement language a board can actually govern.
ID-01
Guest identity becomes a privileged API.
Hospitality access, suite clearance, and biometric exception paths are treated as one identity graph.
Open routed system
BC-02
Biochip custody is a live chain-of-command.
Carrier integrity, thermal control, witness state, and construct consent must move together or not at all.
Open routed system
MI-03
Construct authority cannot outrun lineage.
A stored executive mind becomes a governance object only while lineage, mandate, and drift controls agree.
Open routed system
WF-04
Response authority must survive rumor velocity.
Once the incident becomes public mythology, command surfaces need sealed evidence and fewer public claims.
Open routed system
Doctrine Routing
Konpeki resolves into continuity, archive, watchfloor, and board systems.
The incident is not presented as biography. It is the pressure model behind Relic custody, Mikoshi partitioning, neural substrate certification, and board-grade succession control.