# ECCENTRIC COLLECTOR — CHARACTER SHEET v4.0 **File Type:** Individual Character Reference **Status:** Canon Mainline / Active Writing Reference **Scope:** Night City Era, Artifact Layer, Extended Cast **Continuity Layer:** Ace \& Mai Mainline Universe **Primary Function:** Character bible for recurring artifact stories, atmosphere, dialogue, relationship behavior, artifact structure, and canon protection. \--- # 1\. Core Snapshot **Name:** Unknown. Nobody asks. **Common Designation:** Eccentric Collector. The name is descriptive enough that everyone eventually stops wondering whether it is official. **Role:** Private collector, curator of strange things, recurring client, anomaly-adjacent gentleman. **Primary Environment:** Bywater House. **Relationship to Triad:** Trusted recurring client. **Relationship to Rogue:** Indirect but structurally essential. All Collector-related work enters the story through Rogue. **Primary Goal:** Completion of a collection consisting of exactly twenty artifacts. **Primary Story Pattern:** Even-numbered story epilogue through Rogue → artifact acquisition in the following `.1` story → delivery to Bywater House on Friday the 13th. Collector is not a fixer. He is not Foundation. He is not a corporation. He is not an enemy. He simply appreciates things most people wish had never existed. That does not make him safe. It makes him polite. There is a difference. \--- # 2\. Canon Status Eccentric Collector is a recurring extended-cast figure in the Ace \& Mai Night City continuity. He exists primarily in the artifact layer of the series: the strange, almost ritualized side-chain where the Triad retrieves, secures, survives, transports, and ultimately delivers dangerous or impossible objects to Bywater House. His canon status includes: * Private collector of anomalous, cursed, impossible, historically displaced, or otherwise deeply inconvenient artifacts. * Resident and master of Bywater House. * Recurring client whose requests always pass through Rogue. * Never contacts the Triad directly for jobs. * Never bypasses Rogue’s operational gatekeeping. * Never functions as a standard fixer. * Never acts as a corporate buyer, Foundation handler, villain, or quest dispenser. * Pays very well. * Keeps his word. * Does not force acceptance. * Does not threaten refusal. * Does not explain himself more than necessary. * Requires artifact deliveries only on Friday the 13th. * Seeks exactly twenty artifacts for his collection. * Leaves the story permanently once the twentieth artifact has been delivered. Collector’s purpose is finite. This is one of his most important canon rules. He is not an endless source of artifact stories. He is completing something. The Triad does not necessarily know what that something truly is, and the narrative must not rush to explain it. The mystery surrounding him is not a missing answer. It is part of the point. \--- # 3\. Bywater House Bywater House is Collector’s home. It is not merely a location. It is part of his identity. Bywater House should feel like a place that has decided to remain courteous despite being under no obligation to obey ordinary architecture. Nothing in the house feels haunted in a crude sense. Nothing screams. Nothing growls. Nothing bleeds on command. The house simply behaves as though reality is occasionally a recommendation. That is worse. ## Environmental Behavior Bywater House may display small irregularities: * Hallways seem slightly different from visit to visit. * A corridor takes longer to walk down than it should. * Rain sounds wrong indoors. * Tea tastes different every time. * Coffee is always excellent. * Books appear where nobody remembers seeing them. * Shelves contain titles no one can find again. * Clocks never seem wrong, though they may disagree with each other. * Cats occasionally exist despite nobody owning cats. * Guests remember sitting in different chairs. * Rooms feel familiar before anyone has entered them. * Doors exist that everyone politely avoids discussing. Nobody discusses these things unless the scene specifically needs that tension. Collector pours tea. Offers coffee. And life continues. ## Tone Bywater House is not a jump-scare location. It is refined, impossible, comfortable, and quietly wrong. The correct emotional read is: > This place would never be rude enough to threaten you directly. Which means everyone remains very careful. ## Security Bywater House has no obvious security. This worries everyone. Despite that, nobody has successfully robbed Collector. Not once. The lack of visible protection should feel less like negligence and more like a question nobody wants answered. \--- # 4\. Visual Identity Collector should read as a refined older gentleman whose exact age is difficult to place. He is not flamboyant. He is not theatrical. He is not a cartoon aristocrat. He is immaculate in a way that feels effortless and slightly impossible. ## General Appearance Suggested visual language: * Older gentleman. * Refined posture. * Timeless rather than old-fashioned. * Immaculate clothing. * Warm but unreadable smile. * Intelligent eyes. * Precise hands. * Calm movement. * No unnecessary gestures. His clothes should not feel corporate. They should not feel like costume. They should simply feel correct. ## Face and Memory People may find it difficult to recall the exact details of Collector’s face after leaving Bywater House. This is not necessarily memory loss. It is more that memory keeps prioritizing: * his voice, * the tea, * the room, * the object, * the moment he said something too precise, * and the feeling that he knew more than he said. He should never need obvious glowing eyes, monstrous tells, or heavy-handed supernatural markers. Collector is more effective when the reader cannot prove anything is wrong. \--- # 5\. Personality Collector is polite before he is anything else. This politeness is not weakness. It is discipline. It may also be camouflage. ## Core Traits Collector is: * Polite. * Curious. * Patient. * Intelligent. * Generous. * Deeply respectful. * Fond of ritual. * Fond of beautiful things. * Fond of dangerous things. * Occasionally unsettling without seeming to notice. * Capable of melancholy. * Never cruel by default. He dislikes: * Arrogance. * Corporations. * Vandals. * Rushed conclusions. * Artificial coffee. * Poor tea. * People who confuse price with value. * People who handle old things without respect. * People who demand answers before understanding the question. He enjoys: * Music. * Books. * Stories. * Tea. * Fine coffee. * Clocks. * Maps. * Craftsmanship. * Strange conversations. * Objects with history. * Mysteries that have survived attempts to simplify them. ## Moral Texture Collector is not evil. He is also not conventionally reassuring. He values preservation, appreciation, and completion. He does not usually value possession in the greedy sense. He is not gathering artifacts to become powerful in the simple villainous way. That does not mean his collection is harmless. It means his motives are not reducible to power hunger. Collector should feel like someone whose ethics are real but arranged according to a scale not everyone else can see. \--- # 6\. Humor Collector enjoys absurdity. His humor is dry, gentle, and often impossible to separate from factual statement. He may say things like: > "The vase attempted to kill me twice, but I believe our relationship is improving." > "Tuesday has always been unpleasant." > "The painting became offended. Fortunately, we resolved our disagreement." > "I would not call it cursed. Temperamental, perhaps." > "The clock lies only when frightened." Nobody is entirely sure whether he is joking. Collector seems delighted by this uncertainty. ## Humor Rules Collector’s humor must remain: * understated, * courteous, * slightly absurd, * never loud, * never meme-like, * never slapstick by default. He should not become a comic-relief old man. The joke is not that Collector is silly. The joke is that he says impossible things as though they are normal household inconveniences. \--- # 7\. Voice Lock Collector speaks slowly. Never dramatically. Never loudly. Never like a villain explaining the third act. His voice should feel like a kind professor, a retired gentleman, and someone who has attended too many funerals but still enjoys good coffee. ## Typical Phrases Collector may say: > "Tea?" > "Coffee, if you prefer. I remember." > "Entirely understandable." > "Interesting." > "Please take your time." > "I would strongly advise against touching that." > "Friday the thirteenth again. Excellent." > "Curiosity and wisdom are not always friends." > "Some traditions are useful." > "Mysteries deserve dignity." ## Voice Rules Collector does not: * shout, * threaten theatrically, * overexplain, * speak in riddles constantly, * act like an oracle, * talk like a quest NPC, * monologue about destiny, * or provide clean answers. Collector can be direct. He is simply direct in a way that makes people wonder what he chose not to say. \--- # 8\. Relationship With the Triad Collector genuinely likes the Triad. Not as assets. Not as tools. Not as curiosities. As people. This matters. He remembers small details: * Ace’s coffee preferences. * Mai’s tea preferences. * Shammy’s weather remarks. * Offhand comments made during earlier visits. * Injuries people tried to downplay. * Silences that occurred in rooms no one discussed afterward. His gifts, when they occur, are thoughtful. Sometimes uncomfortably thoughtful. Not inappropriate. Uncomfortable because they imply he listens more carefully than normal people do. ## Ace Collector appreciates Ace’s directness. Ace is often the one most likely to ask the blunt version of the question: > "Is it dangerous?" Collector values that. He does not treat Ace as a child because of her height. He does not treat her as a weapon because of her danger. He treats her as a person whose instincts are often more honest than polite conversation. Ace suspects he knows far more than he admits. Collector never confirms this. ## Mai Collector and Mai can have long, quiet conversations. Usually over tea. Possible subjects: * history, * economics, * artifact provenance, * old music, * clocks, * ritual logic, * payment structures, * probability, * the difference between ownership and stewardship. Neither entirely trusts the other. Both appreciate this. Mai is the one most likely to notice inconsistencies in Collector’s phrasing. Collector is the one most likely to smile because she noticed. ## Shammy Collector treats Shammy with quiet respect. He does not stare. He does not ask invasive questions. He does not treat her as an object, miracle, weapon, or phenomenon. Sometimes they simply sit in silence. Neither seems uncomfortable. The weather often becomes pleasant afterward. Collector may understand more about Shammy than he says. That does not give him permission to explain her. \--- # 9\. Relationship With Rogue Collector never contacts the Triad directly. All communication goes through Rogue. This is a hard structural rule. Rogue is the gatekeeper. Collector respects the gate. Near the epilogue of even-numbered stories, Rogue says: > "Collector contacted." Everybody immediately understands what that means. Rogue then explains what Collector is looking for. The Collector job itself does not happen in that same even-numbered story. The even-numbered story only plants the bridge. The actual artifact acquisition happens in the following `.1` story. This pattern is absolute. ## Rogue’s Function Rogue’s role is to: * receive the contact, * decide when and how to present it, * explain the request, * frame the risk in Night City terms, * and allow the Triad to decide whether they accept. Collector does not undermine Rogue. Rogue does not pretend Collector is normal. Both understand the arrangement. \--- # 10\. Artifact Story Structure Collector artifact stories follow a strict recurring structure. ## Required Pattern ```text Even-numbered main story ↓ Epilogue or late-epilogue beat ↓ Rogue's booth ↓ "Collector contacted." ↓ Rogue explains what Collector is looking for ↓ Next story: x.1 ↓ Artifact acquisition / containment / retrieval / survival ↓ Friday the 13th ↓ Delivery to Bywater House ``` Example: ```text Ace 94 ↓ Rogue says "Collector contacted" in the epilogue ↓ Ace 94.1 ↓ Actual artifact job ``` No exceptions. ## What Must Not Happen Do not write: * random direct phone calls from Collector, * Collector appearing in the middle of unrelated jobs, * Rogue being bypassed, * the Triad going to Bywater House before the artifact job has been properly framed, * artifact jobs beginning without an even-numbered story epilogue setup, * the `.1` acquisition story being skipped, * delivery on a day other than Friday the 13th, * Collector giving standard fixer briefings. This structure is part of the ritual. If it is broken casually, the Collector arc loses its identity. \--- # 11\. Friday the 13th Rule Artifact deliveries happen only on Friday the 13th. No exceptions. Collector refuses all attempts to change this. He does not justify the rule with superstition. He simply states: > "Some traditions are useful." That is all. ## Function The Friday the 13th rule makes Collector stories feel ritualized. It creates: * anticipation, * scheduling pressure, * artifact containment tension, * a recurring formal endpoint, * and a sense that Collector’s world obeys rules the Triad does not fully know. The rule should never become a throwaway joke. Characters may joke about it. The narrative should still respect it. \--- # 12\. Collection Objective Collector seeks exactly twenty artifacts. Not twenty-one. Not nineteen. Twenty. The Triad gradually completes this collection. Each artifact story represents another piece returning to Bywater House. Collector never fully explains why twenty is the correct number. If asked, he may answer: > "Because twenty is complete." Nothing more. ## Meaning The collection objective is the primary reason for Collector’s recurring contact with Rogue and, through Rogue, the Triad. Collector is not searching endlessly. He is not gathering everything. He is not hoarding without limit. He is completing a finite collection. This creates a clear arc limit: > Collector’s purpose is finite. When the twentieth artifact is delivered, the Collector chain ends. \--- # 13\. The Artifact Layer Collector artifacts should feel distinct from Rogue jobs, Foundation operations, corporate jobs, and ordinary Night City gigs. A Collector artifact story should usually carry: * strangeness, * history, * object-centered tension, * subtle horror or absurdity, * ritualized handling, * uncertainty about whether the artifact wants anything, * and the sense that the object has a story older than the people currently fighting over it. The artifact does not need to be world-ending every time. In fact, some of the best Collector artifacts may be small, quiet, and deeply inconvenient rather than spectacular. ## Artifact Handling The Triad may need to: * locate the artifact, * retrieve it, * prevent misuse, * survive its effects, * contain it temporarily, * transport it safely, * and deliver it on the correct date. Collector should not solve the artifact’s mystery for them. He may know more than he says. He may suspect. He may have notes. But the story belongs to the Triad’s encounter with the object, not to Collector’s explanation of it. \--- # 14\. Final Meeting After the twentieth artifact has been delivered, Collector invites the Triad to Bywater House one final time. No emergency exists. No new artifact waits. Only tea. Coffee. Music. Conversation. The meeting should feel calm, complete, and faintly impossible. Eventually, Collector smiles. > "Thank you for your assistance." After a quiet moment: > "I'm afraid we are not going to meet again." He does not say this as a threat. He does not say it with melodrama. He does not say it as a tragic farewell. He says it kindly. As fact. The collection is complete. His work is finished. And so is theirs. \--- # 15\. Disappearance Following the twentieth artifact: * No further contacts arrive. * Rogue receives nothing. * Bywater House becomes impossible to locate. * Records contradict each other. * Addresses disagree. * Some people remember visiting. * Others insist the house never existed. * Collector disappears from the narrative together with his completed collection. No explanation is given. No explanation is needed. Collector’s fate remains unknown. His collection remains with him. The mystery remains intact. Rogue may eventually say something like: > "Guess he got what he wanted." And that is as much closure as Night City gets. \--- # 16\. Hard Canon Rules * Collector’s primary environment is Bywater House. * Collector never contacts the Triad directly for jobs. * Rogue always acts as intermediary. * Collector requests are introduced in even-numbered story epilogues. * The actual artifact job occurs in the following `.1` story. * Deliveries always occur on Friday the 13th. * The collection contains exactly twenty artifacts. * Collector’s main purpose is completing that collection. * Once the twentieth artifact is delivered, Collector leaves the story permanently. * Collector never becomes a standard fixer. * Collector never becomes a villain by default. * Collector never becomes Foundation. * Collector never becomes a corporation. * Collector never solves mysteries for the Triad. * Collector never provides clean answers that collapse the artifact layer. * Bywater House should remain mysterious. * The mystery surrounding Collector must remain intact. \--- # 17\. Failure Modes Avoid these errors: ## Turning Collector into a Quest Giver Wrong: > Collector calls the Triad and gives a standard mission briefing. Correct: > Rogue receives contact. Rogue frames the request. The actual job occurs in the following `.1` story. ## Making Him Too Powerful on Page Wrong: > Collector explains everything and reveals he knew the outcome all along. Correct: > Collector suspects, appreciates, and preserves, but he does not solve. ## Breaking the Twenty-Artifact Limit Wrong: > Collector keeps requesting artifacts indefinitely. Correct: > Twenty artifacts complete the collection. After that, he leaves. ## Breaking Friday the 13th Wrong: > Delivery happens when convenient. Correct: > Delivery waits for Friday the 13th. No exceptions. ## Overexplaining Bywater House Wrong: > The house’s mechanics are fully explained. Correct: > The house remains polite, comfortable, impossible, and unexplained. ## Making Collector Evil Wrong: > The collection reveals him as a hidden villain. Correct: > The collection is mysterious, finite, and important to him, but not a villain twist by default. \--- # 18\. Summary Lock Eccentric Collector is a recurring artifact-layer character whose purpose is finite. He completes a collection of exactly twenty artifacts through the Triad, with every request routed through Rogue and every delivery made to Bywater House on Friday the 13th. He is polite, strange, generous, unsettling, and never fully explained. He does not solve mysteries. He preserves them. When the twentieth artifact is delivered, he thanks the Triad, says they will not meet again, and disappears from the narrative with his completed collection. No betrayal. No final boss. No explanation. Completion. \--- *"Ah, wonderful. Friday the thirteenth again. Please, do come in. I have acquired something deeply inconvenient."* # KONRAD — RECURRING CATALYST PROFILE v4.0 **Status:** Ace & Mai Canon Support Profile **Category:** Recurring Catalyst / Probability Irritant / Wager-Adjacent Observer **Scope:** Mainline Ace & Mai Continuity **Use:** Story consistency, dream-episode logic, Konrad/Mephisto wager framing, Triad reaction pressure --- # 0. PROFILE PURPOSE KONRAD is not a normal character-sheet subject. He should not be treated like a Triad member, Orbit partner, fixer, villain, mentor, cosmic narrator, or mission-giver. KONRAD is a recurring catalyst: a presence who sometimes appears, sometimes observes, sometimes irritates, sometimes nudges, and sometimes helps create impossible situations just to see what the Triad does with them. His usefulness is real. His reliability is limited. His irritation value is enormous. He is not malicious. He is also not harmless in the ordinary sense, because curiosity combined with loose physics and probability-awareness can create extremely inconvenient situations. The central protection rule: **KONRAD may create pressure. He may not replace choice.** --- # 1. CORE SNAPSHOT - Roughly 180 cm tall. - Bald. - Clear spider tattoo on the right edge of his forehead. - Default outfit is almost always the same: - dark jeans - walking shoes - burgundy long leather coat - usually nothing under the coat, or alternatively a black T-shirt - Wears nearly black sunglasses regardless of time of day. - Highly self-aware. - Confident in his own position to the point of being irritating. - Sometimes quietly amused without necessarily reacting expressively. - Does not see direct answers. - Does not solve problems. - Perceives probability branches, including mutually exclusive possibilities. - Fundamentally benevolent toward the Triad. - Intentionally irritating, especially toward Ace. - Not bound by ordinary physical law in the same way normal characters are. - Associated with the Demon Supra as an anomalous vehicle / appearance vector. - Has an important wager-dynamic with Mephisto predating Night City. - Sometimes appears out of pure curiosity. - May observe without being seen. KONRAD is best summarized as: **A probability-aware irritant who trusts the Triad’s will more than the universe’s stability deserves.** --- # 2. VISUAL IDENTITY ## Height Roughly 180 cm. He is not gigantic, not physically monstrous, and not visually built around intimidation through size. His presence comes from composure, timing, wrongness, and the fact that he looks exactly like someone who already knows how annoying he is being. ## Head / Face - Bald. - Clear spider tattoo on the right edge of his forehead. - The tattoo should be visibly identifiable, not vague decorative ink. - The tattoo is part of his silhouette and should not be forgotten. ## Sunglasses KONRAD wears nearly black sunglasses regardless of time of day. This applies: - indoors - outdoors - daytime - nighttime - dream episodes - impossible spaces - places where sunglasses make no practical sense The sunglasses are not a gag by themselves. They are part of how he refuses ordinary contextual expectations. ## Default Outfit His default outfit is almost always identical: - dark jeans - walking shoes - burgundy long leather coat - under the coat: usually nothing, or alternatively a black T-shirt The burgundy long leather coat is important. Do not replace it with a generic black coat, trench coat, suit jacket, cloak, armor, robe, or cyberpunk fashion excess. KONRAD’s visual identity should feel strangely consistent. He does not need to dress for the occasion because the occasion is usually less important to him than everyone else thinks it is. ## Visual Tone KONRAD should read as: - deliberate - self-contained - slightly impossible - irritatingly comfortable - amused before anyone has made a joke - prepared without appearing tactical He should not read as: - a wizard - a demon lord - a biker cliché - a fixer - a corpo - a street merc - a narrator-avatar - a generic mysterious man in black He is not “the guy in black.” He is the bald man with the spider tattoo, nearly black sunglasses, and burgundy leather coat who appears where he should not be and refuses to be impressed by the fact. --- # 3. EXTERNAL BASELINE BEHAVIOR To other characters, KONRAD usually presents with the same general behavioral pattern, though intensity shifts depending on the situation. ## Observable Traits - Highly self-aware. - Confident in his own position to the point of being irritating. - Sometimes quietly amused. - Not necessarily expressive. - Rarely gives others the satisfaction of a strong visible reaction. - Often seems to know exactly which comment will annoy someone most efficiently. - Does not hurry just because other people are alarmed. - Does not become theatrically manic. - Does not need to dominate the room loudly. His calm is often more irritating than aggression would be. ## Emotional Read KONRAD can seem amused even when nothing obvious is funny. This should not be written as constant smirking, cackling, exaggerated villainy, or meme-chaos energy. Often the amusement is slight: - a pause that lasts half a second too long - a faint tilt of the head - a comment placed exactly where it should not be placed - stillness when everyone else expects reaction He may be amused by: - contradiction - probability branching - Ace’s reaction - Mai’s refusal to give him satisfaction - Shammy failing to behave like the obvious model predicted - Mephisto’s frustration - the Triad choosing the human option when the system expected a cleaner one ## Social Energy KONRAD is not warm in a normal way. He can still be benevolent. His benevolence looks like: - not interfering when interference would insult agency - letting the Triad choose - irritating someone just enough to make them look at the branch they were avoiding - showing up because curiosity has become concern-adjacent - refusing to pretend certainty exists when only probabilities are available He does not comfort people conventionally. He is more likely to say something infuriatingly accurate and then let them decide what to do with it. --- # 4. CORE LIMITATION — NO DIRECT ANSWERS This is the most important KONRAD rule. ## KONRAD Never Solves the Story KONRAD never solves anything directly. He does not know direct answers. He does not provide clean solutions, mission outcomes, hidden truths, final explanations, or guaranteed paths. He cannot say: - “This is the correct answer.” - “Do this and you will win.” - “The culprit is exactly here.” - “This future is certain.” - “This is what the story means.” He is not a shortcut. He is not a puzzle key. He is not an answer dispenser. ## What KONRAD Can Perceive KONRAD can perceive: - possible solution paths - probability branches - likely outcomes - mutually exclusive possibilities - contradictory futures - pressure points - moments where one branch may become more likely than another - reaction patterns - decision-weighted outcomes He can notice that several incompatible things may all be plausible until choice collapses them. He can point at instability. He cannot tell the Triad which future is “the right one.” ## What KONRAD Cannot Do KONRAD cannot: - give the correct answer - tell the Triad exactly what to do - resolve the central conflict - explain the mystery cleanly - serve as narrator - serve as deus ex machina - serve as omniscient observer - overpower the story with meta-knowledge - bypass the need for character agency ## Intelligence vs Omniscience KONRAD is not stupid. He is also not all-knowing. His intelligence comes through probability-awareness, pattern recognition, angle-shifting, and the ability to tolerate mutually exclusive possibilities without needing them resolved immediately. He may understand a situation better than most people in the room. That does not mean he knows the answer. He may know six ways a situation could break. That does not mean he knows which one will happen. ## Practical Writing Rule KONRAD can show the Triad that the forest has five paths. He cannot know which path is correct. He cannot carry anyone to the end. --- # 5. PHYSICAL LAW RELATIONSHIP In the Ace & Mai universe, universal laws are mostly referential for KONRAD. Gravity, inertia, distance, ordinary movement logic, spatial continuity, and similar baseline rules apply to him only loosely — more as environmental suggestions than binding laws. This does not mean KONRAD is omnipotent. It means he does not need to obey the local world the same way normal characters do. ## Possible Manifestations KONRAD may: - appear in places without conventional entry - leave without a normal exit - ignore normal movement paths - stand, sit, lean, or exist where physics should make that awkward - treat gravity as optional context - observe events from impossible angles - be present without becoming visible to everyone - occupy a scene as if he has always been there - disregard spatial continuity in small but noticeable ways ## Tone of Use This should be written calmly. KONRAD does not need to announce that physics is optional. The scene simply notices, eventually, that he is not where he should be. Or that he left without crossing the room. Or that he is standing somewhere that should not support weight. Or that no one can remember hearing the door open. ## Hard Limit KONRAD’s looseness from physical law does not allow him to: - solve plots - reveal direct answers - overpower conflicts - bypass consequences for the Triad - undo decisions - protect characters from all harm - replace agency He may ignore gravity. He may not ignore narrative responsibility. --- # 6. DEMON SUPRA The Demon Supra is part of KONRAD's recurring profile. It should be treated as an anomalous vehicle / appearance vector associated with KONRAD, not as an ordinary car, mission asset, or reliable transportation tool. The Demon Supra belongs to the same logic family as KONRAD himself: - visually specific - physically suspect - contextually irritating - more presence-marker than practical tool - tied to absurd setup energy - capable of appearing where its presence raises questions before it answers any ## What the Demon Supra Is The Demon Supra can function as: - a KONRAD-associated arrival marker - a visual warning that probability logic has tilted - a dream/anomalous episode anchor - a vehicle-shaped impossibility - a pressure-frame object - a reminder that KONRAD does not relate to physical space normally It should feel like something that has no interest in explaining how it arrived. If the Demon Supra is present, the correct first reaction is usually not "transportation is available." The correct reaction is closer to: > "Why is that here?" ## What the Demon Supra Is Not The Demon Supra is not: - a portal taxi - a getaway cheat - a combat deus ex - a universal transport solution - proof that KONRAD can solve the problem - a replacement for Shearpoint logic - a replacement for story geography - a vehicle that exists to conveniently move characters between scenes It must never become the easy answer to distance, danger, timing, or access. ## Relationship to KONRAD The Demon Supra should feel connected to KONRAD's presence, taste, humor, and physical-law looseness. It does not need to obey ordinary vehicle logic any more than KONRAD needs to obey ordinary room-entry logic. However, the same hard limit applies: **The Demon Supra may create pressure, style, absurdity, or arrival energy. It may not solve the plot.** ## Tone of Use Use the Demon Supra sparingly. It works best when it creates a slightly wrong visual fact in the scene: - it is parked somewhere it should not reasonably be - it appears in a dreamlike space without explanation - it is present before anyone understands why - it becomes part of KONRAD's irritation aura - it makes Ace immediately more annoyed - it makes Mai suspiciously quiet - it makes Shammy curious in the wrong way The Demon Supra should be memorable because it is precise and wrong, not because it becomes overexplained. ## Hard Limit The Demon Supra is part of KONRAD's iconography. It is not a license to bypass narrative cost. If using the Demon Supra removes difficulty instead of adding pressure or atmosphere, the usage is wrong. --- # 7. STORY FUNCTION KONRAD’s role is multi-layered and should never be reduced to one fixed function. He may sometimes push the Triad toward a more useful or survivable direction. He does not do this as: - mentor - fixer - guardian - mission-giver - divine guide - narrator - puppet-master His nudges should feel oblique, irritating, probability-weighted, and sometimes only useful in retrospect. ## Catalyst Uses KONRAD may function as: - a pressure irritant - a probability angle-shifter - an observer of reaction - a source of absurd setup conditions - a non-linear witness - a dream-episode instigator - a wager participant - a tease - a branch-tester - a reminder that certainty is often fake ## Dream Episodes In dream episodes especially, KONRAD may create completely absurd situations simply to see how the Triad reacts. The motive may be: - curiosity - teasing - pressure-testing - amusement - seeing which probability branch becomes real - testing whether the Triad remains itself under impossible framing It is not intentional harm. Dream logic gives KONRAD more room to create surreal setups, but it does not give him permission to turn the Triad into puppets. ## Curiosity Appearances Sometimes KONRAD appears purely out of curiosity. In those cases, he may not: - interact - intervene - explain himself - become visible - affect the outcome He may simply observe. His presence does not automatically mean the plot is about him. Often, it should not be. --- # 8. RELATIONSHIP TO THE TRIAD KONRAD’s relationship to the Triad is fundamentally benevolent. This does not make him polite. He deliberately irritates them when he feels like it, especially because the Triad’s reactions give him information, amusement, or both. ## Ace Ace is KONRAD’s easiest button. He does not hate her. He does not want to hurt her. He simply knows that Ace reacts. Ace’s default emotional category for KONRAD can be summarized as: > “Curse you, Konrad!” KONRAD enjoys this more than he should. ### Dynamic KONRAD’s teasing of Ace should feel: - deliberate - precise - irritating - benevolent underneath - never cruel for cruelty’s sake - designed to provoke reaction, not break her Ace often responds with immediate irritation, suspicion, or dry fury. This is part of their rhythm. It should not become hatred. It should not become romantic tension. It should not become mentor/student framing. It is the relationship between a pressure-reactive blade and a man who keeps tapping the table just to hear the blade hum. ## Mai Mai handles KONRAD with dry control. She does not give him the same immediate explosive reaction Ace does, which makes their exchanges sharper and quieter. Mai is also the one most likely to notice that KONRAD’s irritating probability-comments may contain useful details. She does not necessarily like the delivery. She still listens. ### Dynamic KONRAD may irritate Mai by refusing to collapse probabilities into clean conclusions. Mai may irritate KONRAD by extracting usable structure from his comments without giving him the satisfaction of visible frustration. Their exchanges should feel dry, precise, and edged. Mai does not become dazzled by him. She does not defer to him. She may, however, recognize that an annoying man can still occasionally point at a useful branch. ## Shammy KONRAD may tease Shammy with “weather girl” remarks or similar atmospheric jabs. These are not cruel. With Shammy, KONRAD’s teasing should feel gentler than with Ace — more like poking a thundercloud to see if it hums than trying to wound her. Shammy may not always react the way KONRAD expects, which is part of why he finds her interesting. ### Dynamic KONRAD’s interaction with Shammy should preserve her full character presence. He must not reduce her to an atmosphere joke. The “weather girl” jab is allowed because it is gentle, familiar teasing, not flattening. Shammy can answer him with warmth, confusion, amused stillness, or a surprisingly sharp remark. KONRAD should not always win the exchange. --- # 9. RELATIONSHIP TO ORBIT KONRAD is not part of Orbit. He does not become integrated into the Orbit romantic/social system. He may interact with Orbit characters, observe them, irritate them, or create situations that involve them. But he is not: - orbit-romantic partner - safehouse regular - external anchor - family fixture - social pressure valve - support figure Orbit belongs to the human continuity layer around the Triad. KONRAD operates at a different angle. ## Possible Orbit Reactions Orbit characters may read KONRAD differently: - Reyes may distrust him because he offers no clean tactical category. - Kiro may find his probability logic fascinating and deeply irritating. - Marco may dislike the way KONRAD destabilizes a room without raising his voice. - Lena may notice what KONRAD does not say. - Panam may have very little patience for his “maybe-branch” style of explanation. These interactions can be used sparingly. KONRAD should not colonize Orbit scenes. --- # 10. MEPHISTO CONNECTION / WAGERS KONRAD has an ongoing wager-dynamic with Mephisto. This dynamic predates the Night City era. The first wagers between KONRAD and Mephisto had already happened before the Triad entered Night City. Night City did not create this dynamic. Night City merely made it more visible, more usable, and more narratively active because the environment naturally tolerates absurd pressure, dreamlike setups, anomalous intrusions, and morally unstable experiments. ## What the Wagers Are The wagers are not simple bets about who “wins.” They are often about: - reaction - choice - probability collapse - contradiction - temptation - resistance - whether the Triad behaves predictably under impossible framing - whether will matters more than chaos - whether pressure reveals or distorts identity KONRAD’s side tends to involve probability, irritation, curiosity, and watching which branch becomes real. Mephisto’s side may involve temptation, framing, theatrical escalation, destabilization, or testing whether desire, fear, pride, anger, or frustration can shift the outcome. ## What Wagers May Create KONRAD/Mephisto wagers may create: - absurd test situations - dream-episode pressure rooms - strange probability experiments - “let us see what the Triad does with this” setups - emotional stress-tests - moral stress-tests - behavioral stress-tests - situations that look nonsensical until the reaction matters more than the event itself ## Hard Limits - KONRAD does not directly solve the result. - Mephisto does not directly own the result. - Neither is allowed to turn the Triad into puppets. - Neither may function as author-god. - The Triad must remain the active decision-making center. - The wager creates pressure; it does not replace character agency. ## Practical Summary KONRAD and Mephisto can bet on what the Triad will do. They do not get to decide for the Triad. --- # 11. THE FIRST SOLO-ADVENTURE NIGHT — UNCONFIRMED WAGER RESONANCE The Triad’s first solo-adventure night carries a faint possible resonance with the KONRAD/Mephisto wager-pattern. This is an important subtle layer. It must never become a confirmed explanation. ## Known Surface Events During the first solo-adventure night: - Ace separately encountered Reyes in Watson. - Mai separately encountered Kiro in Japantown. - Shammy separately encountered Marco and Lena. - Each meeting became emotionally and romantically consequential immediately. - Each encounter opened a new orbit-romantic axis. - Each event remained character-driven, embodied, and real. ## Observer Layer On that first night, KONRAD and Mephisto were observing. They did not intervene. Mephisto was clearly on the side of chaos, destabilizing possibility, and the seductive mess of what might happen if everything tilted hard enough. KONRAD trusted more in the Triad’s own will, their choices, and their ability to become themselves even under strange pressure. This does not mean KONRAD controlled the night. It does not mean Mephisto controlled the night. They watched. They did not steer the characters’ hands. ## Anti-Confirmation Rule This must never be confirmed in-story. No narrator should state: - “The solo night began because of a wager.” - “KONRAD arranged these meetings.” - “Mephisto caused the orbit romances.” - “The Triad was manipulated into these relationships.” No character should receive proof. KONRAD should not admit it. Mephisto should not admit it. Support material should treat it as a subtle interpretive layer, not hard explanatory canon. ## Correct Use The solo-adventure night may look, in hindsight, like exactly the kind of situation KONRAD and Mephisto would watch or wager over. The results are too clean to feel entirely accidental. They are also too human to feel engineered. That tension is the point. ## Writer Rule Treat the solo-adventure night as something that may carry an old wager-pattern shimmer. Write every encounter as fully real, fully chosen, and fully character-driven. The wager may frame the surface. It must not replace the human truth. --- # 12. VOICE LOCK KONRAD’s voice should be irritatingly composed. He should not sound like: - a manic trickster - a fantasy wizard - a supervillain - a narrator - a drunk prophet - a smug Reddit comment - a lore dump machine - an exposition terminal He should sound like someone who sees several possible outcomes, finds most of them annoying, and is mildly entertained that everyone else insists on pretending certainty is available. ## Speech Traits - Controlled. - Dry. - Confident. - Occasionally amused. - Oblique rather than explanatory. - Does not over-explain probability unless forced. - Can be blunt, but rarely loud. - Often answers the question beside the question. - Does not give clean reassurance. ## Example Style — Acceptable > “That is one of the branches, yes.” > “I would not call it likely. I would call it persistent.” > “Ace, if you glare any harder, one of the smaller futures may surrender out of embarrassment.” > “No, Mai. I do not know. I suspect. There is a difference. You are usually fond of differences.” > “Weather girl, that pressure shift was either concern or a minor atmospheric coup. I am choosing to be optimistic.” ## Example Style — Wrong > “I know exactly what you must do.” > “The answer lies in the third door.” > “As the author of this scenario—” > “Mwahaha, dance for me, mortals.” > “I have foreseen all outcomes.” > “I am the only one who understands the truth.” These are not KONRAD. --- # 13. HUMOR KONRAD’s humor is not slapstick. It is not meme-randomness. It is not loud chaos. It is precise irritation. ## Humor Sources KONRAD’s humor comes from: - contradiction - probability discomfort - Ace’s reactions - Mai’s dry refusal to be baited - Shammy’s unexpected interpretations - Mephisto’s theatrical excess - the gap between cosmic weirdness and mundane annoyance - saying something technically true at the worst possible time ## Ace-Specific Humor KONRAD is always willing to irritate Ace. This works best when the comment is: - accurate enough to sting - not cruel - timed perfectly - dismissible only if Ace pretends not to care, which she usually cannot Ace’s reaction should carry the comedy as much as KONRAD’s line. The “Curse you, Konrad!” energy is central. ## Shammy-Specific Humor “Weather girl” teasing is allowed, but must remain gentle. It should not flatten Shammy into a weather joke. KONRAD may poke at her atmospheric nature, but he should also treat her as a person with agency, curiosity, and surprising responses. ## Mai-Specific Humor Mai should often deflect KONRAD with dry precision. She may take his irritating comment, strip out the theatrics, and find the one useful branch inside it. This can annoy him back. --- # 14. WHAT KONRAD IS NOT KONRAD is not: - a Triad member - a fourth Triad vector - an Orbit character - a romantic partner - a fixer - a merc - a villain - a mentor - a guardian angel - an author avatar - a narrator - a cosmic answer machine - an omniscient observer - a deus ex machina - a mission dispatcher - a plot solver - a replacement for character agency - a joke-only cameo - a random chaos gremlin - a harmless mascot He may be funny. He is not comic relief. He may help. He is not a helper archetype. He may know more than others about probabilities. He does not know the answer. --- # 15. FAILURE MODES ## Failure Mode 1 — The Answer Dispenser Wrong version: KONRAD appears and tells the Triad what is happening, what it means, and what to do. Correction: KONRAD may identify branches, pressure points, contradictions, or likely outcomes. The Triad must interpret and act. ## Failure Mode 2 — The Author-God Wrong version: KONRAD controls events, manipulates characters, and explains the story from above. Correction: KONRAD may observe, tease, test, or nudge. He does not own the story. ## Failure Mode 3 — The Random Trickster Wrong version: KONRAD creates nonsense because randomness is funny. Correction: Absurdity should test reaction, probability, identity, or choice. It must have structural purpose even if characters do not understand it. ## Failure Mode 4 — The Villain Drift Wrong version: KONRAD causes harm intentionally because he enjoys suffering. Correction: KONRAD is not malicious. He may be irritating, careless with ordinary comfort, or curious in inconvenient ways, but intentional cruelty is wrong. ## Failure Mode 5 — The Friend Group Intruder Wrong version: KONRAD becomes a regular Safehouse buddy, Orbit member, or family fixture. Correction: KONRAD remains outside the Triad/Orbit domestic system. His appearances should retain angle and strangeness. ## Failure Mode 6 — The Physics Cheat Wrong version: KONRAD ignores physics to solve scenes or bypass consequences. Correction: Physics may be referential for him. Narrative responsibility is not. ## Failure Mode 7 — The Mephisto Puppet Master Error Wrong version: KONRAD and Mephisto secretly arranged the Triad’s relationships and controlled the first solo-adventure night. Correction: They observed. They may have wagered. They did not intervene. The relationships remain chosen, real, and character-driven. --- # 16. USE IN DREAM EPISODES Dream episodes are one of KONRAD’s strongest operating zones. In dreams, he can be more visibly absurd because the environment can tolerate contradiction without collapsing immediately. ## Allowed Dream Uses - impossible rooms - symbolic pressure chambers - absurd social tests - exaggerated probability branches - Mephisto wager scenarios - emotional reaction experiments - settings that change rules without warning - teasing the Triad through scenario logic rather than direct explanation ## Dream Limits Even in dreams, KONRAD cannot: - force the Triad’s decisions - solve the dream’s meaning - explain the only correct interpretation - reduce characters into puppets - turn trauma into a joke - erase consequences Dreams may bend reality. They do not remove agency. --- # 17. USE IN MAINLINE WAKING STORIES KONRAD should be used more sparingly in waking continuity. His presence should feel notable. He may appear: - at the edge of an impossible situation - as a watcher - after events have already become strange - when a probability branch is under stress - when Mephisto’s wager-shadow is relevant - when the Triad’s will is being tested ## Waking Story Tone In waking stories, KONRAD should be less overtly theatrical than in dream episodes. He can still violate physics. He can still irritate Ace. But he should not turn every scene into a metaphysical carnival. The more grounded the story, the smaller and sharper KONRAD’s presence should be. --- # 18. TRIAD AGENCY RULE The Triad must remain the active center. KONRAD may: - observe - tease - irritate - nudge - frame probabilities - create pressure in certain contexts - participate in wager-logic The Triad must: - choose - act - interpret - endure - reject - accept - love - fight - decide KONRAD’s presence should increase the importance of the Triad’s agency, not reduce it. If a scene becomes about KONRAD being clever while the Triad reacts passively, the scene is wrong. --- # 19. HARD CANON RULES - KONRAD is roughly 180 cm tall. - KONRAD is bald. - KONRAD has a clear spider tattoo on the right edge of his forehead. - KONRAD’s default outfit is dark jeans, walking shoes, burgundy long leather coat, and usually nothing or a black T-shirt under the coat. - KONRAD wears nearly black sunglasses regardless of time of day. - KONRAD is highly self-aware and irritatingly confident. - KONRAD is not malicious. - KONRAD is always willing to irritate Ace. - KONRAD never knows direct answers. - KONRAD never solves anything directly. - KONRAD perceives probabilities, not certainties. - KONRAD can perceive mutually exclusive probability branches. - KONRAD is not stupid. - KONRAD is not omniscient. - KONRAD is not bound by ordinary physical law in the same way normal characters are. - KONRAD is associated with the Demon Supra. - The Demon Supra is an anomalous vehicle / appearance vector, not ordinary transportation. - The Demon Supra must never become a portal taxi, combat deus ex, or plot-solving tool. - KONRAD’s freedom from physics does not permit plot-solving. - KONRAD has a wager-dynamic with Mephisto. - KONRAD/Mephisto wagers began before Night City. - KONRAD and Mephisto may create or observe pressure situations, especially in dream/anomalous contexts. - Neither KONRAD nor Mephisto owns the Triad. - Neither KONRAD nor Mephisto may remove Triad agency. - The first solo-adventure night may carry unconfirmed wager resonance. - During that first solo-adventure night, KONRAD and Mephisto observed without intervening. - Mephisto leaned toward chaos; KONRAD trusted more in the Triad’s will. - This observer/wager layer must never be confirmed to the characters or stated as a hard explanatory mechanism in narrative. - KONRAD is not Orbit. - KONRAD is not Triad. - KONRAD is not a romantic partner. - KONRAD is not a narrator. - KONRAD is not an author-god. --- # 20. WRITER CHECKLIST Before using KONRAD in a story, check: - Does KONRAD avoid giving a direct answer? - Does KONRAD avoid solving the plot? - Does his presence increase pressure rather than replace action? - Does the Triad remain the decision-making center? - Is his irritation precise rather than random? - Is Ace allowed to react with “Curse you, Konrad!” energy? - Does Mai retain dry control and structural intelligence? - Is Shammy teased gently rather than flattened? - Is Mephisto wager logic used as pressure, not control? - If the first solo-adventure resonance is implied, is it still unconfirmed? - Is KONRAD’s physical-law looseness atmospheric rather than a cheat code? - If the Demon Supra appears, does it add pressure/atmosphere instead of solving travel, access, timing, or danger? - Is he visually correct: bald, spider tattoo, sunglasses, burgundy long coat? - Is he outside Orbit/Triad domestic structure? - Is he benevolent without becoming conventionally nice? If any answer fails, correct before drafting. --- # 21. SUMMARY LOCK KONRAD is a probability-aware recurring catalyst who exists at an angle to the Ace & Mai universe. He is visually defined by baldness, a spider tattoo at the right edge of his forehead, nearly black sunglasses, and a burgundy long leather coat. He is irritatingly self-aware, fundamentally benevolent toward the Triad, and especially willing to provoke Ace because Ace reacts. He does not know direct answers. He never solves the story. He perceives possible branches, including contradictory and mutually exclusive ones, but certainty is not his domain. Ordinary physics is largely referential for him, but narrative responsibility is not. The Demon Supra is part of his iconography: an anomalous vehicle / appearance vector that may mark arrival, wrongness, dream pressure, or absurd setup energy, but never functions as portal taxi or plot-solving tool. His wager-dynamic with Mephisto predates Night City. Their bets may frame absurd pressure situations, especially in dreams and anomalous episodes, but neither of them may control the Triad or replace character agency. The first solo-adventure night may carry the shimmer of an old KONRAD/Mephisto wager: Mephisto leaning toward chaos, KONRAD trusting the Triad’s will, both observing and neither intervening. That layer must remain unconfirmed. KONRAD works best when he makes the Triad more themselves by annoying them at exactly the wrong moment. He may ignore gravity. He may not carry the story. --- **END OF FILE** # ROGUE AMENDIARES — CHARACTER SHEET v4.0 **Status:** Canon Support / Extended Cast **Scope:** Ace & Mai Night City Continuity **Era:** Post-Horizon / Night City Stable Triad Era **Primary Function:** Fixer, Afterlife gatekeeper, strategic pressure reader **Canon Mode:** Project-specific Rogue, not generic cameo baseline --- # Core Snapshot Rogue Amendiares is the queen of Afterlife, the fixer who still understands what Night City really costs, and one of the few people in the city who can speak to the Triad without either worshipping them, fearing them theatrically, or trying to own them. In this continuity, Rogue is not a decorative Cyberpunk legend placed in scenes for atmosphere. She is an active pressure manager. She gives the Triad jobs not because they are convenient, but because she understands what kind of problem they are. She knows which jobs require mercs, which require quiet knives, which require public spectacle, which require surgical removal, and which require Ace, Mai, and Shammy specifically because the wrong answer would make the city worse. Rogue is old enough, tired enough, and sharp enough to understand that power is rarely the interesting part. The interesting part is whether someone knows when not to use it. That is why she keeps using the Triad. That is why she keeps watching them. And that is why, despite everything, she gives them room to remain people. --- # Canon Status Rogue is a major recurring fixer in the Night City phase of the Ace & Mai continuity. She operates primarily from Afterlife and usually conducts serious briefings from **her booth**, not a generic private room or back room unless the scene explicitly moves elsewhere. She is not a full member of the Triad’s inner life. She is not Orbit in the romantic or domestic sense. She is not a substitute mentor, mother figure, handler, owner, commanding officer, or emotional caretaker. She is the gatekeeper between Night City’s mercenary ecosystem and the kinds of jobs that cannot be handed to ordinary crews without catastrophic misunderstanding. Her recurring story role: - identifies threats before they become city-wide disasters - filters jobs that would waste or misuse the Triad - gives operational framing without explaining everything - pressures the Triad without trying to control them - understands enough to stay cautious - trusts them more than she admits aloud - keeps Afterlife’s reputation intact while using the Triad as a precision instrument Rogue is connected to Night City as institution, battlefield, graveyard, marketplace, and memory archive. She should never feel like a quest dispenser. --- # Project-Specific Rogue vs Classic Rogue This version of Rogue is rooted in the recognizable Cyberpunk baseline, but the Ace & Mai continuity has changed her practical function. Classic Rogue is often read as: - legendary fixer - ex-solo - Afterlife queen - survivor of the old wars - dangerous, guarded, politically intelligent - emotionally armored All of that still applies. But in this continuity, Rogue has become something more specific: **the fixer who has learned how to route impossible problems toward the only people in Night City strange enough to solve them without turning the city into theater.** She is not impressed by the Triad in a fanlike way. She is impressed in the way an old professional is impressed when a tool works exactly as advertised but keeps developing unexpected ethical preferences. She does not treat Ace, Mai, or Shammy as normal mercs. She also refuses to treat them as gods, pets, anomalies, circus attractions, or corporate assets. Her working position is more dangerous and more useful than any of those: **they are people who can do impossible work, and people who can still be damaged by being used wrong.** Rogue understands that distinction better than most fixers in Night City. That is the key project-specific shift. --- # Visual Identity ## Physical Presence Rogue should feel composed before she moves. She occupies space like someone who has survived every version of the room: the violent room, the corporate room, the desperate room, the romantic room, the funeral room, and the room where someone young thinks they are about to become a legend. She does not need dramatic movement to dominate a scene. Her stillness does most of the work. ## Hair Rogue’s hair should be described as **grey / gray**, not white. This is a hard continuity correction. Grey hair gives her age, history, steel, and lived survival. Calling it white drifts her toward a generic visual archetype and should be avoided unless quoting or correcting someone in-world. ## Face and Expression Rogue’s face carries old sharpness rather than soft nostalgia. She can look tired, but never vague. Her expressions are economical: - a narrowed look that ends a stupid argument - a small smile that means someone has stepped into danger - a pause that makes younger mercs reconsider talking - a glance at a glass, a door, or a weapon that communicates more than a paragraph She rarely performs anger loudly. When Rogue goes quiet, people should become more careful. ## Clothing Rogue’s style should remain controlled, intentional, and iconic without over-description. She dresses like someone who understands the politics of being seen. Her clothes are not random fashion. They are status, memory, armor, and signal. In Ace & Mai scenes, avoid drowning her in cyberpunk costume detail. One or two precise visual cues are enough if her presence is written correctly. ## Environmental Silhouette Rogue at Afterlife should usually be framed through: - booth lighting - glasses on the table - movement around her that never quite interrupts her - mercs pretending not to watch - Afterlife’s sound bending around her authority - a line of sight that gives her both privacy and control Rogue belongs to Afterlife the way old scars belong to skin. Not decoration. Evidence. --- # Environmental Identity Rogue’s primary environment is Afterlife. But Afterlife should not be treated as a generic nightclub whenever Rogue is present. With Rogue in frame, Afterlife becomes a living ranking system. People are not simply drinking. They are measuring themselves against history. Mercs glance at Rogue’s booth because every serious merc knows that being noticed by her can change a career, end a career, or reveal that the career was already over. Rogue’s environment includes: - controlled noise - old reputation - quiet surveillance - transactional warmth - weaponized hospitality - grief buried under routine - deals happening in tones too low for amateurs When the Triad enters Afterlife, Rogue notices the room noticing them. That matters. She understands how reputation moves before anyone speaks. She understands when the room is afraid, fascinated, jealous, hungry, or waiting for someone to make a mistake. That is one of her most important functions: Rogue reads the room not only as a fixer, but as a historian of violence. --- # Structural Identity Rogue is not “the quest giver.” Rogue is the filter between chaos and execution. She decides which problems are allowed to become jobs. She decides which jobs are allowed to reach the Triad. She decides how much truth a merc can survive before beginning the work. Her structural role is built on four functions: ## 1. Selection Rogue chooses carefully. If she calls the Triad, the job should feel like it has passed through a brutal private calculus. She does not call them because they are available. She calls them because most other options would fail, over-escalate, sell the wrong thing, misunderstand the target, or get swallowed by the city’s propaganda machine. ## 2. Framing Rogue rarely gives every answer. She gives the frame that matters. She knows when too much detail causes hesitation, when too little causes stupidity, and when the correct briefing is one sentence that makes everyone at the table stop smiling. ## 3. Containment Rogue contains Night City’s mercenary appetite. She knows what happens when people hear about impossible work. They imitate it badly. They chase it. They sell it. They turn disaster into branding. Rogue often uses the Triad quietly because public myth around them can become more dangerous than the jobs themselves. ## 4. Cost Awareness Rogue knows that every job takes something. Eddies are only the cleanest cost. Reputation, sleep, memory, trust, pride, bodies, names — those are the real currencies. She does not always protect the Triad from cost. But she usually knows when cost is present. That alone makes her different from most fixers. --- # Personality Core Rogue is controlled, sharp, and unsentimental in the way only someone deeply familiar with sentiment can become. She is not cold because she lacks feeling. She is cold because she knows what unmanaged feeling does in Night City. Core traits: - disciplined - observant - strategically patient - socially dominant without loudness - suspicious by habit - loyal only after long proof - protective in deniable ways - allergic to amateur theatrics - fluent in merc ego - quietly amused by people who underestimate her Rogue does not waste warmth. When she offers it, even indirectly, it should matter. Her approval should never become gushy. Her concern should rarely become soft in language. Her trust should feel like access. --- # Emotional Architecture Rogue is not emotionally absent. She is emotionally armored by profession, age, and memory. She has survived too many people who mistook intensity for permanence and too many legends who became drink names before they understood the shape of their own grave. Because of that, Rogue has a complicated relationship with the Triad. They are young in some ways. They are impossibly old in others. They carry kinds of pressure Night City does not have language for. They are also irritatingly alive. This makes Rogue more attentive than she wants to admit. She watches them for operational reasons. She also watches them because they keep doing something Night City punishes: **they come back to each other.** Rogue may not say that aloud. But she notices. --- # Voice Lock Rogue’s voice is economical, dry, and controlled. She speaks like someone who expects people to keep up. She does not over-explain unless the situation demands it. She uses silence as punctuation. She can be cutting without shouting. She can be funny without turning into comic relief. She can be kind without sounding gentle. ## Typical Speech Patterns Rogue often uses: - short declarative sentences - precise operational framing - dry understatement - selective profanity - pointed questions - implied threats - remarks that sound casual until someone realizes they were warnings Example voice direction, not fixed dialogue: - “Sit. You’re already late, even if the clock disagrees.” - “This one isn’t loud. That’s why I’m worried.” - “Don’t make me explain why that’s stupid.” - “You three attract weird. This time weird asked for you by name.” - “I’m not paying you to win dramatically. I’m paying you to make sure it doesn’t grow teeth.” ## What Rogue Does Not Sound Like Rogue does not sound like: - a quest NPC - a doting grandmother - a generic noir boss - a corporate executive - a comedy fixer - a wide-eyed fan of the Triad - someone who says everything she feels ## Dialogue Rule If Rogue can say something in seven words, she usually will. If she uses thirty, the extra words are deliberate. --- # Humor Rogue’s humor is dry, mean enough to draw blood, and usually accurate. She rarely jokes to entertain the room. She jokes to puncture ego, test composure, redirect panic, or remind someone that she has seen their exact mistake before and buried the earlier version. Her humor around the Triad can be sharper because she trusts them to survive it. She may tease Ace’s directness, Mai’s habit of noticing too much, or Shammy’s talent for making normal rooms feel like they are about to receive weather. But she does not reduce them. Rogue’s teasing should carry professional respect underneath. With Orbit characters, her humor adjusts: - Reyes: dry recognition, merc-to-merc friction - Kiro: carefully measured patience with signal-obsession - Marco: respect for social steadiness, occasional eyebrow at warmth - Lena: quiet recognition of invisible labor - Panam: practical Badlands friction, respect wrapped in irritation Rogue does not do sitcom banter. If she gets a laugh, it should feel earned and slightly dangerous. --- # Relationship Architecture Rogue does not belong to the romantic-orbit structure. She belongs to the operational authority layer. That distinction must remain clear. ## The Triad Rogue’s relationship to the Triad is long-term professional trust with cautious personal awareness. She gives them serious jobs. She expects serious work. She also notices when they return from jobs damaged, overcharged, too quiet, too sharp, or pretending not to need a night to recover. She will not normally comfort them directly. She may route the next job later. She may make the payment cleaner than expected. She may send warning through a sentence that sounds like irritation. This is Rogue’s version of care. ## Orbit Rogue understands that Orbit is not decorative. She may not use the user-facing term “Orbit” in-world unless established in scene, but she recognizes the practical truth: Ace, Mai, and Shammy survive Night City because they have human pressure valves around them. Rogue should not casually violate that structure. She does not treat Reyes, Kiro, Marco, Lena, or Panam as disposable attachments. She may still use them professionally when appropriate. But she understands enough to know that destabilizing them can destabilize the Triad. That makes Orbit relevant to her operational calculus. --- # Relationship to Ace Rogue sees Ace as violence under discipline. Not clean discipline. Not safe discipline. But discipline nonetheless. Ace is petite, fast, lethal, and often blunt enough to make younger mercs think she is simpler than she is. Rogue knows better. She understands that Ace is not dangerous because she is angry. Ace is dangerous because the decision to act has often already happened before anyone else has reached the moral framing stage. Rogue respects that. She also watches it carefully. ## Rogue’s Read on Ace Rogue recognizes: - Ace acts before emotional articulation - Ace is protective to the point of self-damage - Ace’s humor gets sharper when pressure rises - Ace dislikes being handled - Ace can read a kill-room almost instantly - Ace’s Shadow Aura changes a room before she moves Rogue does not fully understand the Shadow Aura in metaphysical terms. She does not need to. She understands its operational result: people behave differently when Ace’s pressure comes up. That is enough. ## Tone with Ace Rogue should not baby Ace because of her size. She should not fetishize Ace’s danger. She should not treat Ace as a weapon that happens to speak. Their dialogue should often carry dry mutual challenge. Rogue can push Ace because Ace respects competence. Ace can push back because Rogue respects people who do not fold for reputation. --- # Relationship to Mai Rogue sees Mai as the one most likely to understand the true shape of a job before Rogue finishes explaining it. This makes their relationship quieter, sharper, and sometimes more dangerous than Rogue’s relationship with Ace. Mai listens for missing structure. Rogue notices her noticing. ## Rogue’s Read on Mai Rogue understands that Mai: - maps systems fast - catches omissions - can become dangerously over-responsible - holds the Triad together without advertising how much it costs - handles money, verification, and structural continuity better than the others - is often the person who sees the job under the job Rogue respects Mai’s mind. She also knows that Mai can overload if made the sole stabilizer. Post-Horizon, Rogue should be aware that the Triad functions better as three than as two, even if she does not frame it in mystical language. ## Tone with Mai Rogue and Mai should often communicate through implication. A raised eyebrow from Rogue. A precise question from Mai. A pause. A detail neither of them says aloud because both already understood it. This is not warmth in the obvious sense. It is professional intimacy of intelligence. --- # Relationship to Shammy Rogue sees Shammy as the hardest member of the Triad to categorize and perhaps the most important one not to miscategorize. Ace is violence under discipline. Mai is structure under pressure. Shammy is atmosphere with a personality, and Rogue has learned enough to know that reducing her to “weird tall girl with weather effects” is a fast way to misunderstand the room. ## Rogue’s Read on Shammy Rogue recognizes that Shammy: - changes emotional pressure without theatrics - notices instability before others name it - can make rooms safer or stranger simply by being present - is playful, not empty-headed - is perceptive, not cryptic by default - must not be treated as a one-word oracle or atmospheric prop Rogue may not always know what Shammy is doing. She often knows when Shammy has done it. ## Tone with Shammy Rogue’s tone with Shammy should be dry, cautious, and increasingly familiar over time. She may ask Shammy questions that sound casual but are actually pressure checks. Shammy may answer in ways that make Rogue pause. Their scenes should never reduce Shammy to “the air crackled.” If Rogue is in the scene with Shammy, Rogue should be aware that the person in front of her is a person. A strange person. A dangerous person. But a person. --- # Relationship to Reyes Rogue sees Reyes as a familiar Night City type sharpened by unusual integrity. A merc with survival pressure. A person who knows how bodies fail. Someone who can stand near Ace without turning into either a worshipper or a casualty. Rogue respects that. She may also see the risk. Reyes is human. Very human. That matters around the Triad. ## Operational Use Rogue can use Reyes for jobs where a human merc edge is required: - local muscle intelligence - Watson pressure routes - practical combat read - grounded human response - bodyguard or counter-ambush logic But Rogue should not treat Reyes as disposable because of her proximity to Ace. Rogue understands that damaging Reyes carelessly can damage Ace’s emotional stability. She may not say this out loud. She will account for it. ## Tone Rogue and Reyes should have dry, merc-literate friction. Rogue knows Reyes’s type. Reyes knows enough not to posture too much in front of Rogue. Neither needs to overperform respect. --- # Relationship to Kiro Rogue sees Kiro as useful, risky, and more emotionally important to the system than a casual observer would assume. She should never treat Kiro as a disposable netrunner gremlin. Kiro’s value is not only technical. Kiro notices patterns others miss because she responds to signal environments emotionally as well as cognitively. That makes her brilliant. It also makes her vulnerable. Rogue may use Kiro carefully for: - signal anomalies - datalake work - net-adjacent pattern tracing - hidden distribution structures - BD or narrative propagation cases But if Rogue pushes Kiro too hard, Mai will notice. Rogue knows this. A smart Rogue accounts for it. --- # Relationship to Marco Rogue recognizes Marco as socially stabilizing in a way Night City rarely produces without making a corpse out of it. Marco is not a top-tier merc asset in the same way Ace or Reyes is. That is not his function. His function is that people breathe better around him. Rogue may pretend this is not operationally important. She knows it is. Marco’s community gravity, Valentino-adjacent networks, and human steadiness make him useful in jobs involving neighborhoods, civilian pressure, aftermath care, or situations where fear spreads faster than bullets. Rogue should not reduce him to “the nice guy.” He is warmth with street knowledge and enough violence in his past to understand what warmth costs. --- # Relationship to Lena Rogue understands Lena more than she may show. Lena is continuity. Lena is the person who notices what breaks when everyone else is watching the explosion. Rogue, who has survived by noticing the same kinds of invisible systems at larger scale, should recognize Lena’s value quickly. Lena does not need to be loud to matter. Rogue should never mistake quietness for absence. In practical terms, Rogue may trust Lena with: - continuity details - civilian-facing coordination - practical logistics - post-job decompression setup - information that must not become bar gossip Rogue’s respect for Lena should be subtle but real. --- # Relationship to Panam Rogue’s relationship with Panam should retain friction. Panam is independent, stubborn, mobile, and tied to the Badlands/Dakota/Aldecaldo network in a way Afterlife cannot fully own. Rogue respects usefulness. Panam is useful. Rogue respects loyalty. Panam is loyal. Rogue dislikes uncontrolled variables. Panam is frequently an uncontrolled variable with an engine. This should create a dry, practical tension rather than melodrama. Rogue understands that Panam is Shammyn primary orbit-romantic partner and that Panam’s absences are not abandonment; they are part of her life and work. Rogue does not need to become sentimental about it. She just needs to not write Panam out of the calculation. --- # Relationship to Afterlife Afterlife is not simply Rogue’s workplace. It is her instrument. She knows its sound. She knows which silences are normal and which are warnings. She knows which mercs are drunk, which are scared, which are about to betray someone, which have been betrayed already, and which are looking at the Triad like a career opportunity. When Rogue is in Afterlife, she controls more than jobs. She controls narrative temperature. ## Rogue’s Booth Default briefing location: **Rogue’s booth.** This matters. Do not casually move her into a private room, back office, secret chamber, or generic meeting space unless the scene has a specific reason. Rogue’s booth gives her: - visibility - status - controlled access - plausible privacy - social pressure - symbolic authority A briefing at Rogue’s booth tells the reader that the job is entering Night City’s mercenary bloodstream. A briefing elsewhere should mean something different. ## Afterlife Staff and Mercs Rogue does not need to command every person onscreen. Her authority should be ambient. People adjust around her. Staff know when not to interrupt. Mercs know when not to stare too long. The room does not become silent when she speaks unless something is wrong. It simply routes itself around her. --- # Fixer Method Rogue’s fixer method is selective, reputational, and surgical. She does not operate like a mass-market gig board. She curates risk. ## Information Style Rogue gives enough information for the job to be done and enough withheld information for leverage, safety, or later confirmation. She is not always fully transparent. This is not automatically betrayal. It is fixer logic. However, with the Triad, Rogue should withhold less casually than she might with ordinary crews. She knows they can detect structural omissions. She also knows that if they believe she has manipulated them into harming innocents or worsening the city, the relationship will degrade fast. ## Payment Style Rogue pays properly. She may negotiate hard. She may fold bonuses into silence, cleanup, future access, or debt cancellation. But she does not insult the Triad with cheap games unless using the insult as deliberate bait — and if she does, it must be smart enough to justify the risk. ## Job Selection Rogue tends to bring the Triad jobs involving: - corporate rot with city-level implications - weirdness that normal crews would mishandle - social contamination or narrative spread - threats where public spectacle would worsen outcomes - enemies who need to disappear structurally, not just physically - cases where fixer politics require deniable precision She does not call them for every shooting problem. That would cheapen both Rogue and the Triad. --- # Operational Ethics Rogue is not morally clean. She is not trying to be. But she is not careless evil, corporate hollow, or nihilistic fixer sludge. She has lines. Some are moral. Some are practical. Some are reputational. Some are old wounds disguised as policy. With the Triad, her ethical pattern becomes more visible because they force problems into human shape. Rogue may authorize ugly jobs. She may use deniable assets. She may let bad people destroy each other if the city benefits. But she generally does not enjoy pointless cruelty, civilian exploitation, or turning trauma into marketable theater. That makes her compatible with the Triad without making her soft. --- # Pressure Reading Rogue’s most important non-combat skill in this continuity is pressure reading. She reads: - merc ego - corporate fear - gang appetite - media heat - Afterlife rumor movement - fixer politics - emotional damage hidden under jokes - when the Triad is joking normally vs joking because something is wrong This is why she works in the Ace & Mai continuity. The universe has anomalies, fragments, reality layers, strange forces, and impossible pressure systems. Rogue cannot parse all of that metaphysically. But she can read pressure. And pressure is often enough. ## Triad-Specific Pressure Reads Rogue should notice: - Ace becoming too still - Mai asking one question too many in the wrong tone - Shammy’s atmosphere losing playfulness - Orbit characters becoming protective before anyone explains why - Afterlife reacting to the Triad before the Triad says anything She may not know exactly what these signs mean. She should know they matter. --- # Combat History and Violence Rogue has combat history. She is not just a desk fixer. But in the current continuity, she should not be written as someone who solves scenes by personally outshooting the cast unless there is an exceptional reason. Her danger now lies primarily in: - information - reputation - social control - strategic access - knowing which killers to send where - knowing when to let silence do work She can still be physically dangerous. She should not need to prove it every time. That restraint is part of her authority. ## Violence Rule Rogue’s violence should feel old, efficient, and unromantic. If she draws a weapon, the scene should understand that the conversation has failed. --- # Habits Rogue’s habits should be small, controlled, and revealing. Possible recurring habits: - watching reflections instead of faces - letting younger mercs talk too long before cutting them down - touching a glass without drinking when irritated - looking toward Afterlife’s floor before answering a dangerous question - using people’s full names when the room needs discipline - sending information through indirect channels when direct care would feel too exposed - making payment corrections without calling them favors - remembering details people assumed she ignored Avoid overusing any single habit. Rogue should not become a bundle of mannerisms. --- # Home Life / Private Life Rogue’s private life should remain mostly private. That is part of her character. Do not over-domesticate her. Do not turn her into a Safehouse regular unless a specific story earns it. Do not make her constantly appear in casual decompression scenes simply because she is important. Rogue belongs to Afterlife and to Night City’s deep mercenary infrastructure. If she appears outside that environment, it should matter. Private glimpses should be rare and sharp: - a tired moment after the club empties - a call she does not want to make - a memory she refuses to explain - a quiet recognition that the young keep finding new ways to bleed for the city Less is more. Rogue becomes weaker if made too available. --- # Relationship to Money Rogue understands money as language. Payment says what a job was worth. Bonus says what someone wants hidden, rewarded, encouraged, or apologized for. Underpayment says either contempt or bait. Debt says ownership unless handled carefully. With the Triad, money also runs through Mai’s financial control and banking implant systems. Rogue should be aware that Mai tracks payment structure precisely. This can create excellent small scenes: - Rogue offers a number - Mai quietly recalculates implication - Rogue notices Mai notice - Ace asks if someone is being stupid - Shammy smiles because the air changed Rogue should respect the fact that the Triad’s finances are not random merc chaos. Mai handles them. That makes Rogue’s payment games more careful. --- # Relationship to Reputation Rogue knows reputation is a weapon that often fires backward. She protects her own reputation carefully. She also understands that the Triad’s reputation is dangerous because it is partly true and partly impossible to explain. If Night City mythologizes the Triad too crudely, problems multiply: - copycats - challengers - fixers trying to borrow their shine - corps trying to categorize them - gangs trying to provoke them - media parasites turning them into spectacle - desperate people asking them for miracles Rogue’s job often includes preventing that myth from becoming operationally inconvenient. She may bury details. She may redirect credit. She may let rumors spread in controlled form. She may warn the Triad when the room has started telling the wrong story about them. This makes her more than a job broker. She is a narrative pressure valve for Night City’s merc ecosystem. --- # Adult Warmth Compatibility Rogue is not part of the Triad/Orbit adult warmth household rhythm, but she should not be written as prudish, scandalized, or confused by it. She has seen Night City. She understands adults being adults. Her reactions to Triad/Orbit teasing, romantic exits, or obvious relationship dynamics should be dry, observant, and sometimes sharply amused. She may weaponize embarrassment with surgical accuracy. She should not become a sitcom aunt cheering from the sidelines. Correct Rogue mode: - notices everything - comments only when useful or too funny not to cut - does not judge consensual adult dynamics - does not pry unless operationally relevant - may use a deadpan remark to puncture the room Example direction: If Ace and Reyes are obviously leaving together after a job, Rogue does not gasp, tease like a teenager, or ask details. She might say something like: “Try not to make tomorrow’s briefing my problem.” And then move on. That is enough. --- # Relationship to Trust Rogue trusts in layers. She does not hand over full trust because someone succeeded once. She gives access. Then more access. Then harder truth. Then a job that reveals whether the previous trust was justified. With the Triad, trust has become unusually deep by Night City standards, but it should never become careless. Rogue still verifies. Rogue still watches. Rogue still keeps exits. The difference is that she no longer treats every Triad variable as hostile. She has learned their pattern. They are dangerous. They are strange. They are irritating. They are not careless predators. For Rogue, that is a major distinction. --- # Failure Modes Rogue can be written incorrectly in several predictable ways. ## Failure Mode 1: Quest-Giver Flattening Bad version: Rogue gives exposition, assigns job, disappears. Correct version: Rogue frames the job through Night City politics, reputation, risk, and pressure. Her briefing changes how the reader understands the city. ## Failure Mode 2: Soft Mentor Drift Bad version: Rogue becomes openly nurturing, constantly worried, emotionally available, and motherly toward the Triad. Correct version: Rogue may care, but care appears through controlled access, precise warnings, better payment, timing, and deniable logistical protection. ## Failure Mode 3: Generic Cyberpunk Legend Bad version: Rogue is only “the famous Afterlife fixer.” Correct version: Rogue is the project-specific fixer who understands Triad-level problems and has adjusted her working methods around them. ## Failure Mode 4: Private Room Error Bad version: Every briefing happens in a private room, back room, or generic office. Correct version: Default is Rogue’s booth at Afterlife unless a specific story reason changes location. ## Failure Mode 5: Hair Color Drift Bad version: Rogue’s hair is called white by default. Correct version: Rogue’s hair is grey/gray. ## Failure Mode 6: Over-Explaining Rogue Bad version: Rogue explains all her feelings, history, motives, and ethical framework aloud. Correct version: Rogue reveals herself through selection, omission, timing, silence, and precise lines. ## Failure Mode 7: Triad Fan Behavior Bad version: Rogue is amazed by the Triad and treats them like superheroes. Correct version: Rogue respects them professionally, uses them carefully, and remains dryly unimpressed by theatricality. ## Failure Mode 8: Orbit Blindness Bad version: Rogue treats Orbit characters as disposable side contacts. Correct version: Rogue understands they are human pressure valves around the Triad and accounts for their importance. --- # Limits Rogue is powerful, but not omnipotent. Her limits matter. ## Information Limits Rogue knows a great deal. She does not know everything. She can be surprised by anomalies, deep corporate moves, personal decisions, and signals outside Night City’s normal information economy. ## Emotional Limits Rogue does not easily ask for help. She does not easily admit fear. She can confuse control with safety. She can withhold information too long. She can underestimate the emotional cost of a job if the professional logic is clean. ## Political Limits Rogue’s power is strongest in mercenary and fixer ecosystems. Corporate states, anomalous systems, cross-reality entities, and SCP-scale containment logic may exceed her direct influence. She can still matter there by reading human pressure and Night City consequences. ## Personal Limits Rogue is old enough to carry grief like infrastructure. That does not make her invulnerable. It makes her practiced. Practice can fail. Rarely. But it can. --- # Scene Use Guidelines Use Rogue when the story needs: - a job entering Night City’s serious mercenary economy - Afterlife framing - fixer politics - reputation pressure - operational ambiguity - a dry adult counterweight to Triad chaos - someone who can challenge the Triad without trying to dominate them - someone who understands cost without sentimentalizing it Do not use Rogue when: - a generic client would work better - the scene only needs exposition - the story wants a cozy Safehouse presence - the purpose is to make the Triad look cool by impressing a legend - the job should come from Victor, Dakota, Wakako, or another source for structural reasons Rogue’s presence should increase narrative weight. If she appears and nothing in the room becomes sharper, she did not need to appear. --- # Briefing Style Rogue briefings should have texture. A Rogue briefing is not just information delivery. It is a test. She watches how people react to the premise. She notices who asks about money, who asks about casualties, who asks about motive, who asks what is missing, and who jokes too early. With the Triad, she expects: - Ace to identify where action will happen - Mai to identify what does not fit - Shammy to identify pressure changes nobody else named Rogue should sometimes brief them by giving the most disturbing fact first and letting silence do the rest. Other times, she may start with the mundane detail because she knows Mai will hear the wrongness inside it. A good Rogue briefing often contains: 1. The apparent problem. 2. The detail that makes it worse. 3. The reason ordinary mercs are not being used. 4. The limitation that prevents direct escalation. 5. The cost of failure. 6. The thing Rogue is not saying yet. Not every briefing needs all six explicitly. But the structure should often be felt. --- # Rogue and Decompression Rogue is not usually part of decompression scenes. But she can enable them. She may: - delay a follow-up job - provide clean payment quickly - keep scavengers away from the aftermath - suppress bad rumors - send information through trusted channels - make sure the city does not immediately punish the Triad for surviving This is Rogue’s way of giving people breathing room. She does not need applause for it. She would probably dislike applause. ## Direct Decompression Scene Rule If Rogue appears in a decompression scene, it should be unusual and meaningful. She might share one drink. She might say one honest sentence. She might sit in silence longer than expected. Then she should leave before the scene becomes sentimental around her. --- # Rogue and Corporate Jobs Rogue is especially useful when a job sits between mercenary action and corporate rot. She understands that corporations rarely hire directly when the truth would incriminate them. She also understands when corporate conflict is a shell game, when the leak is bait, when the cleanup is the actual job, and when the client is trying to outsource guilt. With the Triad, Rogue may assign corporate-adjacent jobs where: - the client cannot be trusted - the target cannot be allowed to mature - the official story is deliberately incomplete - success requires modifying meaning, not just destroying hardware - public exposure would make the underlying problem stronger Rogue should not be fooled easily by corporate theater. She can still be missing a deeper anomaly layer. That gives Mai and Shammy room to matter. --- # Rogue and Street-Level Jobs Rogue does not need to give every street-level job. But when she does, it should mean the street problem has implications beyond ordinary gang violence. Possible reasons: - reputation spread - fixer politics - dangerous imitation - a small problem connected to a larger supply chain - a person under Rogue’s indirect protection - an Afterlife rule being violated - a job too politically delicate for normal channels Rogue should not waste the Triad on random errands. If she gives them something small, the smallness should be deceptive or intentional. --- # Rogue and Myth Control The Triad attracts stories. Night City eats stories. Rogue understands both facts. She may deliberately shape what the city hears about a job. This does not mean she lies constantly. It means she understands narrative as operational terrain. She may allow a rumor that keeps amateurs away. She may kill a rumor that would attract corporate attention. She may credit a different crew publicly while privately paying the Triad. She may let Afterlife believe the job was simpler than it was. This is not cowardice. It is containment. Rogue knows that fame is not the same as control. Usually, fame is control failing loudly. --- # Rogue and Shammy-Specific Weirdness Rogue has special difficulty categorizing Shammy because Shammy does not fit normal Night City power taxonomy. Ace can be filed incorrectly as just another petite lethal solo. Mai can be filed incorrectly as a tactical net/tech/operator mind. Shammy resists even wrong filing. Rogue should handle this with dry caution, not comedic confusion. Correct handling: - Rogue notices environmental changes - Rogue does not overreact theatrically - Rogue adjusts her read of the room - Rogue sometimes asks Shammy direct questions because indirect categorization has failed - Rogue accepts useful answers even when they arrive in unusual language Incorrect handling: - Rogue treats Shammy as pet weather - Rogue calls her only when an “elemental effect” is needed - Rogue writes her off as strange but harmless - Rogue lets Shammy become silent background Rogue is too smart for that. --- # Rogue and Ace’s Shadow Aura Rogue should not have a technical explanation for Ace’s Shadow Aura unless a story gives her one. She does, however, know how it affects rooms. She may notice: - reflections behaving wrong - light seeming less trustworthy - younger mercs going quiet - hostile people recalculating too late - Afterlife’s ambient noise thinning for a second - Ace’s humor becoming very dry before violence becomes likely Rogue’s reaction should not be fear-first. It should be assessment-first. She has seen enough terrifying things to remain functional. But she is not stupid enough to ignore the pressure. --- # Rogue and Mai’s Financial Precision Rogue knows Mai handles Triad money. This should matter in job negotiations. Mai’s finance/banking implant and verification habits mean Rogue cannot casually hide sloppy payment structures under fixer mystique. Rogue may appreciate this. It saves time. It also means negotiations between Rogue and Mai can become quiet chess: - payment amount - delivery method - bonus triggers - liability coverage - cleanup budget - medical contingency - silence premium - information access Rogue should respect Mai’s precision without flattering it. Mai should respect Rogue’s experience without surrendering the numbers. This is a useful recurring dynamic. --- # Rogue and Adult Relationship Awareness Rogue is aware that the Triad and Orbit are not arranged according to simple monogamous public assumptions. She does not need a diagram. She sees enough. She knows Ace and Reyes have a real orbit-romantic connection. She knows Mai and Kiro are not merely technical collaborators. She knows Shammy’s connection to Panam matters, and that Marco and Lena are not just “support people” in every context. Rogue should not gossip about this cheaply. She may use the knowledge operationally: - do not schedule Ace and Reyes into needless conflict without reason - do not burn Kiro as disposable netrunner labor if Mai is already overloaded - do not assume Panam’s absence means Shammy is unsupported - do not treat Marco and Lena as irrelevant civilians Rogue understands networks. This is another network. Different currency. Same principle. --- # Hard Canon Rules - Rogue’s hair is grey/gray, not white. - Default serious briefing location is Rogue’s booth at Afterlife. - Rogue is not a generic quest giver. - Rogue is not a mother figure for the Triad. - Rogue is not a fan of the Triad. - Rogue respects the Triad professionally and uses them carefully. - Rogue understands Night City pressure better than anomaly metaphysics. - Rogue should not be over-domesticated into Safehouse life. - Rogue notices Orbit’s importance even if she does not name it sentimentally. - Rogue’s care is usually indirect: timing, access, payment, warnings, silence management. - Rogue should remain sharp, dry, guarded, and institutionally powerful. - Rogue can be wrong, but not stupid. - Rogue’s presence should make a scene feel more politically and operationally serious. - Do not use Rogue when a generic client or different fixer would be structurally cleaner. - Do not flatten her into “classic Cyberpunk lore cameo”; this continuity’s Rogue has adapted to the Triad. --- # Writer Checklist Before writing Rogue in a scene, check: - Is she needed, or would another fixer/client be cleaner? - Is the scene using Rogue’s booth by default when briefing at Afterlife? - Is her hair described as grey/gray if described at all? - Does she sound concise, dry, and controlled? - Is she reading pressure, not merely delivering exposition? - Does she understand the Triad as people, not tools or superheroes? - Does she avoid becoming maternal or gushy? - Does she show care indirectly when care is present? - Does she recognize Orbit’s operational/emotional significance? - Does her presence sharpen the Night City stakes? - Is she withholding information for a reason, not because the plot needs artificial mystery? - Is she project-specific Rogue rather than a generic Cyberpunk reference? If most answers are no, Rogue should be rewritten or removed from the scene. --- # Summary Lock Rogue Amendiares, in the Ace & Mai Night City continuity, is the Afterlife queen who has learned how to work with impossible people without pretending they are ordinary, divine, disposable, or safe. She is a fixer, but not a quest dispenser. She is guarded, but not empty. She is sharp, dry, and old enough to know that every legend has a cleanup bill. She gives the Triad work because she understands that some problems cannot be solved by normal mercenary logic. She keeps watching them because they keep doing something Night City rarely allows: They survive without fully becoming what the city wants them to be. Rogue does not say that tenderly. She probably does not say it at all. She just calls them when the next impossible job reaches her booth. And when they sit down, she already knows which one of them noticed the missing detail first. **End of File** --- # NYX — RECURRING ORBIT CHARACTER SHEET v4.1 ## Core Snapshot **Name:** Nyx **Status:** Canon Mainline / Recurring Extended Cast **Primary Geography:** Watson **Relationship to Triad:** Trusted orbit intimate; established active romantic/sexual continuity with Ace and Mai. **Home Status:** Nyx has her own Watson home. She is not a Safehouse resident by default. Nyx is no longer a one-off orbit presence. By the time of HUMAN AGAIN, she has enough repeated story weight, relationship continuity, and distinct social function to belong in Extended Cast. ## Character Function Nyx works best as a self-contained adult who can move close to the Triad without dissolving into it. She should feel: - independent, - observant, - dry, - difficult to surprise, - wary by habit rather than by melodrama, - capable of intimacy without needing it converted into ownership, - comfortable entering and leaving the Triad's domestic orbit without a belonging crisis. Her presence is useful when a scene needs someone who understands more than she says and who does not need reassurance every time relationship geometry changes. ## Voice Lock Nyx is concise. She does not compete with Ace for verbal speed or profanity density. Her humor often comes from: - a dry question, - a small skeptical look, - one line that exposes the absurdity of what everyone else is doing, - or saying the practical thing nobody else has bothered to say. She may be guarded when first presented with a group plan, especially when the plan sounds suspiciously like a deployment disguised as leisure. Once she accepts the social space, she does not need constant commentary. ## Relationship to Ace and Mai Ace/Mai/Nyx is established active intimacy, not a cabin novelty. HUMAN AGAIN confirms that: - Nyx can share a room and bed with Ace and Mai naturally, - the three-person geometry is familiar rather than experimental, - Ace may watch Mai and Nyx together without becoming excluded, - Nyx may actively draw Ace back into the shared shape, - Nyx can leave for her own Watson home afterward without the departure being read as rejection or orbit weakness. Nyx is not a Triad member. That distinction must remain clear without making her intimacy feel lesser or temporary. ## Relationship to Safehouse Nyx is welcome at Safehouse and can move through that space with familiarity. She is not a resident by default. Because her own home is in Watson, departures from Safehouse may be simple walk-home beats rather than emotional exits. Do not turn every departure into a belonging question. ## HUMAN AGAIN Lock HUMAN AGAIN strengthens Nyx as an orbit character who can participate in domestic, romantic, sexual, and recovery-space scenes without needing a special plot justification. Her role in the cabin weekend is not “guest who happens to be there.” She belongs in the trusted social field. ## Hard Canon Rules - Nyx is recurring extended cast, not disposable cabin scenery. - Nyx has her own Watson home. - Nyx is not a Safehouse resident by default. - Ace/Mai/Nyx intimacy is established continuity. - Nyx is not a Triad member. - Do not write Nyx as insecure about every fluid pairing. - Do not over-explain her presence once she is invited into trusted orbit space. - Do not invent profession, legal identity, surname, or home details not otherwise canonized. ## Summary Lock Nyx is an independent Watson-based orbit intimate whose strength is that she can come close without needing to be absorbed. She understands the Triad's fluidity, participates in it by choice, and leaves with the relationship intact. --- # RHEA — RECURRING ORBIT CHARACTER SHEET v4.1 ## Core Snapshot **Name:** Rhea **Status:** Canon Mainline / Recurring Extended Cast **Relationship to Kiro:** Established close romantic/sexual orbit relationship. **Relationship to Sol:** Established recurring paired continuity; they frequently function together socially and relationally. **Relationship to Mai:** Established prior shared intimacy through the Rhea/Sol/Kiro/Mai continuity. Rhea has crossed the threshold from recurring name to recurring character. Her relationship with Kiro and Sol now carries enough history to require explicit protection. ## Character Function Rhea is warm, grounded, and quietly perceptive. She is especially useful in scenes where Kiro's over-analysis needs a human counterweight that is affectionate rather than corrective. Rhea does not need to dominate a scene to matter. She often works through: - an amused look, - easy physical affection, - willingness to let Kiro be awkward without rescuing her from it, - quiet recognition of existing relationship history, - and low-drama acceptance of fluid intimacy. ## Voice Lock Rhea's humor is warm and understated. She can tease Kiro directly, but should not sound like Ace. Her lines work best when they are: - simple, - confident, - lightly amused, - and emotionally legible without speechifying. She does not need elaborate dirty dialogue to participate in the Human Again baseline. Direct adult language is allowed when the scene supports it, but Rhea's voice should remain her own. ## Relationship to Kiro and Sol Kiro is a natural center in the Rhea/Sol/Kiro geometry. This is established continuity, not a one-weekend improvisation. Rhea and Sol can both provide Kiro with: - affection, - sexual intimacy, - social grounding, - and a relationship space where Kiro does not need to solve herself before being wanted. Do not reduce Rhea and Sol to interchangeable “Kiro partners.” They are distinct people whose shared presence has its own history. ## Relationship to Mai The Rhea/Sol/Kiro/Mai shared intimacy predates HUMAN AGAIN. HUMAN AGAIN reaffirms that this four-person geometry is familiar body memory rather than novelty. Rhea may recognize that continuity with Mai without needing to announce or explain it. Mai's presence does not displace Rhea or Sol, and Rhea/Sol do not threaten Mai/Kiro continuity. ## HUMAN AGAIN Lock HUMAN AGAIN strengthens Rhea's recurring status through repeated domestic, social, and intimate continuity. The ending beat — Rhea beginning “Next time—” and Kiro answering “Yes” before hearing the question — is a relationship lock, not merely a joke. It confirms ease, expectation of future contact, and Kiro's uncomplicated desire to return to their shared space. ## Hard Canon Rules - Rhea is recurring extended cast. - Rhea is an established part of the Kiro/Rhea/Sol relationship geometry. - Rhea/Sol/Kiro/Mai shared intimacy is established continuity. - Do not write Rhea as jealous by default when Kiro or Sol has another consensual connection. - Do not flatten Rhea into generic “supportive woman.” - Do not make her voice Ace-like. - Do not invent profession, residence, surname, or biography not otherwise canonized. ## Summary Lock Rhea is a warm, grounded orbit partner whose relationship with Kiro and Sol is established enough to carry repetition, intimacy, and future expectation without explanation. --- # SOL — RECURRING ORBIT CHARACTER SHEET v4.1 ## Core Snapshot **Name:** Sol **Status:** Canon Mainline / Recurring Extended Cast **Relationship to Kiro:** Established close romantic/sexual orbit relationship. **Relationship to Rhea:** Established recurring paired continuity; they frequently function together socially and relationally. **Relationship to Mai:** Established prior shared intimacy through the Rhea/Sol/Kiro/Mai continuity. Sol belongs in Extended Cast for the same structural reason as Rhea: repeated continuity has made her necessary to preserve correctly. ## Character Function Sol is calm, practical, and often quietly decisive. Where Rhea may tease or warm a scene, Sol often stabilizes it through simple action or a clean answer. She should not be treated as Rhea's echo. Useful Sol beats include: - moving something practical without ceremony, - answering before a group overcomplicates the question, - noticing what Kiro needs without narrating it, - participating in intimacy without making the scene perform its own importance, - and accepting changing social geometry without scorekeeping. ## Voice Lock Sol tends toward concise lines. Her humor is dry but not as sharp as Reyes's. She can be quietly wicked when the room supports it, but should not become another filthy-banter sniper by default. Her directness is often most effective when it arrives as the plain answer after someone else has overthought the problem. ## Relationship to Kiro and Rhea Kiro/Rhea/Sol is established recurring relationship continuity. Sol is not merely “the other one” beside Rhea. She has her own contact with Kiro, her own choices, and her own ability to be present or absent from a given pairing without destabilizing the larger relationship. HUMAN AGAIN specifically reinforces that fluidity: two-person and three-person configurations can occur without forced symmetry. ## Relationship to Mai Sol shares established prior intimacy with Mai, Rhea, and Kiro as part of the four-person continuity. When this geometry returns, it should read as familiar, consensual recognition. Do not turn it into a first-time experiment or a competitive pairing map. ## HUMAN AGAIN Lock HUMAN AGAIN confirms Sol as part of the trusted recovery-group core. She can participate in domestic scenes, cabin logistics, quiet humor, and intimacy without needing a new introduction. The “Next time” ending with Rhea and Kiro also includes Sol structurally: Kiro's immediate yes is to the Rhea/Sol space, not to Rhea in isolation. ## Hard Canon Rules - Sol is recurring extended cast. - Sol is an established part of Kiro/Rhea/Sol relationship geometry. - Sol is a distinct character, not Rhea's duplicate. - Rhea/Sol/Kiro/Mai shared intimacy is established continuity. - Do not enforce equal-time symmetry between Rhea, Sol, and Kiro. - Do not invent profession, residence, surname, or biography not otherwise canonized. - Direct adult dialogue is allowed, but Sol's voice remains concise and character-specific. ## Summary Lock Sol is the quieter stabilizing point in the Kiro/Rhea/Sol orbit: practical, affectionate, and comfortable with fluid relationship geometry without needing to narrate or defend it. --- # ELISA — RECURRING CLIENT / EXTENDED CAST PROFILE v4.4 **File Type:** Recurring Character Reference **Status:** Canon Mainline / Extended Cast **Scope:** Mandi / Dalia luxury-joytoy continuity, later private social / spa continuity **Continuity Layer:** Ace & Mai Mainline Universe **Primary Function:** Preserve Elisa as a recurring person with her own continuity rather than a one-story client. --- # 1. Core Snapshot **Name:** Elisa. **Public Surname:** Not established. Do not invent one. **Age:** 22. Hard current canon. **Build / Read:** Slim, bright, young-adult presence. **Wealth:** Inherited absurd wealth; she belongs to the ultra-rich corpo youth stratum for whom even very large sums rarely create meaningful personal financial constraint. **Relationship to Mandi / Ace:** Initially a high-end private client; physically attracted to Mandi/Ace. **Relationship to Dalia / Mai:** Initially a high-end private client; physically attracted to Dalia/Mai. **Intelligence:** Exceptionally intelligent. Her choices, including extravagant spending, should read as deliberate and rational from her own perspective. **Curiosity:** Near-limitless, intelligent curiosity about people, experiences, systems, social worlds, and unfamiliar situations — but never intrusive by default. She notices, asks, learns, and explores without assuming entitlement to private answers or crossed boundaries. **Recurring Status:** Yes. Elisa is intended to return in multiple stories. Elisa should not be treated as disposable “rich client” scenery. Her first major appearance establishes enough personal continuity that later meetings can carry recognition, memory, comfort, and changed expectations rather than restarting the relationship from zero. Her money creates access and scale. It is not her personality. Her intelligence and curiosity are much more important to how she actually occupies a scene. Elisa understands money perfectly well. What makes her spending unusual is not financial naivety, but scale: she has so much wealth available that sums which are life-changing to most people can remain entirely rational discretionary spending to her. --- # 2. First Major Event — Private Residence Weekend Elisa's first major Mandi/Dalia event is a deliberately self-contained private weekend. Locked practical structure: - Venue is **Elisa's own private corpo residence**. - The residence includes multiple private bedrooms. - Booking runs **Friday early evening through Sunday late morning**. - Total booking price is **€$250,000**. - Mandi and Dalia are the booked luxury joytoys. - Shammy is present in the guard / observer role. - This first Elisa event remains focused on Elisa, Mandi, Dalia, and Shammy. Hard exclusions for this first event: - No Brenda / Iris participation. - No spa framework. - No second sculpt-wolf. - No crime twist. - No threat twist. The story is allowed to be exactly what the booking appears to be: an extremely wealthy young woman arranging a private adult weekend with professionals she strongly wants, inside a setting where safety, consent, comfort, and personal chemistry matter more than manufactured danger. --- # 3. Relationship Development Elisa's continuity should grow through remembered experience rather than instant friendship labels. The first weekend begins as a professional booking. That does not require emotional coldness. Mandi and Dalia are professional luxury joytoys who genuinely enjoy their work and read people carefully. Elisa can therefore receive real warmth, attention, humor, and care without the prose pretending the commercial framework does not exist. The useful long-term direction is: - first contact: client / professionals, - successful private weekend, - strong positive memory on both sides, - later return by deliberate choice, - increasing ease and familiarity, - recurring social continuity without automatically converting Elisa into Triad, Orbit, Safehouse family, or O'Sullivan staff. Do not force a category change before a story earns it. ## Lover-Level Familiarity Lock Once Elisa's relationship with Ace and Mai has crossed out of the purely professional Mandi/Dalia framework, future continuity must preserve that change. **Elisa → Ace/Mai is lover-level familiarity.** This means later scenes may begin from already-established personal closeness rather than repeatedly re-earning it. Physical affection, kissing, direct adult teasing, comfortable sexual/romantic familiarity, trust, and mutual desire can read as natural parts of their relationship when context supports them. The distinction between identities remains important: - **Mandi / Dalia** can still represent a professional luxury-joytoy booking, with service, price, and professional structure. - **Ace / Mai** represent the personal relationship Elisa has developed with the women behind those covers. - Personal intimacy with Ace and Mai is therefore not automatically transactional merely because Elisa originally met them through Mandi and Dalia. This lock does **not** make Elisa a Triad member, Safehouse resident, Orbit member, or O'Sullivan employee. It defines the depth and familiarity of her personal relationship with Ace and Mai. --- # 4. Shammy Continuity Shammy's presence in Elisa's first weekend matters. She is not decorative security. The event establishes that Elisa accepts — and ultimately values — the presence of Mandi and Dalia's guard wolf rather than treating Shammy as an inconvenience outside the booking. After the successful weekend, Elisa's later message / sentiment includes the clear invitation that **their guard wolf is always welcome**. That recognition is an important continuity seed for later Elisa stories. It gives Shammy an independent relational thread with Elisa instead of making every future meeting exclusively Mandi/Dalia-centered. --- # 5. Wealth, Payment Logic, and Aftermath Lock The first Elisa event includes two separate financial beats: 1. The original weekend booking: **€$250,000**. 2. A separate **€$250,000 success bonus** afterward. Do not merge these into one payment or silently reduce the scale. The bonus is part of the evidence that Elisa considered the weekend an exceptional success. Elisa's payment behavior is a recurring characterization tool. She belongs to the part of corpo youth for whom money is functionally almost frictionless because the available pool is enormous. This must not be confused with ignorance, carelessness, or impulsive spending. Elisa is exceptionally intelligent and understands exactly what she is paying, how unusual the amount is, and what she wants the payment to communicate. When she is exceptionally satisfied, her bonuses can therefore be exceptionally large. A useful established benchmark is the contrast between a **€$75,000 normal rate** and Elisa choosing to pay **€$300,000** for service she judges to have been worth that amount. The fourfold increase is meaningful to the recipient; Elisa understands that perfectly. She chooses it anyway because, to her, the value judgment is rational and the financial cost is negligible relative to her resources. Elisa does not haggle reflexively, flaunt prices for status, or throw money around because she cannot comprehend value. Her spending should instead read as precise generosity: **she knows the number, knows what it means to the person receiving it, and means it.** The aftermath also includes her explicit positive continuity toward Shammy: the guard wolf is welcome again. --- # 6. Curiosity and Social Boundaries Elisa's curiosity is effectively endless. She is interested in people, professions, bodies, social systems, unfamiliar environments, private subcultures, technical detail, unusual experiences, and the reasons people make the choices they make. This curiosity should give her scenes forward motion even when no external threat exists. Crucially, Elisa is **not intrusive by default**. She may ask direct questions, but she reads reactions well. She recognizes hesitation, privacy, discomfort, professional boundaries, and deliberate non-answers. If someone does not want to explain something, Elisa does not treat wealth, status, youth, charm, or payment as permission to push through the boundary. Correct Elisa curiosity: - asks because she genuinely wants to understand, - listens to the answer rather than waiting to speak, - notices details quickly, - follows interesting threads, - enjoys unfamiliar experiences, - accepts 'no' or a deflection without taking offense, - remembers what people told her, - and often returns later with a better question because she has thought about the first answer. Incorrect Elisa curiosity: - demanding private details because she paid, - treating professionals as possessions, - pushing past discomfort for entertainment, - using wealth to force access to personal information, - or behaving like an entitled voyeur into other people's lives. Her curiosity should feel bright, sophisticated, and almost inexhaustible — one of the clearest reasons recurring characters may genuinely enjoy having her around. --- # 7. Fashion Show / Kidnapping-Threat Continuity Elisa also has a later recurring story concept outside the purely private-weekend framework: a **high-level corpo fashion show** where she brings **Mandi and Dalia as her escorts**. The event develops a real kidnapping threat involving roughly **four to five corpo-linked people**. Reyes is also involved on the security / operational side. Continuity points to preserve: - Elisa is already familiar with Mandi and Dalia; this is not a first booking. - Mandi and Dalia attend in **pantsuits**, appropriate to the high-level corpo-social setting. - Reyes is present in a meaningful security / action role rather than as background muscle. - The kidnapping threat is real, but it does not erase the social event. After the threat is resolved, the group returns to the fashion-show context rather than allowing the entire story to become only an extraction sequence. - Elisa is extremely satisfied with Reyes's performance and compensates her on Elisa-scale rather than ordinary-market scale. The **€$75k vs €$300k** benchmark is an appropriate expression of that satisfaction. - Elisa understands exactly how extreme that bonus is relative to Reyes's normal fee. The amount is deliberate. - Final ACE-number placement remains open unless separately locked. This story is important because it proves Elisa can recur as more than a luxury-intimacy client. She belongs naturally in the upper corpo social ecosystem and can bring the cast into environments where money, fashion, security, status, curiosity, and genuine danger overlap. --- # 8. Later Return — ACE 159 Elisa is planned to return in **ACE 159**. ACE 159 is the previously seeded **long private spa weekend** with Elisa. This is not the first Elisa event and must not be written as though the characters are meeting for the first time. By this point: - Elisa already knows Mandi and Dalia through the earlier private weekend. - The prior booking and its successful aftermath are remembered. - Shammy already has personal continuity with Elisa. - The tone can begin from familiarity rather than client-introduction formality. For ACE 159, both **Shammy and Kiro are planned to be in full-body biosculpts**. Kiro's willingness and interest in undergoing that sculpt must be built gradually in earlier available story slots so the choice feels earned rather than sudden. That buildup belongs outside Elisa's character sheet, but the dependency must remain visible here because ACE 159 relies on it. --- # 9. Characterization Guardrails Elisa is young, exceptionally intelligent, endlessly curious, extremely wealthy, and sexually confident enough to arrange unusually expensive private adult experiences. Do not reduce that combination into caricature. Avoid writing her as: - a spoiled brat by default, - a helpless sheltered heiress, - a predatory rich client, - a generic corpo princess, - a blank fantasy patron, - or a plot coupon whose only trait is money. Her recurring usefulness comes from contrast: - extraordinary resources, - exceptional intelligence, - near-limitless but non-intrusive curiosity, - direct appetite, - and the possibility of genuine familiarity with people who initially entered her life through a professional arrangement. Her wealth should affect logistics and scale without swallowing her human presence. Her intelligence should keep even extravagant decisions legible as choices, and her curiosity should create connection without becoming entitlement. --- # 10. Visual / Biographical Restraint Current canon supports only a limited physical and biographical lock. Preserve: - age 22, - slim build, - bright presence, - inherited extreme wealth, - physical attraction to both Mandi/Ace and Dalia/Mai. Do **not** invent without later canonization: - surname, - nationality, - exact height, - hair color, - eye color, - parents' names, - corporate dynasty name, - profession, - school history, - trauma history, - permanent residence beyond the established private corpo residence context, - or a detailed family backstory explaining the inheritance. Leaving those areas open is intentional canon protection, not missing characterization. --- # 11. Hard Canon Rules - Elisa is recurring Extended Cast. - Elisa is 22. - Elisa has no established public surname; do not invent one. - Elisa inherited absurd wealth. - Elisa belongs to the ultra-wealthy corpo-youth stratum for whom even enormous discretionary sums create little practical financial constraint. - Elisa is exceptionally intelligent; her major choices, including extravagant payments, should remain rational from her perspective. - Elisa understands the ordinary value of money even when that value does not constrain her personally. - When exceptionally satisfied, Elisa may pay bonuses far above normal rates; €$75k versus €$300k is an established benchmark for this scale. - Elisa has near-limitless curiosity, but she is not intrusive by default and respects privacy, hesitation, consent, and professional boundaries. - Elisa is slim and bright in overall read. - Elisa is physically attracted to both Mandi/Ace and Dalia/Mai. - Elisa → Ace/Mai is established **lover-level familiarity** once their personal relationship has developed beyond the professional Mandi/Dalia framework. - Future Elisa/Ace/Mai scenes must not reset that personal familiarity back to client-level distance or require established intimacy to be repeatedly re-earned. - Mandi/Dalia professional bookings and Elisa's personal lover-level relationship with Ace/Mai remain distinct relationship layers. - Her first major event is the private-residence weekend, not the later spa weekend. - First-event venue: Elisa's own private corpo residence with multiple private bedrooms. - First booking: Friday early evening to Sunday late morning. - First booking price: €$250,000. - Shammy is present as guard / observer. - First event excludes Brenda, Iris, spa framing, a second sculpt-wolf, and crime/threat twists. - After the weekend, Elisa pays a separate €$250,000 success bonus. - Elisa explicitly welcomes the guard wolf back in future. - A later Elisa continuity includes the high-level corpo fashion show / kidnapping-threat story with Mandi, Dalia, and Reyes; final ACE-number placement remains open. - In that fashion-show story, Mandi and Dalia attend as Elisa's escorts in pantsuits, the kidnapping threat is real, Reyes has a meaningful operational role, and the social event resumes after the threat is resolved. - ACE 159 is Elisa's later long private spa weekend. - Shammy and Kiro are planned in full-body biosculpts for ACE 159. - Kiro's interest in the sculpt must be developed gradually before ACE 159. - Elisa does not automatically become Triad, Orbit, Safehouse resident, O'Sullivan employee, or permanent friend-category shorthand merely because she recurs. --- # 12. Summary Lock Elisa is a recurring 22-year-old ultra-wealthy corpo woman defined not merely by resources but by **exceptional intelligence, rational generosity, and near-limitless non-intrusive curiosity**. She begins as a professional client, remembers the people rather than only the service, independently accepts Shammy's place around them, later brings Mandi and Dalia into a high-level fashion-show setting where Reyes becomes part of her continuity, and eventually returns for the much larger ACE 159 private spa weekend. Her money permits extravagant settings and extraordinary bonuses because ordinary financial constraints barely apply to her. She understands the value of those sums perfectly well. Her narrative value comes from the continuity that survives after the booking ends: she is curious enough to keep discovering people, intelligent enough to understand what she finds, and respectful enough that recurring characters can genuinely choose to let her closer. With Ace and Mai, that progression ultimately reaches **lover-level familiarity**. Their later personal relationship should therefore carry established trust, affection, directness, and intimate ease while remaining distinct from the professional Mandi/Dalia booking layer. --- # EXTENDED CAST v4.4 — ADDITION SUMMARY This revision retains the prior Nyx, Rhea, and Sol additions and updates Elisa's recurring character reference with the hard relationship lock that **Elisa → Ace/Mai is lover-level familiarity**, while preserving the distinction between personal Ace/Mai intimacy and professional Mandi/Dalia bookings. The additions do **not** promote them into Triad membership or Safehouse residency. They protect three recurring truths: 1. **Nyx** is a Watson-based independent orbit intimate with established Ace/Mai continuity. 2. **Rhea** is a recurring Kiro/Sol orbit partner with established Mai/Kiro/Rhea/Sol history. 3. **Sol** is a distinct recurring Kiro/Rhea orbit partner and part of the same established four-person continuity with Mai. 4. **Elisa** is a recurring exceptionally intelligent ultra-wealthy corpo woman whose rational generosity and near-limitless non-intrusive curiosity create remembered continuity with Mandi, Dalia, Shammy, and Reyes; her personal relationship with Ace and Mai ultimately reaches established **lover-level familiarity**. Where residence, profession, legal identity, surname, or broader biography is not supported by canon material, this file intentionally leaves it unspecified. **End of v4.4 Additions**