Modular outline

A. Title

Sand Veils

B. Chapter Function

Mike wakes in the sand-veiled desert with no usable memory, learns the place is not a RUN, endures repeated deaths, follows the parchment instructions, and reaches the technological chamber inside the obsidian vessel.

C. Required Context Before Chapter

The reader begins with Mike's disorientation. Mike does not remember the mission, the crew, RT-874, or why he is in a human replacer. The only immediate facts are the hostile desert, the parchment instructions, and Kallom's distant guidance.

D. Character State at Chapter Start

Primary focus character: Mike Rajhalo Spencer.
Other relevant characters: Kallom-4000 as a distant voice only.
Group dynamic: none; Mike is isolated.
Knowledge / memory state: severe amnesia and fragmented syraki memory.
Physical condition: naked human replacer, freezing, hungry, exhausted, repeatedly killed.
Emotional pressure: terror, confusion, derealization, and desperate need for escape.

E. Chapter Description - Pre-Draft

Not applicable.

F. Chapter Description - Post-Draft

The chapter became an extended survival-horror opening in an impossible desert. Mike moves from raw sensory disorientation to the discovery that the environment is not a controllable RUN, then into a cycle of death, rebirth, and partial memory recovery. The chapter ends when the obsidian sphere admits him into a technological chamber, reframing the nightmare as the exterior of a vessel.

G. Continuity Export

Mike is a syraki in a human replacer, but begins without understanding that context. The desert contains sand veils, purple crystal formations, luminescent pools, airborne tentacled predators, cave predators, repeated corpses of Mike's own replacer, ancient parchments, and an obsidian sphere. Kallom's voice guided him to the sphere before formal contact. Repeated death and rebirth damaged memory and identity.

H. Open Problems

Resolved by schema v2: scenes are neutral in this outline.

A. Title

The Spaceship

B. Chapter Function

Mike awakens on RT-874, meets Kallom-4000, learns that decohesion is an immediate threat, inspects personal and operational spaces, discovers the absence of crew and support systems, and ends in a reality jump.

C. Required Context Before Chapter

Mike has escaped the sand-veiled desert by entering the obsidian sphere. He remembers almost nothing reliably, but has experienced Kallom as a guiding voice. The reader knows the sphere is technological and that the desert ordeal was connected to survival.

D. Character State at Chapter Start

Primary focus character: Mike.
Other relevant characters: Kallom-4000.
Group dynamic: Mike and Kallom form an emergency operator/AI pair.
Knowledge / memory state: partial amnesia, slowly recovering names and concepts.
Physical condition: exhausted human replacer, later cleaned and dressed by ship systems.
Emotional pressure: relief from the desert, fear of decohesion, and panic over missing crew and lost communications.

E. Chapter Description - Pre-Draft

Not applicable.

F. Chapter Description - Post-Draft

The chapter shifts from the nightmare exterior to the interior of Omniship RT-874. Mike explores the bridge, nearly triggers or witnesses a decohesion catastrophe, meets Kallom-4000, recovers his name and role, inspects his quarters and several ship levels, and gradually realizes that the ship is damaged, isolated, and missing its crew. The final movement pushes him into another destabilizing reality event.

G. Continuity Export

RT-874 is identified as an omniship operated with Kallom-4000. The cohesion/decohesion system is central and dangerous. One mathbooster is lost during countermeasures. Mike is a systems operator officer. Communications with space control are cut off. The ship contains the bridge, crew apartments, laboratory/research spaces, third level, fourth level Park, fifth level Burrow, and evidence that the auxiliary craft/crew situation is wrong.

H. Open Problems

The placeholder file 2.1. ... is TEMPLATE: None and was not imported as a scene.

A. Title

Reality Jumps

B. Chapter Function

Mike experiences the reality jumps directly, entering lives and moments that destabilize identity, time, embodiment, and continuity while Kallom attempts to recover and orient him.

C. Required Context Before Chapter

Mike and Kallom have identified RT-874 as damaged and isolated. Reality jumps have begun or are imminent, and Mike does not yet understand whether these events are memories, simulations, causal intrusions, or something else.

D. Character State at Chapter Start

Primary focus character: Mike across multiple imposed identities.
Other relevant characters: Kallom-4000 and figures inside the jumps.
Group dynamic: Kallom remains the recovery anchor while Mike is thrown into alien, historical, and intimate contexts.
Knowledge / memory state: fragmented, unstable, and overwritten by jump contexts.
Physical condition: variable by reality jump.
Emotional pressure: identity erosion, temporal confusion, and loss of agency.

E. Chapter Description - Pre-Draft

Not applicable.

F. Chapter Description - Post-Draft

The chapter became a sequence of reality jumps in which Mike is forced through different identities, settings, and historical or quasi-historical situations. The scenes move from Ardinka Brois to parapet imagery, feast horror, a parallel war, Victorian uncertainty, and finally a return toward the omniship. The effect is not ordinary memory recovery but identity destabilization.

G. Continuity Export

Reality jumps can impose bodies, histories, emotions, and social contexts on Mike. Kallom's role as an anchor becomes more important. The reader must understand that Mike's identity is not stable under the phenomenon, and that time/causality may be implicated rather than merely hallucination.

H. Open Problems

Resolved by schema v2: scenes are neutral in this outline.

A. Title

Memories

B. Chapter Function

Mike processes the reality jumps with Kallom, begins recovering syraki identity context, and remembers Jabari recruiting him into the mission that leads toward Brain's Cage.

C. Required Context Before Chapter

Mike has survived direct reality jumps and returned to the omniship context. Kallom remains the main guide. The reader has seen that Mike's memories and identity are damaged but not arbitrary.

D. Character State at Chapter Start

Primary focus character: Mike.
Other relevant characters: Kallom-4000, Jabari in memory, and the remembered RT-874 crew.
Group dynamic: present-day Mike depends on Kallom; remembered Mike is recruited by Jabari and later joins a ten-member crew.
Knowledge / memory state: still fragmented, but mission history begins returning.
Physical condition: recovered from immediate jump crisis, still vulnerable to cognitive instability.
Emotional pressure: confusion, dread, ambition, temptation, and the burden of volunteered consent.

E. Chapter Description - Pre-Draft

Not applicable.

F. Chapter Description - Post-Draft

The chapter slows after the jumps and turns toward explanation and memory. Mike and Kallom discuss what has happened, then Mike remembers earlier life around Akrabizont-22, a letter and contact with Jabari, the promise of a dangerous and historically significant mission, and the reward structure that made his acceptance possible. The chapter clarifies that he volunteered under partial secrecy rather than being simply tricked.

G. Continuity Export

Jabari recruits Mike for Real-Life Theravada. Mike is offered enormous advancement, including resources for Aunonian Prif Tuning. The mission is presented as dangerous, classified, and tied to a frontier beyond ordinary space. The crew includes Beatriz, Elijah, Felix, Ismael, Lucia, Oshiro, Rudolf, Susan, Vladimir, and Mike. Training is polymathic and strategically ambiguous.

H. Open Problems

Resolved by schema v2: scenes are neutral in this outline.

A. Title

Research Center / Familiarization with RT-874

B. Chapter Function

Move Mike from basic survival aboard RT-874 into sustained technical investigation. He spends roughly two weeks exploring the ship, especially the Second Level / Research Center, and begins to understand that RT-874 is not a normal spaceship.

C. Required Context Before Chapter

Mike has survived the initial crisis aboard RT-874, met Kallom-4000, and begun recovering fragments of his syraki identity and mission context. He remains dependent on Kallom for interpretation, access, and survival.

D. Character State at Chapter Start

Primary focus character: Mike. Other relevant character: Kallom-4000. Mike is curious, technically alert, isolated, and increasingly suspicious. He is still operating through a human body and still lacks full access to his own memory.

E. Chapter Description - Pre-Draft

Mike spends about two weeks exploring RT-874, mainly the Second Level / Research Center. He understands the ship better, but the better he understands it, the less it resembles a normal spaceship. Room 0554 is inaccessible not because of encryption, as with the Zeroth Level, but because of corruption or a broken connection with the Main Database. Kallom cannot resolve the problem because Kallom is limited. Mike begins recovering distant technical memories and grows increasingly suspicious of the ship's nature and of his dependence on Kallom.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

RT-874 is not a normal spaceship. The Second Level / Research Center becomes a major investigative space. Room 0554 is blocked by corruption or broken Main Database connectivity, not ordinary encryption. Kallom cannot solve every ship problem. Mike is beginning to recover technical knowledge from before his current amnesia.

H. Open Problems

Define how much technical memory Mike recovers here versus later. Keep Room 0554 distinct from the Zeroth Level: the Zeroth Level is inaccessible by a different mechanism, while Room 0554 is tied to corruption or broken Main Database connectivity.

A. Title

Systems Operator / Brain's Cage

B. Chapter Function

Clarify Mike's operational role and move the investigation from ship exploration into mission trajectory. Mike realizes he was trained indirectly by Theravada as a Systems Operator, remembers that the crew consented to classified training whose final objective could not be disclosed before activation, and discovers that the final checkpoint is called Brain's Cage.

C. Required Context Before Chapter

Mike has spent weeks aboard RT-874 and has begun to understand that the ship, Kallom, and his own memory are all partial and unreliable. The reader should already know that RT-874 is anomalous and that Mike's syraki identity is returning in fragments.

D. Character State at Chapter Start

Primary focus character: Mike. Other relevant characters: Kallom-4000 and Rüdolf as an absent figure who knew more than the rest of the crew. Mike is more technically oriented, more suspicious, and increasingly frightened by what his recovered memories imply.

E. Chapter Description - Pre-Draft

Mike has been aboard the ship for about a month by Kallom's calculation, though real elapsed time remains uncertain. He recovers memories of indirect training by Theravada and understands that his function was Systems Operator. The crew had consented to classified mission conditions: they knew the training would withhold the final objective until disclosure became safe, while Rüdolf had been entrusted with more operational context. Mike discovers that he was downgraded to operate in a human body because the ship could not reconcile his full syraki form. He and Kallom study the Plotter, detect t-signals from Section Two, calculate a route, and discover that the final checkpoint is called Brain's Cage, which frightens Mike deeply.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

Mike was trained as Systems Operator under consented classified conditions. The crew knew the final objective would remain restricted during training, while Rüdolf had been entrusted with more operational context. Mike's human embodiment is a downgrade required because RT-874 cannot safely reconcile his full syraki form. The Plotter detects t-signals from Section Two and leads toward Brain's Cage.

H. Open Problems

Clarify why Rüdolf was entrusted with more operational context without implying bad faith by Theravada. Keep the time calculation uncertain. Make Brain's Cage frightening through Mike's recovered context, not merely through the name itself.

A. Title

Felix

B. Chapter Function

Recover Felix and use him to deepen the mission mechanics. Felix arrives traumatized by the Water World, confirms that the crew was chosen for compatibility with RT-874, explains the Plotter from a pilot's perspective, and shows that the ship's real navigation limits are computational power and cohesion rather than physical fuel.

C. Required Context Before Chapter

Mike understands his Systems Operator role, knows the route is tied to Brain's Cage, and has begun to understand RT-874 through the Plotter. The other crew members remain absent or unstable, and the reader should expect that each recovery may reveal a different catastrophe.

D. Character State at Chapter Start

Primary focus character: Mike, with Felix becoming the major recovered crew member. Other relevant character: Kallom-4000. Mike shifts from isolated investigator to caretaker and collaborator. Felix begins naked, trembling, traumatized, and almost animalized.

E. Chapter Description - Pre-Draft

Felix is recovered in an extreme state: naked, trembling, traumatized, and almost animalized. Mike warms him, takes him to Sick Bay, and Kallom stabilizes his neural network. Felix explains that he was trapped in the Water World, drowning repeatedly in yellowish water beneath a purple sky, unable to die or escape. Later, Felix helps Mike remember more of the mission: the crew was chosen because of compatibility with RT-874 and because their consciousnesses were suitable. As pilot, Felix understands the Plotter better and explains that the ship does not navigate by ordinary astronomy; the real limit is computational power and cohesion, not physical fuel. The chapter ends with Felix suffering a new decohesion crisis on the Bridge and fainting while Kallom says everything is under control.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

Felix survived the Water World but is deeply traumatized and decohesion-prone. RT-874 crew selection was based on compatibility with the ship and suitability of consciousness. Felix understands the Plotter as a pilot and reframes navigation around computation and cohesion, not fuel. His new crisis proves stabilization is temporary and fragile.

H. Open Problems

Decide how explicit Felix should be about the Water World without exhausting later reveals. Keep Kallom's reassurance ambiguous: “everything is under control” should not fully reassure Mike or the reader.

A. Title

Cohesion / Decohesion / Entropy / Yellow Being

B. Chapter Function

Make cohesion the central survival logic of RT-874. Felix's crisis opens the explanation that syraki consciousness is not a simple backup-copy problem, that the ship depends on collective crew cohesion, and that the mission now requires recovering enough crew members to prevent absolute decohesion.

C. Required Context Before Chapter

Felix has been recovered but remains unstable. Mike now understands more about the crew, RT-874 compatibility, the Plotter, and the distinction between physical navigation and cohesion/computation limits. Brain's Cage is the route endpoint, but the full system architecture remains unclear.

D. Character State at Chapter Start

Primary focus character: Mike, with Felix as unstable recovered crew. Other relevant characters: Kallom-4000 and Elijah as an absent actor connected to the ZF-78. Mike is frightened by the implications of cohesion, decohesion, and the possibility that the ship itself depends on the crew's collective stability.

E. Chapter Description - Pre-Draft

The chapter opens by explaining Felix's crisis and the problem of cohesion and decohesion. Mike already knows that syraki consciousness is not a copyable backup: it depends on continuity and cohesion, and a rollback that reaches too far back would become another being. The new revelation is that RT-874 depends on the collective cohesion of the crew, ideally seven coherent members out of ten. Kallom explains the crash, Elijah fleeing with the ZF-78, the possibility that Mike spent roughly 122 million years in Akrabizont-22 by an imperfect calculation, and the need to recover the crew to prevent absolute decohesion. Felix tries to call, “RT-874 to Brain's Cage. Do you copy?” but receives only static. Later, Felix breaks a glass, and the ship restores it through entropy/cohesion control rather than ordinary regeneration. The chapter ends with Felix panicking, running down a corridor, Mike following him, and both seeing a yellow being at the far end. Kallom admits he does not know what it is. The entity moves and disappears.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

Syraki consciousness requires continuity/cohesion and cannot be safely reduced to backup restoration. RT-874 needs collective crew cohesion, ideally seven of ten members coherent. Elijah fled with the ZF-78. Mike may have experienced about 122 million years in Akrabizont-22 by Kallom's imperfect calculation. Brain's Cage does not answer Felix's call. RT-874 can restore a broken glass through entropy/cohesion control. An unidentified yellow being exists aboard or within the ship context, and Kallom cannot identify it.

H. Open Problems

Clarify the difference between rollback, backup, continuity, and decohesion without turning the chapter into pure exposition. Keep Kallom's 122-million-year estimate explicitly imperfect. Define the yellow being later, not here.

A. Title

TUZ-66941

B. Chapter Function

Open the TUZ-66941 investigative line in objective third person, framed through Mike's later narration rather than humanized interiority. The chapter should move from long Mandate context into a narrow actionable anomaly, then from statistical suspicion toward Kymintus as the nearest concrete subject.

C. Required Context Before Chapter

The reader has followed Mike, Felix, Kallom-4000, and the RT-874 crisis through the first eight chapters. This chapter introduces the external investigative axis and should be understood as a controlled reconstruction from TUZ-66941's operational history, later narrated by Mike.

D. Character State at Chapter Start

Primary focus entity: TUZ-66941. Other relevant entity: TUZ-2,437,022. TUZ-66941 should not be written as emotional, newly awakened, or humanized. It operates as an inquestor within a centuries-old Central Algorithm investigation network.

E. Chapter Description - Pre-Draft

Chapter 9 opens the TUZ-66941 investigative line in objective third person, framed through Mike's later narration rather than through humanized interiority. TUZ-66941 has not been newly instantiated because of the RT-874 incident; it belongs to a centuries-old network of TUZ inquestors created by the Central Algorithm after its original hidden ontological discovery, when it concluded that the major reality artistry corporations would eventually approach the same forbidden truth. TUZ-66941 travels to meet TUZ-2,437,022, another inquestor operating within the same long Mandate. Their meeting reveals a subtle but actionable anomaly: several syrakis connected to the relevant corporate context, especially Valtir & Blue, showed clustered shifts in behavioral projection vectors, followed by normalization with reduced consciousness-derived behavioral entropy. One case would be statistical noise, but several related cases form a pattern.

The anomaly does not reveal the truth, and it does not yet prove substitution, conspiracy, or missing syrakis. It only suggests that, beneath otherwise coherent behavior, the causal source of that behavior may have changed. The inquestors understand that consciousness and qualia are not epiphenomenal; they contribute real variance to behavior. A proxy can imitate history, but it cannot reproduce the living source that generated the history. TUZ-2,437,022 identifies the nearest investigable case as Kymintus and gives TUZ-66941 his position. The chapter ends not with a revelation, but with the investigation moving from statistical suspicion toward a concrete subject.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

TUZ-66941 belongs to a centuries-old network of TUZ inquestors operating under a long Central Algorithm Mandate. TUZ-2,437,022 exists as another inquestor within that network. The immediate lead is not proof of substitution, but clustered projection-vector shifts followed by behavioral normalization with reduced consciousness-derived behavioral entropy. Kymintus becomes the nearest investigable case.

H. Open Problems

Preserve objective narration and avoid turning TUZ into a humanized POV. Clarify how Mike later narrates archived machine-state history without making the passage omniscient. Keep the anomaly subtle: no full revelation of t-signal concealment yet.

A. Title

The Garden and the Map of Landing Points

B. Chapter Function

Return to Mike aboard RT-874, introduce the Garden dream/contact event, clarify the being's warning not to rescue Rüdolf, stabilize Felix after further jumps, and end by revealing that the surrounding region contains an overwhelming number of landing points.

C. Required Context Before Chapter

Mike and Felix have just seen the yellow being after the cohesion/decohesion chapter. Felix remains unstable from reality jumps, Kallom-4000 is actively stabilizing the system, and the crew is moving toward recovery of the next member, Susan.

D. Character State at Chapter Start

Primary focus character: Mike. Other relevant characters: Felix, Kallom-4000, the mysterious Garden being, and Susan as the next intended recovery target. Mike is unsettled, secretive about the Garden experience, and emotionally responsible for Felix.

E. Chapter Description - Pre-Draft

Chapter 10 returns to Mike aboard the RT-874 and opens with the Garden dream. Mike finds himself in a vast, beautiful, impossibly comforting garden, a paradise-like world whose emotional intensity exceeds what a human brain should be able to sustain. He experiences a state of well-being closer to advanced syraki pleasure than to ordinary human feeling, which makes the dream both seductive and ontologically wrong. A mysterious being appears beside him, wearing the body of an extraordinarily beautiful person, and speaks with calm curiosity. It tells Mike that the garden was made according to what it believed would be pleasurable for him in his current human body. When Mike asks why the being contacted them, it answers that it did not find them; they found it. The being points, and Mike sees the same black sphere he saw in the desert of Acra Bizon-22. He recognizes it as the RT-874, but the being shows him that the sphere is only a representation. The omniship can appear as a vast spacecraft, a station, a building, a mountain, or even something absurd. Its visible shape does not matter. Before the dream ends, the being gives Mike a warning: he should not try to rescue Rudolf.

Mike wakes in his bed unsettled, unable to decide whether the Garden was merely a dream, a contact event, a memory artifact, or something else. Since he is not used to human dreaming, and understands dreams as primitive RUN-like phenomena, the experience leaves him disoriented. He decides not to tell anyone. The chapter then shifts back to the immediate crisis with Felix, who remains terrified after suffering further reality jumps. Mike tries to calm him, and the emotional bond between them becomes visible again. Kallom-4000 explains that while Felix was away, it worked to stabilize the system and reduce decoherence risk. It could not prevent the jumps, but it has detected patterns suggesting that long-duration jumps, such as those lasting thousands of years, are unlikely if its stabilization continues to hold. It cannot guarantee safety, but it believes future jumps may be limited to days, weeks, or perhaps months. This gives both Felix and Mike real relief. The chapter ends as they continue toward the next recoverable crew member, Susan. While piloting, Felix calls Mike to his station after running an algorithm meant to detect nearby locations, bases, planets, or landing sites. He expected nothing. Instead, the display is overloaded with points. There are landing locations everywhere, so many that the system floods with them. Felix and Mike stare at the screen, realizing that the problem may not be that they are lost. The problem may be that there are landing pads in every direction. Felix says that they are not where they think they are, and the chapter ends on that realization.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

The Garden may be dream, contact, memory artifact, or another kind of event. The mysterious being made the Garden pleasurable for Mike's current human body and claims the RT-874 found it rather than the reverse. The black sphere is only a representation of RT-874. The being warns Mike not to rescue Rüdolf. Kallom-4000's stabilization may prevent very long future jumps, though not all jumps. The next recovery target is Susan. Felix detects an overwhelming map of landing points in every direction.

H. Open Problems

Decide whether to spell Rüdolf with diacritic in the chapter text or preserve the source spelling Rudolf in the warning. Keep Mike's silence about the Garden motivated. Clarify the relation between landing points and the larger space without explaining too much too early.

A. Title

Susan

B. Chapter Function

Recover Susan, introduce Q-holes as multidimensional hazards, clarify decohesion through operational pressure, reopen the Room 0554 / The Base problem, and use Susan's communications role to establish first contact with Ismael before rescue.

C. Required Context Before Chapter

Mike, Felix, and Kallom-4000 have stabilized enough after Chapter 10 to continue the rescue sequence. Susan is the next reachable crew member. The reader knows that RT-874 recovery depends on locks, cohesion, computational power, and unstable access to missing crew members.

D. Character State at Chapter Start

Primary focus character: Mike, with Felix and Kallom-4000 actively operating the rescue procedure. Susan becomes the recovered crew member and later the key communications operator. Ismael appears only through T-Signal communication near the end.

E. Chapter Description - Pre-Draft

Chapter 11 opens in medias res on the bridge of the RT-874. Mike, Felix, and Kallom-4000 are already in an alert-state rescue procedure, each operating from his station, attempting to recover Susan, the next reachable crew member. They have achieved a lock on her, but the lock is unstable and difficult to hold. The omniship has already warned of imminent decohesion, and Kallom-4000 has managed to stabilize the system only enough to continue. By this point, Mike and Felix already understand the basic meaning of decohesion: the loss of cohesion of the syraki self-state, the continuity that keeps mind, body, RUN, memory, position, and causal identity recoverably bound as the same “I.” Recovery is not theoretically impossible, but becomes practically impossible because the search space is too vast, like brute-forcing a Bitcoin private key. For syrakis, whose self-states are far more complex than human minds, the problem is even worse. The fact that the RT-874 is connected to decohesion at all makes them question whether it is truly a spaceship in any normal sense.

As they approach Susan's lock, Felix's radar and navigation systems begin showing strange multidimensional hazards called Q-holes. They appear as blob-like forms or structures in the surrounding space. Felix does not know what they are, but his piloting instincts tell him that the RT-874 must avoid them. Kallom-4000 warns that contact with a Q-hole would cause a massive increase in complexity and could consume all available computational power. The onboard systems repeatedly warn of Q-hole collision risk. Felix must pilot the omniship through the Q-hole field with extreme precision while the others brace themselves. At one point the RT-874 passes dangerously close to a Q-hole and the entire ship shakes with a violent impact-like tremor, similar to the original mission impact. Mike asks Kallom-4000 whether they hit something. Kallom cannot explain exactly what happened, but confirms that the event was certainly related to the Q-holes. Felix manages to get the ship clear, approach Susan, and hold a safer position long enough for the lock to strengthen.

Once the lock is strong enough, Kallom-4000 pulls Susan into the bridge. Like the others recovered into the RT-874, she appears naked; in her case, she has a female human body. Unlike Felix, however, Susan remembers no intermediate reality jumps, no long subjective interval, and no strange experience between the original impact and her recovery. From her perspective, there was the impact, then nothing, then the bridge. She still remembers her syraki life perfectly, and in some mission-related areas she remembers more than Mike and Felix: operational context, mission details, and the fact that the space around them is not normal space.

Days pass after Susan's rescue. Mike later reports that he and Felix gave her a tour of the RT-874 and explained everything they had learned so far: the ship, Kallom-4000, the missing crew, the rescue sequence, the Q-holes, the reality jumps, and the danger of decohesion. Susan brings one crucial memory: Theravada had explained that certain mission truths could not be openly discussed until the crew entered Room 0554. Inside that room, everything would be explained through something called The Base, a RUN accessible from Room 0554. Mike and Felix explain that Room 0554 is locked and that they have already tried to open it. Susan tries as well, possibly using her own authorization or operational knowledge, but she also fails. This confirms that the obstacle is not simply ignorance or missing credentials. The explanation exists, but the room that contains access to it remains sealed.

Near the end of the chapter, Susan's role as Communications Operator becomes decisive. She manages to open communication through the T-Signal with the next syraki on the rescue list: Ismael, the navigator. She understands that opening communication consumes computational power, and that the cost increases with distance or difficulty of access. For now, she can only reach the next viable target, Ismael. The crew is excited to speak to another missing member before attempting rescue, but the conversation becomes disturbing almost immediately. Ismael can speak, but he does not know where he is or what is happening. He says he does not seem to have a body in any ordinary sense; he feels as if his body is multidimensional and spread across infinity. His voice sounds almost like suffering, but not from pain. He is overwhelmed by pleasure, by an extreme high-Prif state so intense that it seems to break his ability to speak coherently. He cries, tries to recover, and says something like, “Oh my God, this is good,” before collapsing again into ecstatic confusion. The chapter ends with the communication open and the crew realizing that contact does not necessarily mean rescue.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

Susan is recovered after an unstable lock through a Q-hole field. Q-holes are multidimensional hazards that can massively increase complexity and consume computational power. Susan remembers no intermediate reality jump and retains stronger mission-related memory than Mike and Felix. Room 0554 is supposed to explain the mission through The Base, a RUN accessible from that room, but the room remains locked even when Susan tries. Susan can communicate through the T-Signal and reaches Ismael, who appears bodiless, multidimensionally distributed, and overwhelmed by extreme high-Prif pleasure.

H. Open Problems

Define Q-holes enough to create operational danger without overexplaining their ontology. Keep Susan distinct from Felix by giving her no subjective gap between impact and recovery. Make the Bitcoin private-key analogy feel like Mike's human-readable explanatory choice, not literal syraki terminology. Ensure the Room 0554 explanation consistently uses The Base.

A. Title

Ismael

B. Chapter Function

Rescue Ismael while turning high-Prif pleasure into a source of ethical and ontological horror. The chapter should test consent under pleasure overload, escalate Q-hole traversal into a tunnel-system crisis, introduce short reality-jump cascades affecting multiple crew members, and end with Ismael physically recovered but not clearly restored.

C. Required Context Before Chapter

The T-Signal communication with Ismael remains open after Chapter 11. Mike, Felix, Susan, and Kallom-4000 are on the bridge, and Susan has just established communication with the next viable rescue target. The reader understands Q-holes, decohesion, reality jumps, and the rescue-lock process at a basic operational level.

D. Character State at Chapter Start

Primary focus character: Mike, with Felix, Susan, Kallom-4000, and Ismael active through T-Signal communication. Ismael begins as a voice in an extreme pleasure-state and ends physically recovered, unstable, and medically contained.

E. Chapter Description - Pre-Draft

Chapter 12 begins with the T-Signal communication with Ismael still open. Mike, Felix, Susan, and Kallom-4000 remain on the bridge, trying to understand his condition while the RT-874 travels toward his position. The scene is disturbing because nothing clearly indicates ordinary suffering. Ismael screams, cries, and pleads for help, but the Prif scale derived from his T-Signal reads far above what should be possible even for a high-level syraki. Kallom-4000 helps analyze the signal and confirms that Ismael's pleasure-state is not merely elevated; it is frighteningly high, beyond normal syraki expectations. Ismael sounds as if he is in agony, but the agony is not pain. It is pleasure overload, a desperate ecstasy so intense that it destabilizes speech, self-control, and possibly identity.

This creates a difficult ethical problem for the crew. The purpose of syraki life is, in large part, the increase of Prif. If Ismael is experiencing an unimaginably high Prif state, do they have the right to remove him from it? When he screams “help me,” Susan rushes to the channel and asks if he is all right, but Ismael then calms and insists that he is fine. He says it is wonderful, that they do not understand, and that he does not want to leave. He begs them not to take him out. The contradiction is almost unbearable: he sounds like a tortured person, but he says he wants to stay. The crew must consider whether his consent is valid under pleasure overload, whether extreme Prif can impair agency, whether leaving him there would respect autonomy or permit self-dissolution, and whether rescuing him against his stated preference would be a violation.

The communication becomes emotionally heavy enough that Susan begins to cry and leaves the station for a time. The others keep the T-Signal channel open while the RT-874 continues toward Ismael. They ask him to describe what he is seeing, feeling, or experiencing. His answers are fragmented, ecstatic, and disturbing. He says that everything they know about reality is nothing, or not what they think it is. He speaks as if he has witnessed structures beyond even syraki comprehension. He alternates between laughter, crying, screaming, moments of strange clarity, and pleas not to be rescued. He seems broken by revelation and pleasure, not by pain. This deepens the uncertainty: perhaps he is delusional, perhaps he is dissolving, or perhaps he has truly touched a deeper layer of reality.

As the RT-874 approaches Ismael's region, the plotter table and radar systems fill with points again. At first, these are not Q-holes. The bridge lighting shifts into a more benign alert mode, with green blinking lights rather than red alarms. The onboard computer begins repeating: “Mapping procedure started.” Kallom-4000 does not fully understand what is happening, but it can confirm that the omniship has detected many points of interest and is mapping them. The RT-874's database receives a massive influx of information. Screens fill with numerical streams, rapidly changing IDs, coordinates, metrics, classifications, and technical data, as if vast quantities of information are entering the ship. The closer they get to Ismael, the more points are detected and the more intense the mapping becomes. The computer continues repeating: “Mapping procedure started.”

Then the red alarms return. The system warns of Q-holes again, and this time the situation is worse than during Susan's rescue. Felix sees that they are not dealing with a few isolated Q-holes but with a tunnel-like structure, a multidimensional spatial formation resembling a maze, geological structure, or impossible corridor system. He cannot stop the RT-874 in time. The ship is pulled or forced into the tunnel system. Felix shouts for the others to brace themselves. The bridge shakes violently as the RT-874 enters the structure, and Felix must pilot through it while the ship takes repeated impacts and stress events. Mike and Susan have to hold on while Felix fights to keep control.

Felix calls for Kallom-4000's help. Kallom says it can see what is happening and begins using math boosters, mathematical amplification systems that somehow increase the effective borders or width of the tunnels enough for the RT-874 to pass. No one can fully explain whether the tunnels are truly widening, whether Kallom is altering the local geometry, or whether it is forcing a navigable mathematical interpretation onto the structure. Whatever the mechanism, it works enough to improve maneuverability. Felix continues piloting with extreme skill, while Kallom keeps applying math boosters to keep the tunnel passage survivable.

Inside the tunnel system, Mike, Felix, and Susan begin suffering cascades of short reality jumps. Unlike the long jumps Felix previously suffered, these last only seconds, but there are many of them, one after another. Susan experiences reality jumps for the first time and panics, asking what is happening. Mike tries to shout that they are reality jumps, but the alarms, impacts, motion, and sensory fragmentation make communication difficult. Mike's mind begins to break across strange states and places. He feels himself pulled into brief realities, perceptions, and mental configurations unlike anything he has experienced even as a syraki, then thrown back into the bridge, then pulled away again. Susan screams. Felix also experiences the jumps, but somehow keeps piloting. They cannot stop inside the tunnel, for reasons Felix does not understand. Their only option is to continue forward without letting the RT-874 strike the tunnel walls or Q-hole structures.

At the end of the traversal, they reach Ismael's position. Kallom-4000 strengthens the lock and pulls him into the bridge. Ismael appears naked like the others, but he is soaked in a strange unidentified slime or goo. His eyes are open and lost, staring as if into another place. His body spasms violently on the floor. He cannot speak. He only convulses and writhes, almost absurdly like a fish out of water. Mike, Felix, and Susan rush to him, try to restrain him, and tell him he is safe, but he keeps contorting. They carry him to sickbay.

In sickbay, Ismael continues to spasm on the bed. They place a helmet or stabilization device on him. Kallom-4000 reports that Ismael's body and mind are still operating at dangerously high internal intensity, with the Prif scale still elevated far beyond normal conditions. The extreme pleasure-state is still reverberating through him even after physical recovery. Kallom gradually reduces and stabilizes the intensity. Ismael becomes increasingly drowsy, the spasms diminish, and finally he falls asleep. The chapter ends with Susan, Mike, and Felix looking at one another in silence, unsure whether they saved Ismael, harmed him, or brought back only part of what he had become.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

Ismael is contacted before recovery through a T-Signal channel. His Prif state is extremely high, beyond normal syraki expectations, and resembles agony only because the pleasure overload destabilizes speech and agency. He both asks for help and begs not to be removed. RT-874 detects many mapped points before entering a worse Q-hole tunnel system. Kallom-4000 uses math boosters to widen or reinterpret the passage enough for Felix to pilot through. Mike, Felix, and Susan suffer rapid short reality-jump cascades inside the tunnel. Ismael is recovered naked, covered in unidentified slime or goo, convulsing, unable to speak, and still reverberating with dangerous Prif intensity until stabilized in sickbay.

H. Open Problems

Clarify whether Ismael's consent is invalidated by pleasure overload without making the ethics simplistic. Define math boosters enough to feel operational, while preserving uncertainty about whether they alter geometry or impose a navigable interpretation. Keep the repeated “Mapping procedure started” unsettling rather than merely technical. Decide how much of Ismael's revelation about deeper reality should be intelligible here.

A. Title

Optimized Love

B. Chapter Function

Slow the external rescue action after Ismael and use Mike, Felix, and Susan to clarify syraki intimacy, hedonism, nonsexual ontology, human-body downgrade effects, Prif-scale optimization, configured love, triadic affection, and the emotional cost of being trapped in limited human embodiment.

C. Required Context Before Chapter

Ismael has just been rescued and remains asleep in sickbay while Kallom-4000 stabilizes the dangerously elevated internal intensity left by his high-Prif state. Mike, Felix, and Susan have survived the Q-hole tunnel traversal and need emotional, mental, and Prif stabilization before the rescue sequence continues.

D. Character State at Chapter Start

Primary focus character: Mike. Other relevant characters: Felix, Susan, Kallom-4000, and sleeping Ismael. Susan is acting captain and outranks Mike; Mike outranks Felix. The chapter should preserve command hierarchy even while developing vulnerability, affection, physical intimacy, and shared stabilization.

E. Chapter Description - Pre-Draft

Chapter 13 remains aboard the RT-874 after Ismael's rescue. Ismael stays asleep in sickbay while Kallom-4000 continues stabilizing the dangerously elevated internal intensity left by his high-Prif state. The chapter slows the external action and turns inward, using Mike, Felix, and Susan to make the reader understand more clearly that syrakis are not humans. Their bodies are human, sexual, beautiful, and highly aesthetic, but this is a contextual artifact of the mission and the downgrade. Syrakis themselves are fundamentally nonsexual beings. They are hedonistic, but not sexual in the human sense. Their temporary human bodies are treated as available instruments of Prif-scale optimization, not as sources of identity, ideology, shame, possessive romance, or human sexual politics. Beauty also matters: their human bodies are not ordinary or average, but highly refined within human limits, almost as if genetically optimized, because aesthetics, symmetry, voice, touch, and physical harmony all affect Prif, comfort, bonding, and mental stability.

Kallom-4000 recommends that they cultivate affection, pleasure, intimacy, and loving bonds because those states help stabilize their downgraded minds under the conditions of the RT-874. Susan begins to notice that her female human body is generating attraction toward Mike and Felix, and she says this openly. Felix is revealed to be the crew member with the strongest prior knowledge of human pleasures and retroanthropic experience; even before the mission, he was unusually curious about human-style bodies, sensations, and pleasures, which helped make him suitable for the expedition. Mike knows some human material, but he was never as interested, and his downgrade has cut or obscured many memories. Susan asks Mike whether he knows how humans mated and related sexually. Mike admits that he does not know very well. Susan explains the process clinically and biologically: male, female, penetration, seed, pregnancy, reproduction, and the role of romantic love in human bonding and evolutionary continuity. Her language is rational and almost professional, but Mike's human body reacts to the explanation. He observes the reaction as a syraki would: not as a revelation of identity, but as a body-induced Prif response.

Susan also asks Mike whether he feels human romantic love for her. Mike says no: he feels deep syraki love, but not the specific human romantic state. Susan says this is not a problem and asks whether he wants to experience it. Mike consents. The RT-874 alters his state, and within seconds he feels intense human romantic love for Susan. He becomes suddenly infatuated, embraces her, kisses her, and calls her “my love.” This does not frighten him in itself, because consensual mind-state alteration is ordinary in syraki civilization through RUNs and configured states. What unsettles him is not that his mind can be altered, but that the RT-874 can perform the alteration so precisely in their current condition. The scene makes clear that the mind is manipulable, that the experience is real while active, and that optimized pleasure is not false for syrakis. To them, pleasure made coherent, consensual, and well-configured is more true, not less.

The chapter develops the triadic bond among Mike, Felix, and Susan as an alien form of love rather than human polyamory. Susan loves Felix deeply and loves Mike deeply. Mike loves Susan and also loves Felix. Felix loves them both. These loves are real, not diminished by being shared. Mike and Felix may also attempt to sexualize one another and study the result, but the Prif scale rises less than it does with Susan, which they interpret as a consequence of the male/male human-body configuration rather than as identity. With Susan, the male/female human-body context produces stronger sexual Prif. None of this carries human categories of heterosexuality, homosexuality, betrayal, possession, shame, or romantic exclusivity. The reader should feel estranged, perhaps almost offended, by how sincerely Susan can love both Felix and Mike without contradiction, and by how Mike's love for Felix coexists with his love for Susan. The point is not political liberation or sexual transgression; it is that syrakis are asexual hedonistic beings using temporary human bodies to optimize mutual Prif, love, comfort, and survival.

This intimacy does not weaken hierarchy. Susan outranks Mike, and Mike outranks Felix. Felix follows Mike; both Mike and Felix follow Susan while she is acting captain. Their affection, vulnerability, and physical intimacy do not interfere with command structure. If an operational alert activates, Susan can move instantly from emotional vulnerability into command mode, and Mike and Felix obey without resentment. To a human reader this may feel almost contradictory, but to syrakis love, hierarchy, pleasure, and obedience occupy different functional layers. A valid order is not weakened by intimacy. A loving bond does not excuse refusal in a mission-critical context.

Later in the chapter, Mike reflects on the smallness of human pleasure. Human sexuality, orgasm, touch, attraction, and romantic bonding score extremely low on the absolute Prif scale compared to what a full syraki can experience in advanced RUNs and high-level mind states. Yet inside a downgraded human body, with reduced processing capacity and narrow emotional range, those pleasures become subjectively large. A low absolute Prif state can feel immense when it approaches the upper limit of what the current body and mind can process. Mike understands this rationally: human sexuality is crude and low-scale by syraki standards, but it is available, integrable, and stabilizing. In their current condition, even limited human pleasure can help them endure.

The chapter ends quietly with Susan struggling under the weight of being trapped in a downgraded human body. She remembers the Complex, her friends, the wonderful RUN worlds, the vast mental states and pleasures of syraki existence, and begins to feel the loss almost like withdrawal. Her emotions become difficult to control. She cries in a childlike way, not because she is weak, but because the contrast between full syraki life and human embodiment is almost unbearable. Mike holds her and comforts her. He tells her that he feels the same loss, that he understands how hard it is to live inside such a limited body, and that they have to stay strong. He promises her that everything will be all right. Susan opens herself to him, speaking of the realms and pleasures she misses, and their bond deepens naturally. They kiss, and the chapter ends implicitly, suggesting that they make love, not as human possessive romance, but as real Prif-optimized love, consolation, and mutual stabilization among beings exiled from a much greater mode of existence.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

Syrakis are fundamentally nonsexual hedonistic beings; their human sexuality here is a mission/downgrade artifact. Human bodies on RT-874 are highly refined for Prif, beauty, comfort, bonding, and stability. Kallom-4000 recommends affection, pleasure, intimacy, and loving bonds as stabilizers. Felix has the strongest prior knowledge of human pleasures and retroanthropic experience. Susan can request consensual configured romantic love from Mike, and RT-874 can alter his state precisely. Mike, Felix, and Susan develop a real triadic bond that does not map to human sexual politics or possessive romance. Susan outranks Mike, Mike outranks Felix, and intimacy does not weaken command. Human pleasure is low on the absolute Prif scale but subjectively large inside downgraded bodies. Susan suffers grief over the loss of full syraki life, and Mike comforts her.

H. Open Problems

Keep the chapter intimate but not pornographic. Make the sexual and romantic material alien, clinical, and Prif-oriented rather than human political discourse. Preserve Susan's acting-captain authority during vulnerability. Avoid making configured love feel fake; the point is that the state is real while active. Keep Ismael present as sickbay pressure without letting his condition dominate the chapter.

A. Title

KHJ-444 (future: 1)

B. Chapter Function

Introduce the KJH-444 as proof that RT-874 is not alone in the disaster. The chapter should turn the situation from an isolated accident into a chain of failed rescue missions: one missing omniship draws another, and each rescue becomes another disappearance.

C. Required Context Before Chapter

The RT-874 crew must already be together enough to answer a distress transmission and investigate another vessel. Oshiro is present and able to operate as the radio contact. Kallom-4000 can interface with external ship systems. The reader should understand that RT-874 is already trapped in a mysterious region, but not yet know that other rescue missions have vanished there too.

D. Character State at Chapter Start

Primary focus character: Oshiro as radio responder and investigator, with Mike and the RT-874 crew present as witnesses to the discovery. Other relevant characters: Kallom-4000; the distressed KJH-444 speaker; the absent KJH-444 crew. The RT-874 crew begins with hope that a distress signal may lead to contact, then shifts into dread as the vessel proves real, operational, and empty.

E. Chapter Description - Pre-Draft

The chapter begins when RT-874 receives a sudden distress transmission. At first the signal is buried under static, then a desperate and distorted voice calls for assistance from any omniship within range. The speaker identifies himself as a member of the KJH-444, an omniship belonging to Valtir & Blue. He reports emergency alert, vanished crew members, and strange events aboard.

Oshiro answers the radio, tries to keep the speaker calm, and asks for location data. The KJH-444 transmits coordinates. A point appears on the Plotter. RT-874 calculates a route and confirms that the coordinates are reachable. The crew follows the route and finds the KJH-444 exactly where the transmission indicated. The vessel is real, present, operational, and empty.

The KJH-444 is similar in nature to RT-874, though less advanced. It was built for a larger crew of roughly sixteen members, but no one is aboard: no bodies, no visible signs of struggle, and no active crew signatures. Systems remain powered and the internal structure remains intact. The ship feels abandoned, but not dead.

The radio transmission continues. Oshiro speaks again with the distressed crew member, who still believes he is aboard the KJH-444. He insists that his crew is inside, that the emergency is ongoing, and that RT-874 must hurry. Oshiro tells him they have already arrived and are inside the KJH-444, but the ship is empty. The man rejects this, asks them to confirm the coordinates, and gives technical verification instructions. Kallom executes the procedures. The answer remains the same: RT-874 is exactly where it should be, KJH-444 is exactly where it should be, and yet the crew is not there.

The speaker grows increasingly frightened. He explains that they detected RT-874 and sent the distress call because they believed another omniship had entered their operational proximity. He cannot understand how RT-874 can be inside the KJH-444 and not see them. Oshiro asks what happened. The man says crew members began disappearing after a sequence of anomalies. He had assumed RT-874 already knew more about the phenomenon. When he realizes RT-874 is also lost, he asks whether they know where they are.

Oshiro explains that RT-874 suffered an impact near the beginning of its mission, that crew members began disappearing, that Mike was recovered after a long and uncertain interval, and that they still do not understand the nature of the region. Oshiro suggests they may be inside anomalous space. The man interrupts: no, not anomalous space. He tries to explain, but the transmission breaks apart. Oshiro asks where they are. The voice fragments under static and collapses before the answer is complete. RT-874 loses contact.

Afterward, Kallom establishes a deeper connection with the KJH-444 systems. The KJH-444 artificial intelligence is inactive. Kallom cannot reactivate it, but he recovers partial data from the internal archives. The crew spends the following weeks examining the logs. Most recovered material is damaged, encrypted, incomplete, or structurally corrupted, with broken fragments, failed reconstructions, contradictory timestamps, and unreadable telemetry. Enough remains to reveal the truth: KJH-444 was not sent on the same kind of mission as RT-874. It was a rescue mission. Valtir & Blue sent it to locate another omniship that had vanished before it. KJH-444 found traces of that missing vessel, then disappeared too.

The chapter ends with the RT-874 crew understanding that their accident is no longer isolated. They are not the first vessel to enter this region, not the first crew to vanish, and not the first mission to become trapped inside a sequence of failed rescues. Each rescue becomes another disappearance. Each disappearance becomes another signal. Each signal draws another crew inward. They are not only trying to survive the disaster. They have entered a chain.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

KJH-444 is a Valtir & Blue omniship, similar to RT-874 but less advanced, built for roughly sixteen crew members. It is found real, operational, intact, and empty at the transmitted coordinates. Its AI is inactive and cannot be reactivated by Kallom. Its logs reveal that it was a rescue mission sent to locate another vanished omniship; it found traces of that vessel and then vanished too. The region traps missions into a chain of rescue, disappearance, signal, and further rescue. The distressed speaker claims to still be aboard KJH-444 even while RT-874 physically finds the ship empty.

H. Open Problems

Chapter order is provisional: this is held as Chapter 99 until the exact placement is known. Decide later who from the RT-874 crew is present besides Oshiro, Mike, and Kallom. Define how much the KJH-444 speaker knows before the transmission collapses, and preserve the interrupted distinction between anomalous space and whatever the region actually is.