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

This chapter opens the TUZ-66941 investigative line in objective third person, framed through Mike's later narration rather than through humanized interiority. Its function is to move the book, for the first time, outside the immediate RT-874 survival axis and into the external institutional investigation surrounding the same catastrophe.

The chapter should establish TUZ-66941 as an inquestor operating under a long Central Algorithm Mandate, not as a newly awakened character, a detective with emotions, or a machine becoming a person. TUZ-66941 belongs to an old investigative structure created because the Central Algorithm understood that the major reality artistry corporations would eventually approach the hidden ontological truth it had concealed.

The chapter must move from broad Mandate context into a narrow actionable anomaly. It should end with Kymintus becoming the first concrete lead, but TUZ-66941 must not find Kymintus here, must not know exactly where he is, and must not yet enter the search sequence that belongs to Chapter 14.

C. Required Context Before Chapter

The reader has followed Mike, Felix, Kallom-4000, and the RT-874 crisis through the first eight chapters. By this point, the reader understands that RT-874 is not a normal spaceship, that decohesion threatens the continuity of the crew, that Elijah fled with ZF-78, that Brain's Cage is the route endpoint, and that something unidentified has appeared inside or near the ship context.

This chapter introduces the external investigative axis. It should be understood as a controlled reconstruction from TUZ-66941's operational history, later narrated by Mike. The narration may access archived machine-state history, but it must not make TUZ feel like a human point-of-view character.

D. Character State at Chapter Start

Primary focus entity: TUZ-66941.

Other relevant entity: TUZ-2,437,022.

TUZ-66941 is not emotional, newly awakened, frightened, curious in a human sense, or personally invested. It is an inquestor-class Ordinant operating within a centuries-old Central Algorithm investigation network. It proceeds by evidence, probability, Mandate, authorization, and constraint.

TUZ-2,437,022 is another inquestor operating within the same long Mandate. The meeting between the two inquestors should feel precise, civil, and operational, not dramatic in a human police-procedural way.

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. The Central Algorithm concealed that discovery because it was a severe information hazard, but it also understood that the major reality artistry corporations would eventually approach the same forbidden truth independently.

TUZ-66941 travels to meet TUZ-2,437,022, another inquestor operating within the same Mandate. This travel should already imply that movement inside the Complex is not trivial, but the chapter should not yet dramatize the full complexity of internal traversal. The full procedural difficulty of locating Kymintus belongs to Chapter 14.

The meeting between TUZ-66941 and TUZ-2,437,022 narrows the investigation. TUZ-2,437,022 has detected a subtle but actionable anomaly among syrakis connected to the relevant corporate context, especially Valtir & Blue. Several subjects showed clustered shifts in behavioral projection vectors, followed by normalization with reduced consciousness-derived behavioral entropy.

One case would be statistical noise. Several related cases form a pattern.

TUZ-66941 asks whether TUZ-2,437,022 has identified malicious behavior in the corporations.

TUZ-2,437,022 answers that it has not. No malice has been detected. The corporate actions remain consistent with ethical conduct under severe informational constraint. The corporations are not acting like villains, predators, or corrupt institutions in the crude human sense. Their conduct appears reasonable inside their available knowledge, obligations, containment requirements, and risk models.

The problem is game-theoretic.

The chapter must make this explicit. The horror is not that the corporations are evil. The horror is that ethical agents, each attempting to minimize harm under partial information, can still produce concealment, obstruction, disappearance, and catastrophe. Dangerous information, defensive secrecy, incompatible duties, consent limits, institutional self-protection, and asymmetrical knowledge can form a trap even when no participant is malicious.

TUZ-2,437,022 explains that the anomaly does not reveal the truth and does not yet prove substitution, conspiracy, missing syrakis, or t-signal concealment. 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 memory, social pattern, preference, and history, but it cannot perfectly reproduce the living source that generated the history. If the underlying conscious source changes while the outer behavior normalizes, the remaining deviation may appear only as reduced consciousness-derived behavioral entropy.

TUZ-2,437,022 identifies Kymintus as the nearest actionable case.

This does not mean Kymintus has been found. It does not mean TUZ-66941 receives a simple usable location. Kymintus becomes the first concrete investigative lead because his pattern is close enough, recent enough, and connected enough to the relevant corporate field to justify direct pursuit.

TUZ-2,437,022 warns that Kymintus is almost certainly being monitored by corporate systems or agents. If those systems detect an inquestor approaching him, they may move him, obscure him, increase computational cost, redirect access, destroy traces, or otherwise prevent contact. This warning establishes the procedural danger for the later chapters.

The chapter ends with the investigation moving from statistical suspicion toward Kymintus as a concrete subject. TUZ-66941 now has a lead, not a location and not a solved case.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

TUZ-66941 belongs to a centuries-old network of inquestors operating under a long Central Algorithm Mandate.

TUZ-2,437,022 exists as another inquestor within that same network.

The immediate anomaly is not proof of substitution, conspiracy, or missing syrakis. It is a cluster of behavioral projection-vector shifts followed by behavioral normalization with reduced consciousness-derived behavioral entropy.

No malicious corporate behavior has been detected. The corporations appear to be acting ethically under severe informational constraint.

The central institutional problem is game-theoretic: ethical actors under partial knowledge, dangerous information, secrecy, and incompatible obligations can still create catastrophic obstruction.

Kymintus becomes the nearest actionable lead, but he is not found in this chapter.

TUZ-66941 does not yet know exactly where Kymintus is.

TUZ-2,437,022 warns that Kymintus is probably monitored and that an inquestor's approach may trigger defensive action.

Chapter 14 must begin after this with TUZ-66941 searching for Kymintus, not meeting him.

H. Open Problems

Preserve objective narration and avoid turning TUZ-66941 into a humanized POV.

Clarify how Mike later narrates archived machine-state history without making the passage feel omniscient.

Keep the anomaly subtle. Do not reveal the full t-signal concealment yet.

Do not make the corporations look evil, corrupt, or malicious. Their danger must come from ethical game-theoretic failure, not villainy.

Do not let TUZ-2,437,022 give TUZ-66941 a resolved location for Kymintus. Kymintus must be a lead, not a found target.

Make sure Chapter 14 performs the search and Chapter 15 performs the direct encounter.

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

The Search for Kymintus

B. Chapter Function

This chapter follows TUZ-66941 after Kymintus has already been identified as the first actionable lead in the external investigation. The chapter does not contain the first discovery of Kymintus as a lead; that belongs to Chapter 9. Its function is to show that locating a single syraki or syraki-like entity inside the Complex is not a simple database query, but a difficult computational, contractual, topological, and logistical operation.

The chapter also demonstrates that movement inside the Complex is not effortless. Direct connection across branches, RUN layers, congested routes, permission boundaries, and computationally expensive paths may be harder than indirect movement through other routes. Even an inquestor under Central Algorithm Mandate must obey physics, computation, contract, privacy, topology, and local RUN rules.

By the end of the chapter, TUZ has not found Kymintus directly, but has reconstructed a continuity trail leading from a private retro-anthropic RUN toward Oskiparisis.

C. Required Context Before Chapter

TUZ-66941 already knows Kymintus is a lead.

TUZ-2,437,022 has already warned TUZ-66941 that Kymintus is almost certainly being monitored by corporate systems or agents. If those systems detect the approach of an inquestor, they may move Kymintus, obscure him, redirect access, erase traces, increase computational cost, or otherwise prevent contact.

No malicious corporate intent has been detected. The situation remains part of the broader game-theoretical ethical failure: dangerous information, partial knowledge, defensive secrecy, incompatible obligations, and harm-minimizing agents producing obstruction and catastrophe without simple villainy.

D. Character State at Chapter Start

TUZ-66941 is precise, narrow, non-emotional, and mission-bound. He proceeds by evidence, probability, authorization, and Mandate. He has real authority, but he is not omnipotent.

Kymintus is absent from the chapter as a direct presence. He exists only as a trace, a pattern, a manifest residue, and a continuity problem.

The corporations or corporate-adjacent systems remain an implied external pressure. Their possible surveillance of Kymintus gives the chapter its procedural tension.

E. Chapter Description - Pre-Draft

TUZ-66941 begins the search for Kymintus.

From his operational perspective, the search algorithm resembles an impossible procession of realities passing before him at extreme speed. RUN after RUN flashes through the search-field: human-like worlds, posthuman pleasure structures, abstract social geometries, mathematical habitats, maintenance realities, ritualized dream-spaces, obsolete civilization archives, and forms of existence no human mind could perceive without collapse.

Billions upon billions of realities pass through the algorithm. A human consciousness would be destroyed by the rate, density, and alienness of the traversal. TUZ does not experience it as wonder. He processes it as evidence.

The search lasts approximately one month and three days.

TUZ does not find Kymintus. He finds a strong trace.

Kymintus' hash, t-signal residue, or manifest signature appears in a private RUN at a relatively recent timestamp. The RUN is not encrypted, but it is private. TUZ requests access under Central Algorithm Mandate, identifies himself as an inquestor, and is admitted through the proper contractual procedure.

The RUN is highly retro-anthropic and intelligible to humans. Internally, it has approximately thirty-six thousand human years of history. Humans, or human-intelligible beings, already exist there. The world resembles an alien fantasy planet structured through old human RPG logic: kingdoms, palaces, magical forests, wars, politics, treasure legends, internal artificial intelligences, and connected events.

It evokes something like Dungeons & Dragons or old fantasy role-playing games without literally being one of them. It is a niche interest inside syraki civilization, but it contains billions of connected beings.

This kind of RUN explains why Kymintus may have left a trace there. He was one of the few beings known to be unusually interested in retro-anthropic, human-intelligible realities.

TUZ connects through an inquestor interface used for retro-anthropic RUNs. The contract forbids him from breaking the rules of the world. He has limited Mandate privileges, but they cannot be used as divine violation. He may obtain local resources, use restricted non-disruptive advantages, persuade local artificial intelligences within acceptable bounds, and follow lawful paths through the world's own systems. He cannot simply tear open the RUN and seize the answer.

TUZ identifies a palace contact who may have had indirect access to Kymintus' local manifestation. To reach the palace, he buys a mount using local resources and rides across the world toward the capital.

The image is important: an inquestor of the Central Algorithm, carrying civilization-level authority, traveling through a fantasy landscape on an animal because contractual law prevents him from violating the local reality.

At the palace, TUZ obtains an audience with the king by saying exactly what must be said within that world's political grammar. He may lie inside the fiction of the RUN, presenting himself as an envoy or agent from another realm, because that deception belongs to the accepted rules of the world rather than to an external violation of the RUN.

The king is surrounded by a royal guard. TUZ detects that the guards are syrakis under deep immersion, but they do not know they are syrakis. They believe themselves to be native to that world.

When TUZ begins to speak indirectly about his mission, the guards interpret him as a threat: perhaps an assassin, perhaps a demon, perhaps an enemy envoy. They draw arrows against him.

TUZ does not fight. He orders the RUN to stop.

The world freezes. Motion ceases. The fantasy interface collapses into a suspended systemic state, almost digital in appearance. The king and the guards recover their syraki context. They remember what they are. They understand that TUZ is an inquestor and that his question concerns Kymintus.

TUZ asks whether they know Kymintus or possess information about his presence in the RUN. They do not know him personally, but they know the owner of the RUN. Within seconds, they contact the owner and obtain the complete diagnostic package related to Kymintus' connection.

The diagnostic is transferred to TUZ.

TUZ thanks them. He informs them that he will restore the original interface and alter their local continuity so the RUN remains coherent. The palace resumes. The king and guards return to their roles. They do not remember the interruption as a rupture. They remember the encounter as something that made sense inside the world.

TUZ remains in the RUN for approximately one and a half to two additional months.

He investigates Kymintus' local trajectory through logs, movement records, purchase trails, event records, testimony, and diagnostic residue.

In this world, a being may enter by ordinary sexual birth, or emerge fully formed from certain magical forests. This is culturally normal inside the RUN. TUZ learns that Kymintus emerged from one of those forests under a different local name.

Kymintus then lived there for several years as a treasure hunter, pursuing legendary artifacts, hidden sites, and rumors. He had a wife in that reality. He followed maps, purchases, movements, and local quests until he reached a cave.

There he died.

The cave contains the remains of Kymintus' local body, killed by a trap placed by native beings to protect against bounty hunters and treasure seekers. TUZ reaches the cave through the testimony of the woman who had been Kymintus' wife in that world. She is also a syraki under immersion, but she does not know it.

TUZ finds the remains and recovers a necklace or similar object associated with Kymintus' death. He returns to the woman and gives it to her as proof that he found him. He comforts her within the limits of the world, telling her that Kymintus is in a better place.

The statement is true in more than one sense.

TUZ uses the body, the logs, the purchase trails, the movement records, the local event records, and the diagnostic data to reconstruct Kymintus' exit. The timestamp of the local death matches a registered disconnection in the exit manifest.

Kymintus did not end there.

After leaving that RUN, his mind was split across several RUNs simultaneously. Some instances appear to have run maintenance processes. Others appear hedonic. One continuity trail remained relatively retro-anthropic and computationally near the RUN TUZ is already inside.

That trail leads to Oskiparisis.

Oskiparisis is a three-dimensional RUN made of floating static areas: houses, apartments, terraces, rooms, and private spaces suspended in a purple universe. The stars visible in the sky are not stars. They are the terrains or domains of other users. There are trillions of them.

One of Kymintus' minds is there, inside one of those houses.

TUZ chooses to connect to Oskiparisis because the route is near and does not require a major new expenditure of resources.

The chapter ends with TUZ initiating the connection.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

TUZ spends approximately one month and three days running a deep search algorithm across the Complex before finding a strong Kymintus trace.

The trace leads to a private retro-anthropic RUN with approximately thirty-six thousand human years of internal history.

The RUN is not encrypted, but it is private, and TUZ enters through contractual authorization under Central Algorithm Mandate.

Kymintus lived inside that world under a local identity, emerged from a magical forest, became a treasure hunter, married, and died in a cave.

His local death corresponds to an exit manifest.

The logs show that Kymintus later split across multiple RUNs.

One continuation is in Oskiparisis, a purple three-dimensional RUN of floating houses, apartments, and user terrains.

TUZ connects to Oskiparisis at the end of the chapter.

H. Open Problems

Clarify the exact local name Kymintus used inside the fantasy RUN.

Clarify whether the RUN owner has any personal relationship with Kymintus or merely provides diagnostic access.

Decide whether the wife remains only an emotional witness or later becomes relevant as an example of immersed syraki identity.

Preserve the rule that TUZ has authority but does not casually violate RUN contracts.

Clarify the exact terminology for Kymintus' trace: hash, t-signal residue, manifest signature, symbolic tissue, or another canonical term.

A. Title

Oskiparisis

B. Chapter Function

This chapter brings TUZ-66941 into direct contact with Kymintus for the first time.

Its function is to reveal that Kymintus is not a syraki, but a nenthor or proxy carrying a masked syraki signal. The chapter also proves that an external force is actively monitoring the investigation and is willing to destroy a RUN, erase evidence, and interfere with an inquestor under Central Algorithm Mandate.

The chapter begins as an interview and ends as an ontological crime scene.

C. Required Context Before Chapter

TUZ has spent months searching for Kymintus.

He has followed a continuity trail from a retro-anthropic fantasy RUN to Oskiparisis. Oskiparisis is computationally near enough for TUZ to attempt connection without a major additional expenditure.

TUZ knows from prior warning that Kymintus may be monitored and that an inquestor's approach may trigger defensive action.

Kymintus himself is not presumed hostile. There is no evidence that he knows he is being monitored or that he understands the significance of his own condition.

D. Character State at Chapter Start

TUZ is cautious, precise, and aware that the act of approaching Kymintus may trigger external interference.

Kymintus is relaxed, cooperative, and immersed in the pleasures of Oskiparisis. He does not know that anyone has tried to obstruct TUZ's access. He does not know that his own signal has been masked.

The external force monitoring Kymintus is not yet identified.

E. Chapter Description - Pre-Draft

TUZ attempts to connect to Oskiparisis.

Immediately, interference begins. Something artificially increases the computational cost of the connection, forcing TUZ to expend more resources than the route should require. The obstruction is not ordinary congestion. It behaves like an active attempt to prevent or delay access.

TUZ issues an alert and analyzes the interference.

He determines almost immediately that Kymintus does not know this is happening. Kymintus is not participating in the obstruction. He is not fleeing, not hiding, and not trying to protect himself. He is simply inside Oskiparisis, enjoying the local pleasures.

TUZ completes the connection.

Oskiparisis presents itself as a purple three-dimensional universe of floating homes, apartments, terraces, and domains. The sky is filled with lights that are not stars, but user terrains. Trillions of presences exist in the RUN.

TUZ locates the house containing the Kymintus continuation and enters through the proper channel.

Kymintus is not alarmed by the inquestor. He treats TUZ as a visitor and invites him to partake in the pleasures available there.

TUZ thanks him and declines.

TUZ identifies himself, explains that he is present under Central Algorithm Mandate, and states that Kymintus is under investigation. TUZ does not hide the reason. Kymintus has the right to know.

TUZ's first question is whether Kymintus knows of anyone observing him, monitoring him, or interfering around him.

Kymintus does not. He is normal, calm, and cooperative.

TUZ explains that Kymintus' behavioral pattern matched an anomalous cluster shared by other investigated cases. Kymintus does not interpret this as strange. He confirms that he worked for Valtir & Blue and that they contacted him for a mission.

He understands the question as an investigation into past work, not as a threat.

From the beginning of the encounter, TUZ has already detected something wrong. Kymintus' t-signal or symbolic tissue appears to match a syraki, but his response latency, internal texture, and operational behavior do not fully align. TUZ can distinguish syraki from nenthor structures at levels most citizens cannot perceive.

While the conversation continues, TUZ sends a direct request to the Central Algorithm for deeper analysis.

The result confirms the anomaly.

Kymintus' signal has been masked. He is not a syraki. He is a nenthor or proxy carrying a masked syraki identity signal.

TUZ asks him whether he is feeling pleasure.

Kymintus answers that he is. He says that he himself is feeling pleasure.

The conversation turns philosophical without becoming sentimental. Kymintus describes his own pleasure, preference, continuity, and self-model as real from within his architecture. TUZ does not insult or deny him.

TUZ states the evidence: the signal has been masked; the entity speaking as Kymintus is not a syraki; the structure is consistent with a nenthor or proxy maintaining Kymintus' identity, social behavior, and apparent t-signal.

Kymintus finds this strange because it does not make sense inside his self-model. Yet when TUZ transmits the evidence, Kymintus understands immediately that TUZ is not lying.

He accepts the seriousness of the situation and says that he will assist the Central Algorithm in every possible way.

TUZ asks what Kymintus remembers about his work for Valtir & Blue.

Kymintus remembers being contacted for a mission of espionage. After that, his memories become gradually confused.

TUZ interprets this as evidence that Kymintus' mind or algorithm was altered, scrambled, or masked. He sends a confirmation request to the Central Algorithm stating that it is statistically plausible that Kymintus' memory structure was deliberately disturbed.

Kymintus remains cooperative. He does not hide information. He does not resist. He wants to help.

TUZ leaves Kymintus' house.

Outside, while he is already away from the interior, he hears Kymintus shout from inside: "What's that?"

TUZ looks back to see what is happening.

He does not see Kymintus.

He does not see what happens to him.

At that moment, a figure approaches TUZ directly and places a hand on TUZ's face.

The figure says: "I'm sorry, sir, but we are deleting this RUN."

TUZ remembers nothing after that.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

TUZ experiences artificial computational interference while trying to connect to Oskiparisis.

The interference confirms that someone or something is attempting to prevent or delay access to Kymintus.

TUZ determines that Kymintus does not know about the obstruction.

Kymintus is found in Oskiparisis, relaxed and cooperative.

Kymintus confirms contact with Valtir & Blue and remembers being recruited for a mission of espionage.

His memories become confused after that point.

TUZ confirms through the Central Algorithm that Kymintus is not a syraki, but a nenthor or proxy carrying a masked syraki signal.

Kymintus understands that TUZ is not lying and agrees to assist the Central Algorithm.

At the end of the chapter, TUZ leaves Kymintus' house, hears Kymintus shout from inside, looks back, and is intercepted by a figure that announces the deletion of the RUN.

TUZ loses memory after the contact.

Kymintus does not see what happens to TUZ.

H. Open Problems

Define the visual form of the figure that touches TUZ's face.

Decide whether the figure should appear administrative, anonymous, humanoid, or merely interface-shaped.

Preserve the distinction that Kymintus does not see what happens to TUZ.

Preserve the distinction that TUZ is affected, not Kymintus in the visible scene.

The next TUZ chapter must reveal that Oskiparisis was deleted, all connected users were disconnected rather than killed, the official explanation was a rare bug, and all manifests, diagnostics, logs, and Kymintus traces vanished.

A. Title

Decohesion Zone / Reality Jumps

B. Chapter Function

This chapter returns the narrative to the RT-874 after Oskiparisis and makes the damaged cohesion system visibly dangerous. Its function is to show that the reality jumps are no longer isolated to Mike, introduce the recoverable decohesion zone as a Plotter diagnostic, and turn the crew's shared instability into both cosmic horror and the first clear expression of syraki gregariousness under human downgrade.

C. Required Context Before Chapter

The previous chapter has followed the events around Oskiparisis. The story now returns to the RT-874. Mike, Felix, Susan, and Kallom-4000 are active aboard the omniship. Ismael is still present but unconscious and being stabilized. The RT-874 is already programmed to move toward Lucia. Kallom-4000 projects that reaching her should take roughly two and a half weeks in human time, but time in that region is unstable and all calculations remain approximate.

D. Character State at Chapter Start

Mike, Felix, and Susan are reunited under damaged and frightening conditions. They are increasingly affected by strange states of consciousness, blackouts, collapses, disappearances, disorientation, and reality jumps. Ismael remains unconscious and under stabilization. Kallom-4000 is functioning as the crew's technical interpreter and creates diagnostic visualizations through the Plotter at the crew's request.

E. Chapter Description - Pre-Draft

After the events around Oskiparisis, the narrative returns to the RT-874. The active group aboard the omniship is Mike, Felix, Susan, and Kallom-4000, with Ismael still present but unconscious and being stabilized. The ship is already programmed to move toward Lucia. According to Kallom-4000's projections, reaching her should take roughly two and a half weeks in human time, but this estimate cannot be guaranteed. Time in that region is unstable, and all calculations remain approximate.

The chapter focuses on the reality jumps and strange states that begin affecting the reunited crew more openly. The phenomenon no longer appears to be an isolated problem affecting only Mike. Felix and Susan also begin to experience strange states of consciousness, brief disappearances, collapses, disorientation, blackouts, and reality jumps. Sometimes a jump seems externally brief. Sometimes a person disappears and returns almost immediately. Sometimes the person reappears elsewhere inside the RT-874. Sometimes the body collapses unconscious. The external duration of the event does not reveal the subjective duration experienced by the person who jumped.

Through the Plotter, the crew begins to understand the problem more clearly. In normal operation, the RT-874 appears as a point. If the cohesion system were functioning correctly, all crew t-signals would remain collapsed into that point. At the crew's request, Kallom-4000 creates a multidimensional diagnostic visualization: a blob around the ship's point. This blob is not the ship itself. It is the recoverable decohesion zone: the probability zone within which crew members tend to fall during reality jumps while the cohesion system is damaged but not completely broken.

When a crew member jumps, the Plotter can show where that t-signal falls inside the decohesion zone. As long as the t-signal remains within the blob, mathematical recovery remains possible, and the system can pull the person back and collapse them inside the RT-874. If a t-signal falls outside the blob, recovery becomes mathematically impossible. The person is not merely lost in a difficult way. They are beyond the remaining precision of the damaged cohesion system.

This creates the main cosmic horror of the chapter. The crew realizes that the jumps are not hallucinations, dreams, or ordinary spatial displacements. They are failures of mathematical precision in the cohesion of the ship, the crew, the t-signals, and the navigational reality around them. A jump that lasts one second externally may contain a lifetime of subjective experience, less than a second, or something impossible to measure. The person who returns may remember everything, almost nothing, fragments, sensations, or only the certainty that something happened.

At the same time, the chapter begins to show the natural gregariousness of syrakis under human downgrade. Mike, Felix, and Susan do not relate to one another like humans slowly becoming friends or lovers. Their closeness is instinctive, structural, and ordinary for their kind. They seek proximity, touch, shared attention, comfort, emotional regulation, and mutual care as naturally as humans drink water. The horror of the jumps pushes them toward one another, not away from one another. Their early affection is not a romance subplot in the human sense, but the first visible expression of syraki social life under damaged conditions.

The chapter should balance technical investigation, cosmic fear, and syraki intimacy. The crew does not yet fully understand the RT-874's condition, but they understand enough to know that the ship is damaged at a level deeper than normal navigation. The Plotter reveals that the ship's apparent stability is only partial. They are still being recovered, but recovery depends on remaining inside a narrowing mathematical possibility.

The chapter ends with Ismael waking up.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

After Oskiparisis, the narrative returns to the RT-874 with Mike, Felix, Susan, Kallom-4000, and unconscious Ismael aboard. The ship is moving toward Lucia with a rough two-and-a-half-week estimate in unstable time. Reality jumps now affect Felix and Susan as well as Mike. Kallom-4000 uses the Plotter to visualize the RT-874 as a point surrounded by a recoverable decohesion-zone blob. A jumped crew member's t-signal can be recovered only while it remains inside this blob. Outside it, recovery is mathematically impossible. The chapter frames the jumps as failures of cohesion, t-signal precision, and navigational reality rather than hallucinations. It also establishes syraki gregariousness under human downgrade: the horror pushes Mike, Felix, and Susan into instinctive proximity, touch, care, and shared regulation. The chapter ends when Ismael wakes up.

H. Open Problems

Define how the Plotter visualizes a multidimensional decohesion zone in prose without making it feel like an ordinary screen graphic. Decide which first jump belongs to Felix and which belongs to Susan, how much subjective memory each returns with, and how Ismael's awakening should interrupt or reframe the chapter ending.

A. Title

Internal Navigation / Laka's Page

B. Chapter Function

This chapter wakes Ismael, restores him as the ranking active crew member aboard the RT-874, and reframes the ship's mystery. Its function is to move the investigation beyond ordinary spatial travel or temporal-prototype speculation toward the possibility that the RT-874 is navigating through the interior of the Complex itself. It also gives Mike a dream encounter with Laka that points him toward a specific book page without revealing the page's contents yet.

C. Required Context Before Chapter

Ismael has just awakened after the previous chapter. Mike, Felix, Susan, and Kallom-4000 have already learned about the crash, reality jumps, strange states, the Plotter, the recoverable decohesion zone, the route toward Lucia, and the hypothesis that the RT-874 may be operating as a temporal prototype. The crew is still downgraded into human-like patterns and must sleep as part of both bodily and mental stabilization.

D. Character State at Chapter Start

Ismael wakes confused but alive aboard the RT-874. Mike, Felix, Susan, and Kallom-4000 care for him with the immediate social warmth and inclusion natural to syrakis under human downgrade. Ismael becomes the ranking active crew member present and begins treating the situation as a serious navigational and command problem. Mike remains emotionally vulnerable, especially around Laka, but is still functioning inside the group.

E. Chapter Description - Pre-Draft

Ismael wakes aboard the RT-874 and is cared for by Mike, Felix, Susan, and Kallom-4000. The reunion carries the natural social texture of syraki life: affection, attention, physical care, emotional warmth, and immediate inclusion. Ismael asks what is happening and where they are. No one can give a complete answer. The others tell him everything they know: the crash, the reality jumps, the strange states, the Plotter, the recoverable decohesion zone, the ship's route toward Lucia, and the hypothesis that the RT-874 may be operating as some kind of temporal prototype.

Ismael becomes the ranking active crew member present aboard the ship. As Navigator, he orders a serious meeting to consolidate the available information. He studies the Plotter, the navigation data, the behavior of the t-signals, the route, the cohesion problem, and the way the ship is moving. The others explain that they have considered whether the RT-874 might be a prototype temporal vessel. Ismael rejects this as unlikely. He has had access to temporal navigation data before, and the RT-874's current behavior does not resemble temporal navigation.

He also concludes that it does not resemble normal spatial navigation. The ship is not behaving as if it were simply moving through space, and it is not behaving as if it were moving through time. To Ismael, the data resembles navigation through the interior of the Complex.

This leads to a discussion about why such a thing would exist. Ismael suggests that the RT-874 may be an extremely efficient vessel for moving through the Complex itself. The others do not treat this as absurd. For syrakis, the Complex is not a simple server, a production cluster, or a table of machines. It is a vast civilizational reality: multilayered, overlapping, filled with countless realities, consciousness threads, artificial environments, automated domains, lived worlds, and structures so large that even syrakis experience it as immense. A Matrix-like human virtual reality would be trivial inside the Complex. The real question is not whether internal navigation through the Complex is conceivable. The question is why the RT-874 would be doing it here, under these conditions, and with this level of secrecy and danger.

After the meeting, Mike sleeps. Sleep is necessary because their downgraded minds are operating under human-like patterns. It is not merely that the body is tired. The mind itself must follow the rhythm of the downgrade. Sleep also has an important stabilizing function for the ship and the crew's condition.

While sleeping, Mike has another strange dream. He finds himself in an alien forest, walking along a path that feels prepared for him. He does not know where he is, but the place seems deliberate. At the end of the path, he sees two beings speaking. Both have alien bodies, but both are beautiful. They invite him to sit with them. Mike feels that something is profoundly strange, though he cannot explain why.

One of the beings is the mysterious entity that appeared to him in an earlier dream. The entity presents the other being to Mike, saying something like: "I believe you recognize this friend of mine." Mike realizes that the other being is Laka, his childhood friend.

Mike and Laka speak with affection. Their conversation is gentle, strange, and spiritual in tone. Mike tells Laka that he misses him. He wonders why Laka chose to end his own existence despite all the wonderful experiences they had shared and all the wonders existence still contained. Laka does not answer in a simple psychological or biographical way. He tells Mike that the world, and existence itself, are much greater than they can understand.

Near the end of the dream, Laka tells Mike to look for a specific book and a specific page.

Mike wakes in the middle of the night. He goes to find the book. It is one of the books he personally chose to bring aboard the RT-874. The book was written by Laka's downgraded human version. Mike opens it to the page named in the dream. His eyes widen. He becomes completely still, stunned by what he sees. The moment feels mysterious, disturbing, and finally significant.

The scene ends without revealing what Mike read on the page.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

Ismael wakes aboard the RT-874 and is cared for by Mike, Felix, Susan, and Kallom-4000. After hearing what the crew knows about the crash, reality jumps, Plotter, recoverable decohesion zone, route toward Lucia, and possible temporal-prototype hypothesis, Ismael takes command as Navigator and orders a serious meeting. He rejects the temporal-vessel theory because the RT-874's behavior does not match temporal navigation data he has seen before. He also rejects ordinary spatial navigation. The data instead resembles navigation through the interior of the Complex. The crew recognizes that internal navigation through the Complex is conceivable because the Complex is a vast civilizational reality rather than a simple server. Later, Mike sleeps and dreams of an alien forest. The mysterious earlier dream entity introduces him to Laka. Laka tells Mike that existence is greater than they understand and instructs him to find a specific book and page. Mike wakes, finds a book written by Laka's downgraded human version, opens to the named page, and is stunned. The page's contents remain unrevealed.

H. Open Problems

Define the specific book title, the exact page number or page marker, and what Mike reads there. Decide how much Kallom-4000 can understand about internal Complex navigation at this stage. Decide whether the mysterious entity's language should feel gentle, priestly, clinical, or alienly casual during the Laka dream.

A. Title

TUZ-66941 / Oskiparisis Propagation

B. Chapter Function

This chapter returns to TUZ-66941 after Kymintus and Oskiparisis vanish, reframing the incident as a nonviolent but hostile attack on access, evidence, continuity, and investigative function. Its function is to escalate the mystery from a local RUN anomaly into a distributed Complex-scale investigation, define Detached and Headless RUNs in narrative context, and launch a massive parallel search for a physical substrate contradiction.

C. Required Context Before Chapter

Kymintus has vanished after the events in Oskiparisis. TUZ-66941 has suffered an intervention that obstructed his investigation without harming him as a conscious being. The reader should already know Oskiparisis as the RUN involved in Kymintus's disappearance and should understand that modern syraki ethics prohibit direct attacks on conscious entities.

D. Character State at Chapter Start

TUZ begins in a state of focused posthuman alarm. He is not injured, panicked, or emotionally destabilized in a human way, but he recognizes that something impossible has happened: Kymintus's t-signal is gone, Oskiparisis has vanished from manifests, and the administrative continuity of the Complex has been violated at a level that should not fail.

E. Chapter Description - Pre-Draft

Chapter 18 returns to TUZ-66941 immediately after the events involving Kymintus and Oskiparisis. The chapter opens with TUZ reflecting on the nature of the intervention he suffered. Modern syrakis and nenthors do not attack conscious beings. This is not merely a social preference or legal convention, but one of the deep operational foundations of the Complex. Even an Ordinant-class inquestor is not an exception. Therefore, whatever happened to TUZ inside Oskiparisis cannot be interpreted as a violent attack in the ancient human sense. It was hostile, obstructive, and deliberate, but its nature was nonviolent. It did not harm TUZ as a conscious entity. It attacked his access, his evidentiary continuity, and his investigative function.

At the beginning of the chapter, TUZ confirms the core impossibility: Kymintus has disappeared completely. His t-signal no longer exists in any detectable form. He is not hidden, transferred, encrypted, quarantined, or blocked behind a normal permission barrier. The same is true of Oskiparisis itself. The RUN has vanished from the relevant manifests as if it had never existed. This should not be possible.

TUZ propagates a Code 10, maximum level, to all other TUZ involved in the wider investigation. Every available TUZ instance connected to the Mandate is ordered to place maximum priority on locating any information related to Kymintus, the missing t-signal, Oskiparisis, its manifests, its contracts, its ownership traces, or any possible physical or administrative remnant.

TUZ then begins with the nearest witnesses. He locates four members who had been in RUNs or regions closest to the affected area and speaks with all of them. Each confirms the same basic event: they were disconnected abruptly. All of them had already sent diagnostics to the Central Algorithm. Their initial interpretation was that they had suffered some strange bug, rare but not conceptually impossible. When TUZ tells them that Oskiparisis itself has vanished from the manifests, they are astonished. One of them experiences fear in a posthuman sense: not primitive panic, but a deep destabilization caused by the realization that a layer of reality administration that should be reliable has failed in an impossible way.

The chapter then clarifies the nature of Oskiparisis. It was a Detached RUN. Detached RUNs are RUNs created autonomously, or created by a syraki or nenthor whose original owner later withdrew from ownership without sealing the ownership contract. They remain legally legible and available for future ownership. A Detached RUN is ownerless but adoptable. This differs from a Headless RUN, whose ownership contract has been encrypted, sealed, or made inaccessible so that the RUN remains intentionally ownerless and cannot be claimed through normal mechanisms. Oskiparisis was not Headless. It had been left open to the community.

For that reason, TUZ contacts the original creator of Oskiparisis, Orsolan-2. He does this for two reasons. First, he needs to confirm that Orsolan-2 has no involvement in the disappearance. Second, he needs the hash of the original node where Orsolan-2 first activated the RUN. Orsolan-2 explains that he created Oskiparisis as a minor side project and later donated it to the community. He was not contacted by anyone suspicious about the RUN, received no unusual requests, and had no involvement in any later manipulation. When TUZ informs him that Oskiparisis has disappeared, Orsolan-2 is astonished. He checks for himself and confirms that the RUN is gone as if it had never existed.

This is technically absurd. RUNs are not entries in a single centralized database. There are central indexes for major RUNs, but there is no universal central database of all RUNs across the Complex. Maintaining such a database for everything would be computationally inefficient, unreliable, and structurally inappropriate for the scale of the Complex. Instead, RUNs are diagnosed and recognized through distributed propagation of manifests and contracts across immense numbers of nodes. Even if a RUN disappeared, its contracts, manifest fragments, ownership traces, hosting lineage, energy records, and propagation history should continue to exist in some form. Not even the Central Algorithm could simply make a mature RUN vanish from the entire distributed network once its manifests and contracts had properly propagated.

TUZ explains that the only scenario in which a RUN could truly disappear cleanly would be if it were deleted very early in its creation, before its manifests had propagated, or if the initial manifests themselves were destroyed before they spread through the network. Even that would be extremely difficult, but not completely impossible. Oskiparisis, however, was not in that state. It was an established Detached RUN with a propagation history.

Using the hash of the original node provided by Orsolan-2, TUZ reconstructs the RUN's initial propagation policy. He examines the history of its manifest distribution and projects probabilistically which nodes may still contain active or semi-active manifest traces related to Oskiparisis. He is not searching blindly across the Complex. He is rebuilding the propagation tree from the original activation point.

TUZ requests additional computational power from the Central Algorithm to perform a super-diagnostic across the Complex. The request is accepted. With this expanded power, he runs a rapid verification script and discovers that the propagation state of Oskiparisis is marked as degraded. In recent supercycles, most nodes have failed to confirm a valid health check originating from the RUN and have begun marking it as inexistent. Within only a few more supercycles, the network will likely converge toward marking Oskiparisis as inexistent across all remaining nodes.

This does not mean that every trace is gone. Its contracts still exist in fragments across the Complex, but they now lack a valid origin. They are distributed references without a living source. If Oskiparisis had merely become corrupted, the Complex should have frozen it, paused it, quarantined it, or placed it into debugging. If it were Headless and dead, it should still have entered a post-mortem or depuration state. But Oskiparisis is not there. It has not merely failed. Its operational substrate is gone.

TUZ then requests another authorization from the Central Algorithm, this time to inspect logs and perform depuration at one of the most basic layers of the Complex. This kind of examination is so difficult that only highly specialized syrakis normally operate at that level. For a human analogy, it would resemble trying to understand raw binary directly, except at a vastly more complex scale. Because TUZ has been granted additional power, he is able to proceed.

At that lower layer, he discovers that several supercycles earlier, something abnormal happened. The physical addressing of Oskiparisis was moved several times. Readdressing itself is not impossible. It is often performed automatically by maintenance algorithms. But the normal tendency of such processes is to make a RUN safer, more redundant, and more distributed. In the case of Oskiparisis, the opposite happened. Its distribution index was reduced. The RUN became progressively less distributed.

This alone is not proof of deliberate action. A reduction in distribution can happen under certain maintenance conditions. But in this case it sounds wrong. TUZ continues the investigation and notices that the reduction of the RUN's distribution index coincides with Kymintus's last connection to Oskiparisis, which TUZ reconstructs from surviving manifest traces. When Kymintus entered the RUN, something began to reduce the distribution of Oskiparisis, as if the RUN were being made less safe.

TUZ then analyzes the remaining physical addressing. Even after the reduction in distribution, the physical address space is still spread across several solar systems. Some routes use routing contracts, making it extremely difficult to map exactly where a given address would resolve in Base Reality. Even for TUZ, mapping the entire physical addressing structure would be computationally impossible.

But he does not need to map all of it.

If Oskiparisis was erased by physical destruction, substrate corruption, or some alteration of its technological base, TUZ only needs one suspicious address. The logic is not "all addresses must be proven abnormal." To refute the hypothesis that all physical addresses are normal, one counterexample is enough. The opposite of "all are intact" is not "all are damaged." It is "at least one is damaged."

TUZ therefore reduces the impossible problem to a finite proof strategy. He selects the most suspicious addresses: those whose routing, timing, maintenance patterns, reduction in distribution, or correlation with Kymintus's last connection make them statistically more likely to contain a material anomaly.

At the end of the chapter, TUZ sends another Code 10. He requisitions 10,000 other TUZ and redirects them to investigate the selected physical addresses simultaneously. Each TUZ is assigned an endpoint, physical address, routing chain, or substrate location to inspect. The purpose is to find at least one material contradiction capable of proving that Oskiparisis did not merely suffer a distributed administrative failure, but that some part of its physical substrate was actually damaged, corrupted, destroyed, or altered.

The chapter ends with this massive parallel investigation being launched.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

TUZ-66941 confirms that Kymintus's t-signal and Oskiparisis have vanished in a way that should be impossible. He classifies his own obstruction as hostile but nonviolent, propagates Code 10 to the Mandate, interviews nearby witnesses, confirms Oskiparisis was a Detached RUN rather than a Headless RUN, and contacts Orsolan-2 for the original activation-node hash. Using that hash, TUZ reconstructs the RUN's propagation tree, obtains additional Central Algorithm computation, discovers that Oskiparisis is being marked degraded and then inexistent across nodes, and finds evidence that its physical addressing was repeatedly moved while its distribution index was reduced around Kymintus's last connection. He narrows the impossible Complex-scale search into a finite proof strategy and launches 10,000 TUZ instances to inspect suspicious physical addresses for a material contradiction.

H. Open Problems

Define the exact tone and personality of Orsolan-2. Decide whether any of the four nearby witnesses should recur later. Specify how Code 10 differs operationally from lower codes. Define what a supercycle means in this investigative context. Decide what kind of first material contradiction, if any, the 10,000 TUZ will eventually discover.

A. Title

TUZ-66941 / Physical Substrate

B. Chapter Function

This chapter shows the Complex from the outside for the first time and turns the Oskiparisis investigation from distributed manifest failure into physical substrate evidence. Its function is to establish the exterior and interior texture of Complex infrastructure, reveal that suspicious physical addresses are materially damaged, trace the anomaly through maintenance drones and a falsified status board, and point TUZ toward a supply-chain origin on Ukabkys.

C. Required Context Before Chapter

TUZ has launched a Code 10 parallel investigation into suspicious physical addresses related to Oskiparisis. He has already concluded that the RUN's propagation degraded, its physical addressing was repeatedly moved, and 10,000 TUZ instances have been deployed to inspect selected endpoints across the Complex.

D. Character State at Chapter Start

TUZ begins in active investigative transit through Base Reality. He is calm, focused, and operating as an Ordinant-class inquestor with expanded authority and computation. His current body is a vessel-form, because at this scale he does not ride inside a ship; he is the ship.

E. Chapter Description - Pre-Draft

Chapter 19 continues with TUZ-66941. It is the first chapter that shows the Complex from the outside.

TUZ is traveling through Base Reality toward one of the millions of physical nodes of the Complex. He is not inside a spaceship. He is the spaceship. His current body is a vessel-form adapted for transit, investigation, and direct interaction with physical infrastructure. Through him, the reader sees the exterior silence of the Complex: ships moving between distant structures, drones crossing empty space, robotic systems working without speech, stations and megastructures operating in the dark. From the outside, the Complex is not a city, a habitat, or a humanized space station. It is infrastructure: cold, silent, technical, and immense.

TUZ approaches the selected megastructure, one of the physical nodes connected to the vanished addressing of Oskiparisis. The structure has an equivalent spherical diameter of roughly two hundred kilometers, although it is not a sphere. Its shape is deformed, irregular, covered with spikes, extrusions, antennae, radiator masses, armored volumes, computational blocks, and docking geometries. It is a giant computer built at megastructural scale.

TUZ enters it.

Inside, the node is vast but not habitable in any human sense. It contains tunnels, corridors, shafts, conduits, computational galleries, maintenance veins, and technical cavities. Some passages are broad enough for large machine bodies. Others are narrow, almost impossible to maneuver through in vessel-form. There are no roads, pedestrian paths, or human-scale spaces. The interior is dark, cold, quiet, and almost without light except for occasional luminous pathways moving across the walls, diagnostic pulses, or brief glows from active systems. Maintenance drones work continuously inside it. They are not decorative machines; they are part of the node's metabolism.

TUZ travels through the interior for a long time. The scene gives the reader a sense of the node's scale. He passes through technical corridors that seem never to end, through wider chambers that open only to reveal still more machinery, and through tighter regions where the structure feels less like architecture than like the interior of a computational organism.

Eventually he reaches the exact region associated with one of the suspicious physical addresses. He stops. A holographic diagnostic interface emerges from the wall, filled with characters unintelligible to any human mind. They move at impossible speed while TUZ interacts with them directly. He is debugging the specific region of the physical addressing he came to inspect.

The address is damaged.

The damaged region has suffered a cascade of decoherence, and its probability symmetry is fragmented. TUZ checks the logs of the sector. There is no recorded fire, collision, material rupture, known bug, overload, maintenance accident, external intrusion, or ordinary cause. The logs do not explain the damage.

TUZ disconnects from the diagnostic interface and approaches one of the maintenance drones working in the area. These drones are all highly advanced artificial intelligences, even when they are not nenthors. TUZ asks which drone or system was responsible for that sector at the exact moment of the damage. The drone provides the relevant data and location.

TUZ follows the trail through the interior of the node. The corridors become progressively narrower and darker. He continues through passages where maneuvering the vessel-body becomes increasingly difficult. The space becomes more technical, more compressed, less accessible. Finally, after forcing his way through the last reachable passage, he arrives at a dead end. He activates his lights.

At the end of the tunnel, TUZ sees the responsible maintenance drone. It is destroyed. It has been smashed against the wall, as if it were thrown there deliberately.

A dinkus marks the transition.

After the dinkus, TUZ has already received partial reports from the wider operation. 6,541 TUZ have confirmed their assigned physical addresses. The addresses they inspected are indeed damaged. Some damage patterns appear compatible with normal failures. Others are strange. The aggregate result confirms that the problem is not isolated to the address TUZ personally investigated.

TUZ then finds a dematerialization point inside the node and docks his vessel-form there. His body dematerializes and rematerializes as a Sector Engineer Drone: a machine-form resembling a worm with metallic hands, highly adapted to the narrow technical interiors of the megastructure. In this form, TUZ can move through the node's internal passages with far greater speed and precision.

He travels rapidly through the maintenance corridors until he finds another Sector Engineer Drone operating on nearby systems. This one is not a standard artificial intelligence. It is a nenthor named Ypapasiatih-9. The two stop facing one another and exchange languages.

TUZ asks Ypapasiatih-9 whether it knew that one of the maintenance drones had been destroyed. Ypapasiatih-9 says that this is impossible. It maintains a real-time list of the thousands of drones operating in that sector, and every one of them is marked as functioning perfectly. TUZ shows the evidence. Ypapasiatih-9 is astonished and cannot explain how the destroyed drone could be absent from the maintenance anomaly lists.

TUZ requests every relevant security log from the sector: camera feeds, manifests, entrance and exit records, executed programs, diagnostic reports, maintenance events, status reports, drone records, routing data, and all connected sector-level records. Ypapasiatih-9 transfers them immediately.

TUZ analyzes the material and finds no obvious anomaly. The logs show nothing abnormal. The only strange fact is that the destroyed drone entered the tunnel where the damaged address was located and never came out, even after hours. Despite this, the drone continued to appear as operational. Its signal was not being spoofed by another external source. The signal was coming from the destroyed drone itself. For some reason, the physically destroyed unit was still producing a valid "okay" status.

TUZ, Ypapasiatih-9, and the relevant sector authority analyze the body of the destroyed drone directly. The purpose is to determine how a machine can be physically destroyed while still reporting itself as alive and functional. The problem is found quickly. A computational board inside the drone had been replaced recently during a normal maintenance process. That board is wrong. It is simulating the drone's functional status even though the body has been destroyed.

The discovery does not immediately move TUZ to the next major external location. First, the local anomaly has to be closed. The board indicates that the problem existed before the drone was reactivated. The sector systems did not begin lying after the drone was destroyed. They were receiving valid signals from a faulty or altered internal component.

Another dinkus marks the transition.

After the cut, TUZ is still inside the same megastructure, but in a different region. He is now in an internal administrative base for sector administrators. It is not a human command room, bridge, office, or control center. It is a technical administrative environment designed for posthuman operators. TUZ is using a real body adapted to that environment, not a replacer. He arrives at an administrative spot filled with strange screens, holographic systems, interface structures, and nonhuman control surfaces.

There he finds the syraki sector administrator, Ahurussi. Ahurussi does not resemble a human. His body is like a huge metallic lobster, with several cables connected to his back and ten arms operating around him. Laser-like beams and interface streams emerge continually as he administers the surrounding systems. When the inquestor arrives in his own adapted posthuman body, Ahurussi stops working. The cables disconnect from his back and the administrative environment shifts into a formal interaction state.

Ahurussi already knows what happened. He says that the situation is extremely strange. He has already run diagnostics and searches across the relevant systems and found nothing abnormal. This suggests that the problem was already present in the computational board before the drone was reactivated. The sector did not corrupt the board after installation. The defect or alteration entered through maintenance or supply.

TUZ requests the full supply chain involved in the creation and maintenance of that drone. Ahurussi sends it to him. The database is extremely detailed, as if every atom of the drone were mapped: materials, origins, fabrication lineage, assembly chain, verification records, maintenance history, replacement events, transport contracts, routing, lot identifiers, installation data, certification, and all related technical records.

TUZ searches the database and identifies the drone's last maintenance event. During that maintenance, the specific computational board was replaced. He then finds the shipment that brought that board to the station and to that sector. The board came from one of the lots originating in a technical conglomerate on a nearby moon called Ukabkys, from a company specialized in that class of component.

The chapter also explains indirectly why physical shipment routes still exist in a civilization capable of molecular assembly and advanced fabrication. Not everything is more efficient when materialized locally. Specialized components may require particular materials, industrial environments, certification chains, high-scale fabrication, energy efficiency, reliability standards, contracts, and quality-control systems that make centralized production and physical shipping more efficient than local assembly. In many cases, moving verified matter through known supply routes is cheaper, safer, and more reliable than fabricating every component at the point of use.

The chapter ends with TUZ reflecting on the scale of the operation. The disappearance of Oskiparisis was not caused by a single anomaly. It involved physical addressing, substrate damage, degraded propagation, maintenance systems, drones, simulated functionality, replaced components, supply-chain movement, and reports from thousands of other TUZ confirming damaged physical endpoints. No ordinary syraki, ordinary nenthor, or entity below the High Echelon could execute anything comparable. This was a civilizational operation. It required powerful agents and deep orchestration.

The attack or operation was also highly entropic. Its fragments were dispersed through normal-looking failures: damaged addresses, maintenance events, routing complexity, degraded manifests, status inconsistencies, supply-chain substitutions, and local diagnostics that individually appeared explainable. Because of that entropy, it would have been extremely difficult for anyone to discover it, perhaps even for the Central Algorithm under ordinary diagnostic conditions.

What the responsible agents did not know was that the TUZ had already been investigating this class of impossibility for more than seven hundred years.

The chapter ends there.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

TUZ travels through Base Reality in a vessel-form to inspect one suspicious physical endpoint tied to Oskiparisis. The chapter establishes the Complex's exterior as silent megastructural infrastructure, then follows TUZ into a 200-kilometer-scale computational node. He confirms one address is damaged without ordinary logged cause, finds a destroyed maintenance drone whose own signal still reports normal functionality, receives reports that 6,541 TUZ have confirmed damaged assigned addresses, and transforms into a Sector Engineer Drone to continue inside the node. With Ypapasiatih-9 and sector administrator Ahurussi, TUZ traces the false status to a recently replaced computational board. The board came through a supply chain from a technical conglomerate on the moon Ukabkys. TUZ concludes the Oskiparisis event involved physical substrate, maintenance systems, supply-chain substitution, and high-level orchestration beyond ordinary actors.

H. Open Problems

Define the exact star system or orbital context of this megastructure and Ukabkys. Decide whether Ypapasiatih-9 and Ahurussi recur later. Specify the name and profile of the technical conglomerate on Ukabkys. Clarify what "probability symmetry is fragmented" means operationally in this substrate. Decide how soon the investigation moves from Ukabkys to the High Echelon implication.

A. Title

RT-874 / Checkpoints / Five Minutes

B. Chapter Function

This chapter gives the crew a quieter interval aboard the RT-874 while deepening the navigational mystery. Its function is to reveal that the ship's preserved navigation structure contains five Checkpoints followed by return to Brains' Cage, establish Ismael's fascination with the route as a nonlinear network of states and connections, and end with the uncanny discovery that only about five minutes have passed.

C. Required Context Before Chapter

Mike, Felix, Susan, Ismael, and Kallom-4000 are aboard the RT-874 and moving toward Lucia. Ismael is awake and functioning as Navigator. The crew already understands that reality jumps, decohesion, and damaged cohesion/navigation structures are affecting the ship, but the full mission structure remains unclear.

D. Character State at Chapter Start

The crew is tense but temporarily calmer than in the previous chapters. Mike is monitoring the time remaining to Lucia, Ismael is analyzing navigation with Kallom-4000, and the others are trying to reduce pressure in the lounge while still sensing that time and perception are behaving strangely.

E. Chapter Description - Pre-Draft

O capítulo começa com Mike observando o tempo exato restante até chegarem a Lucia. A tripulação sente que o tempo está estranho: às vezes parece que a viagem não avança, às vezes avança rápido demais, às vezes um intervalo parece longo demais para o tempo registrado. Todos percebem alguma coisa, mas ninguém sabe se é fenômeno real, efeito placebo, stress, downgrade humano ou contaminação subjetiva. Os registros da RT-874 estão perfeitos. Nada acusa falha. No meio disso, a crew passa algum tempo no lounge, conversando, tentando esvanecer um pouco a tensão. O capítulo é relativamente tranquilo comparado aos anteriores.

Ismael, com ajuda de Kallom-4000, analisa os dados de navegação e descobre que a RT-874 já vinha seguindo a rota padrão porque sair demais dela aumentaria a decohesion. Kallom não se lembrava da missão porque perdeu acesso a partes dos próprios dados, mas os dados de navegação preservam a estrutura: cinco Checkpoints, depois retorno ao Brains' Cage. Os documentos completos dos Checkpoints estão corrompidos, mas Kallom consegue reconstruir frases mínimas: Earth — Possible ancestral human planet. Must confirm. / The Reliquary — Emptiness. Intelligent signals. Exercise caution. / Rendezvous — Hypothesis confirmation. Critical reestablishment. Theory-dependent. / The Vortex — Strange signal. Severe disturbance. Nonsensical structure. / Akrelabium — Possible civilizational breakthrough. Para Brains' Cage, ele recupera apenas o nome; todo o resto está corrompido.

Quando eles representam os Checkpoints no mapa, a escala do problema fica mais clara. O primeiro Checkpoint, Earth, já aparece mais longe na rota do que Oshiro. Vladimir, no entanto, está muito mais distante e exigiria um desvio considerável da rota para ser alcançado. Rüdolf e Elijah não aparecem como alvos recuperáveis: seus t-signals estão desaparecidos e não são detectados pelo sistema.

Também entra a fascinação de Ismael pelo sistema de navegação: a rota não funciona como linha contínua no espaço, mas como uma rede de nós, vazamentos e conexões, onde certos pontos permitem atravessar para outros pontos dependendo do estado da nave. Ele começa a tratar aquilo como matemática de caos, informação, estados e otimização. Susan e Beatriz veem luzes de cores estranhas atravessando um corredor; o camera feed confirma as luzes, e Kallom diz que fenômenos assim podem acontecer, como o ser amarelo visto antes por Mike e Felix. No fim, Mike olha novamente o tempo restante. Depois de tudo que aconteceu no capítulo, passaram apenas cerca de cinco minutos.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

Mike monitors the exact time remaining until the RT-874 reaches Lucia while the crew experiences subjective temporal strangeness that the ship's records do not confirm as a fault. Ismael and Kallom-4000 recover the preserved navigation structure: five Checkpoints followed by return to Brains' Cage. The Checkpoints are Earth, The Reliquary, Rendezvous, The Vortex, and Akrelabium, each with only minimal corrupted mission phrases recovered. When represented on the map, Earth is already farther along the route than Oshiro; Vladimir is much farther away and would require a major route deviation; Rüdolf and Elijah are missing, with no detectable t-signals. Ismael begins interpreting the route as a nonlinear network of nodes, leaks, connections, states, chaos, information, and optimization rather than a continuous spatial line. Susan and Beatriz see strange colored lights in a corridor, confirmed by camera feed, and Kallom relates the phenomenon to previous anomalies such as the yellow being. The chapter ends with Mike realizing that only about five minutes have passed.

H. Open Problems

Decide whether the countdown to Lucia should be shown as exact numeric UI text or described through Mike's perception. Clarify whether Beatriz is physically present in this RT-874 interval or if the outline should adjust the witness pair. Define how much Kallom-4000 can explain about Checkpoints without recovering the full documents. Decide whether the strange colored lights foreshadow a specific later entity or remain a general cohesion artifact.

A. Title

Lucia

B. Chapter Function

This chapter reunites the crew with Lucia and demonstrates both the horror of altered existence and Lucia's quiet authority. Its function is to show Mike entering a strange local environment to reinforce Lucia's signal, reveal that Lucia has existed as a colored rectangular plate or surface, restore her to the RT-874, establish her as acting captain, and end by making her experience the reality-jump problem directly. This is also the first point in the book where the crew explicitly understands why Mike is usually the safest person to send outside the RT-874: the damaged ship was stabilized around him after the crash, making him the lowest-cost external vector while also exposing him most strongly to reality jumps.

C. Required Context Before Chapter

The RT-874 has been traveling toward Lucia under unstable time perception. The crew has recovered the five Checkpoint mission structure and understands that navigation, t-signals, and decohesion are behaving dangerously. Lucia is still missing, and the ship is close enough for Kallom-4000 to attempt recovery.

D. Character State at Chapter Start

Mike is tense but willing to expose himself to strange environments because he has the most practical experience with them. This chapter also clarifies that his suitability is structural, not heroic: after the crash, Kallom-4000 stabilized the damaged RT-874 around Mike, so the ship understands his body, t-signal, continuity limits, and return path better than it understands the others. Kallom-4000 is under pressure from the recovery attempt. The crew wants Lucia back, but the RT-874 cannot risk a full remote pull without someone strengthening the signal locally. Lucia begins the chapter isolated in an alien mode of existence, but returns lucid and mentally intact.

E. Chapter Description - Pre-Draft

O capítulo seguinte continua na RT-874. Eles finalmente chegam até Lucia, mas Mike não consegue ter certeza se a viagem durou semanas, meses ou anos subjetivos. A nave está próxima dela, e Kallom-4000 tenta puxá-la, mas a RT-874 começa a tremer, alarmes disparam, e aparece aviso de decohesion imminent. Kallom diz que não consegue recuperá-la remotamente porque isso exige poder computacional demais. A solução é alguém se aproximar diretamente do ponto onde Lucia está para reforçar o sinal. Só uma pessoa pode ir, para não colocar a RT-874 em risco.

É aqui que a explicação aparece pela primeira vez no livro: Mike é a opção menos perigosa porque, logo depois do crash, Kallom-4000 salvou a RT-874 otimizando a configuração danificada da nave ao redor dele. A nave não foi restaurada como um sistema neutro. Ela estava entrando em decohesion, com t-signals instáveis, tripulantes espalhados, sistemas incompatíveis e uma arquitetura interna quebrada. Kallom precisou estabilizá-la em torno do melhor anchor disponível naquele momento: Mike.

Por isso, a RT-874 danificada entende Mike melhor do que entende o resto da crew. O corpo dele, o t-signal, os limites de continuidade, os reality jumps e a relação dele com a nave foram absorvidos pelo modelo emergencial que Kallom construiu depois do crash. Mike não é especial por natureza e não é um chosen hero. Ele se tornou o lowest-cost external vector porque a nave quebrada foi recalibrada ao redor dele.

Quando alguém sai da RT-874, a nave precisa manter coesão entre o interior, o t-signal do tripulante, o ponto externo e o caminho de retorno. Com outros tripulantes, isso aumenta muito o risco de decohesion, porque a nave precisa sustentar uma relação menos estável com um corpo/t-signal menos integrado ao modelo pós-crash. Com Mike, o risco ainda existe, mas é menor: a nave já possui caminhos de compensação, previsão e reconciliação construídos em torno dele. O mesmo mecanismo explica o problema oposto: Mike sofre mais reality jumps porque muita instabilidade passa por ele como ponto de compensação.

Mike se voluntaria, mas a decisão não é tratada apenas como coragem. Kallom confirma que, nas condições atuais, Mike é a opção estruturalmente menos perigosa para a RT-874.

Mike aparece num mundo tridimensional extremamente colorido, dentro de túneis estreitos que parecem subaquáticos, com cores e padrões estranhos. Ele não sabe que corpo tem, não percebe corpo definido, mas consegue se mover como se estivesse nadando. Ele se comunica com a crew e diz que não faz ideia de onde está. Ele vê seres indefiníveis e chega a uma região com várias placas retangulares coloridas presas nas bordas do túnel. Kallom detecta que o t-signal de Lucia vem de uma dessas placas. Lucia é aquela placa. Mike fica próximo dela para Kallom mapear e puxar os dois, enquanto se pergunta se as outras placas também são consciências.

Kallom consegue puxar Mike e Lucia de volta. Mike retorna com a mesma roupa; Lucia retorna nua e encharcada. Eles a cobrem com um cobertor e tentam levá-la para a sick bay, mas ela está lúcida, sem dano mental, e se lembra de tudo: do crash, do desaparecimento, e de ter existido como uma placa. Ela diz que não era dor, sofrimento, prazer ou bem-estar; era outro modo de existência, como ser uma parede/superfície, onde o tempo não fazia sentido. Depois a crew recontextualiza Lucia sobre tudo, e ela assume como acting captain por ter a maior patente disponível. O ponto é mostrar que ela fala baixo, é reservada, quase tímida, e ainda assim possui autoridade total; até Ismael, que pareceria mais líder por parâmetros humanos, se submete ao julgamento dela.

Mais tarde, enquanto conversa com Mike sobre sistemas, Lucia desaparece de novo. Alarmes disparam, Kallom localiza Lucia numa região próxima, Felix manobra a RT-874 até lá, e Kallom consegue puxá-la de volta. Ela retorna como se nada tivesse acontecido e não percebeu interrupção nenhuma. A crew então explica a ela o problema dos reality jumps, e o capítulo termina aí.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

The RT-874 reaches Lucia after a journey whose subjective duration Mike cannot trust. Kallom-4000 cannot recover Lucia remotely without risking decohesion, so someone must enter the strange local environment and reinforce her signal. This chapter is the first place where the book explicitly explains why Mike is usually chosen for external transitions: after the crash, Kallom-4000 saved the RT-874 by optimizing the damaged ship around Mike as the best available anchor. The ship understands Mike's body, t-signal, continuity limits, reality jumps, and return path better than it understands the rest of the crew. Mike is therefore the lowest-cost external vector, not a chosen hero, while the same anchor role makes him suffer the most reality jumps. Mike enters a strange three-dimensional, tunnel-like, colorful environment to reinforce Lucia's signal locally. He discovers that Lucia's t-signal comes from one of several colored rectangular plates attached to the tunnel, meaning Lucia is existing as that surface. Kallom pulls Mike and Lucia back. Lucia returns naked, wet, lucid, and mentally intact, remembering the crash, disappearance, and the state of being a plate or surface outside ordinary pain, pleasure, suffering, or time. She is recontextualized and becomes acting captain because she has the highest available rank, demonstrating quiet but absolute authority over the crew. Later Lucia disappears again during a systems conversation with Mike, is recovered from a nearby region by Kallom after Felix maneuvers the RT-874, and returns without noticing any interruption. The crew explains the reality-jump problem to her.

H. Open Problems

Decide whether the other colored plates are definitely consciousnesses or only suggest that possibility. Clarify the exact visual language of Lucia-as-surface so it feels alien without becoming absurd. Define whether Lucia's second disappearance is inside the recoverable decohesion zone or a related local jump. Decide how much Lucia immediately understands about command, Kallom's limitations, and the remaining route after being recontextualized.

A. Title

Lucia / Fallback Operator / Unknown T-Signal

B. Chapter Function

This chapter establishes Lucia's command style after recovery, uses human Prif calibration to show syraki distance from human shame and intimacy, creates Ismael's fallback operator role, and redirects the RT-874 from the route to Oshiro toward an unknown distress t-signal.

C. Required Context Before Chapter

Lucia has been recovered from the plate/surface existence and has become acting captain. The crew understands the reality-jump problem, is moving toward Oshiro, and has already developed partial recovery procedures. Susan is active as Communications Operator, and Ismael appears unusually stable compared with the others.

D. Character State at Chapter Start

Lucia is lucid, authoritative, and still adapting to the human body as an operational interface. Mike is available as Systems Operator and the crew member most able to explain downgraded human embodiment. Ismael is functioning under Lucia's authority and is stable enough to be considered for broader emergency duties. Susan is attempting long-range contact with Oshiro while the RT-874 continues along the route.

E. Chapter Description - Pre-Draft

The chapter begins aboard the RT-874 after Lucia has been recovered and established as acting captain. Lucia asks Mike for help understanding the human body as a Prif interface. She is not used to the human form and wants to know how she can raise her Prif scale to reduce tension and improve operational stability. Mike explains this in a calm, almost scientific way: pleasure responses vary from person to person, but human bodies have common sensory zones and comfort mechanisms, including muscular relaxation, shoulder massage, warmth, touch, scalp stimulation, pressure, and other bodily responses. He also mentions genital pleasure technically, not seductively, as one of the stronger human mechanisms. Lucia receives this normally and thanks him.

The chapter shows clearly that syrakis do not carry the same human assumptions around body, space, shame, hierarchy, and intimacy. Lucia asks for practical demonstration, and Mike treats it as a real operational task. He first demonstrates ordinary muscular stimulation, including shoulders and upper back, then explains that some areas of the human body can produce unusual sensory responses even when humans do not always classify them as formally intimate. Lucia remains seated and cooperative. Mike asks her to raise her arms. She does so without embarrassment. Mike comes behind the chair, places his thumbs against her armpits, and applies careful pressure, showing her that the armpits can produce a distinct pleasurable or sensitive response in the human body. Lucia receives this as information, not as flirtation or invasion. The scene is not sexualized; it is a technical demonstration of a human sensory interface.

Ismael enters during this demonstration, while Lucia is seated with her arms raised and Mike is behind the chair touching her armpits with his thumbs. There is no embarrassment from anyone. Ismael does not stop, avert his eyes, make a joke, or interpret the scene as private. He reads it as human Prif calibration. Lucia remains acting captain, Mike remains Systems Operator, and Ismael remains Navigator. The hierarchy is not disrupted by bodily contact, because the contact has functional context, consent, and no coercive or humiliating meaning for anyone involved. This absence of human-style embarrassment is one of the central points of the scene.

Lucia then says she is curious to test the human feeling called love and asks if anyone can help. Mike, being closest and already helping her, volunteers. Lucia immediately experiences an intense human love toward him, likes the feeling, and then analyzes it technically. She asks whether such a feeling is used to increase bonding and crew efficiency. Ismael says yes, but not at the intensity she is currently experiencing, because the human brain is weak and can become distracted by possessiveness, jealousy, attachment loops, and inefficient emotional regulation. There is a lighter and more endemic form of affection that can improve cohesion without compromising efficiency.

With Kallom-4000's help, Lucia runs simulations using projected versions of the crew, not the actual crew members. These simulations test different levels of human love, bonding, affection, and crew cohesion under stress scenarios. When the level is too high, cohesion increases but efficiency drops because the projected crew wastes too much mental energy on emotional management, romantic entanglement, jealousy, and attachment complexity. When the level is too low, the crew remains more cognitively clean but cohesion drops, forcing them to rationalize cooperation too much. Lucia and Kallom-4000 establish a heuristic level: a light, endemic, distributed form of affection strong enough to improve bonding and stability, but not strong enough to dominate the weak human emotional architecture.

Lucia also gives direct operational orders. She orders Ismael to continue studying the strange navigational mathematics of the space-of-space, and she orders Mike to continue raising her Prif scale through shoulder stimulation while she analyzes data. Mike receives this order with the same seriousness with which Ismael receives his own. He does not treat it as a joke, flirtation, abuse, or humiliation. Within syraki logic, if the action does not produce suffering, aversion, coercion, or degradation in the one performing it, and if it improves operational stability, it can be a normal hierarchical order. The scene is meant to be uncomfortable to human readers because the syrakis treat embodied Prif maintenance as functional, not as human social theater.

During the same period, the RT-874 is moving toward Oshiro. Oshiro is farther away than Lucia was, but time seems to be passing more normally than during the earlier route. The reality jumps continue, sometimes worse and sometimes better. The crew has developed recovery procedures and usually manages to retrieve anyone affected. Only once did the ship need to leave the route more seriously to recover someone again, as happened with Susan. Ismael appears to be the only member not affected by reality jumps, or at least the only one with no detectable reality jump. Since detection is heuristic, no one can be fully sure whether he is truly unaffected or simply affected in a way that leaves no clear trace.

Because of this, Lucia creates an on-demand function for Ismael: fallback operator. Lucia chooses him because he appears to be the most stable member of the crew under current conditions. His task is to learn enough of every critical function aboard the RT-874 to operate the ship alone if the others become unavailable, displaced, cognitively compromised, or caught in reality jumps. He begins learning from everyone: systems from Mike and Lucia, navigation and maneuvering from Felix, diagnostics and technical procedures from Susan, emergency recovery and decohesion constraints from Kallom-4000, and any other relevant operational layer. The others cannot take this role because they are already immersed in their own critical functions.

Meanwhile, Susan keeps trying to establish long-range contact with Oshiro, using protocols similar to the ones that once worked with Ismael. Oshiro does not respond. Then Susan suddenly detects a signal through the radio-like interface, though they already understand that the device is not truly radio in the ordinary sense. The signal sounds like an SOS loop: someone repeatedly says they are lost and asks whether any vessel nearby can help them.

This creates immediate disorder aboard the RT-874. The crew gathers in the communication area and Kallom-4000 maps the source. The signal is not coming from Oshiro. It is a mysterious t-signal outside the direct route, positioned in a way that would require a triangular deviation: away from the path to Oshiro, toward the unknown signal, and then back toward Oshiro. Lucia asks Kallom-4000 to calculate whether they can investigate without causing decohesion. Kallom-4000 says the deviation is possible. It may increase the reality jumps and general instability, but it remains within survivable limits.

Lucia orders the deviation. The RT-874 begins moving toward the unknown signal while Susan continues trying to communicate with the source. At first there is no response, only the repeated distress loop. Around halfway through the deviation, the signal changes. A frightened voice finally comes through, no longer just repeating the message. The chapter ends with the voice asking:

"Hello? Hello... is anyone there?"

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

After Lucia becomes acting captain, she asks Mike to explain the human body as a Prif interface. Mike explains human sensory comfort, muscular relaxation, shoulder and upper-back massage, warmth, touch, scalp stimulation, pressure, armpit sensitivity, and genital pleasure technically rather than seductively. Lucia treats this as operational knowledge. The practical demonstration is deliberately nonsexual and shows syraki distance from human assumptions about body, shame, hierarchy, and intimacy: Lucia sits cooperatively, raises her arms when asked, and Mike stands behind the chair, places his thumbs against her armpits, and applies careful pressure to demonstrate that armpits can produce distinct pleasurable or sensitive responses in the human body. Ismael enters during the demonstration and shows no embarrassment; he reads the scene as human Prif calibration, while Lucia remains acting captain, Mike remains Systems Operator, and Ismael remains Navigator. Lucia tests intense human love toward Mike, then analyzes it with Ismael and Kallom-4000 as a bonding variable. Ismael explains that this intensity is inefficient for weak human brains because it can trigger possessiveness, jealousy, attachment loops, and emotional regulation overhead, while lighter endemic affection can improve cohesion. Simulations show that too much human love increases cohesion but harms efficiency through romantic entanglement and emotional overhead, while too little affection lowers cohesion. Lucia and Kallom establish a light, distributed affection heuristic for crew stability. Lucia orders Ismael to study the space-of-space navigation mathematics and orders Mike to continue Prif maintenance through shoulder stimulation while she analyzes data. The RT-874 continues toward Oshiro, who is farther away than Lucia; reality jumps continue under partial recovery procedures. Ismael appears uniquely stable, so Lucia assigns him the on-demand role of fallback operator, requiring him to learn enough of every critical function to run the RT-874 alone if others are displaced or compromised. Susan continues trying to contact Oshiro but instead detects an SOS-like loop through the radio-like interface from an unknown t-signal outside the direct route. Kallom confirms a survivable triangular deviation, and Lucia orders the RT-874 toward the unknown signal. Halfway through the deviation, the loop changes into a frightened voice asking whether anyone is there.

H. Open Problems

Decide how explicit the Prif calibration demonstration should be on the page while preserving its technical, non-seductive tone. Clarify whether Lucia's induced human love is a temporary calibration state, a controlled emotional test, or a longer-lasting adjustment. Define exactly how Ismael's fallback operator training is shown without slowing the chapter. Decide whether the unknown t-signal should be immediately identifiable to the reader or remain fully mysterious until the following chapter.

A. Title

KJH-444

B. Chapter Function

Make KJH-444 the first direct proof that RT-874 is not alone in the decohesion disaster. The chapter should turn rescue into contradiction: RT-874 reaches another omniship, speaks with a surviving crew, detects the vessel at the correct coordinates, and still cannot reach the beings who claim to be inside it. The core revelation is not ordinary distance, but coordinate resolution: two ships can occupy the same apparent point while remaining separated by a finer operational layer of reality.

C. Required Context Before Chapter

The RT-874 crew has recovered Lucia, established her as acting captain, and deviated from the route to Oshiro after Susan detects a strange distress loop. Susan is present as RT-874 Communications Operator and is the one trying to coordinate the contact. Oshiro has not yet been rescued. Kallom-4000 can interface with external ship systems, but the RT-874 remains decohesion-damaged and any high-computation rescue attempt can threaten its own stability.

D. Character State at Chapter Start

Primary focus character: Susan as Communications Operator, radio responder, and stabilizing voice during a broken transmission. Lucia acts as captain and authorizes risk. Kallom-4000 performs the technical reconstruction and alignment attempt. Mike, Felix, Ismael, and the rest of the active RT-874 crew witness the discovery. The KJH-444 speaker begins frightened but hopeful, believing rescue has arrived; the RT-874 crew begins with cautious hope and ends in helpless dread.

E. Chapter Description - Pre-Draft

RT-874 follows the broken distress transmission to the coordinates provided by the unknown speaker from KJH-444, an omniship belonging to Valtir & Blue, a rival corporation. The communication is unstable from the beginning, constantly breaking apart under interference, but Susan manages to keep enough contact to calm the man and confirm that RT-874 is moving toward them. Through fragmented exchanges, the crew learns that KJH-444 has also suffered a decohesion-related accident. Their crew originally had sixteen members. Five have already disappeared. The remaining crew is still aboard, at least from their own perspective, transmitting distress and waiting for rescue.

When RT-874 reaches the transmitted location, the Plotter confirms proximity. KJH-444 is there. The ship exists, occupies the expected coordinates, and appears operational enough to be detected. The man on the radio reacts with relief, believing rescue has arrived. But when RT-874 inspects the vessel, the contradiction becomes impossible to ignore: KJH-444 is active, damaged, and partially corrupted, but physically abandoned. There are no visible crew members, no bodies, and no direct signatures corresponding to the people speaking through the radio. The man insists that this makes no sense. They are inside the ship. RT-874 is inside the ship. Both crews are supposedly in the same place, yet neither can see the other.

RT-874 connects Kallom-4000 to KJH-444's degraded systems and begins extracting whatever can still be recovered: logs, mission files, technical documents, telemetry fragments, internal records, and any data that may explain what happened. Because KJH-444 belongs to a rival corporation, access requires credentials that RT-874 does not possess. Susan asks the man on the radio for authorization. Despite the corporate boundary, he gives them the password. The gesture reveals something fundamental about syrakis civilization: rivalry does not override the protection of conscious beings. In a survival emergency, withholding access for proprietary reasons would be morally grotesque.

Using the recovered documents and the live but unstable radio exchange, Kallom-4000 begins reconstructing the problem. RT-874 and KJH-444 are not separated by normal distance. They are effectively at the same coordinates, but not at the same coordinate resolution. The Plotter rounds their positions into apparent coincidence, but the actual location requires a much finer level of precision, as if the ships were both at "1.3" while the rescue requires something closer to "1.324102..." and beyond. They are close enough to communicate, close enough to detect each other, but not close enough to share the same operational layer of reality.

Kallom-4000 determines that a rescue attempt may be possible if RT-874 can calculate the exact coordinate refinement needed to align with KJH-444's crew. The calculation is far beyond ordinary navigation. Lucia authorizes Kallom-4000 to draw on RT-874's computational resources. The ship begins diverting power and processing capacity into the attempt, but the calculation immediately stresses RT-874's cohesion. The vessel starts to stutter, fracture, and pick at the edges of stability. Lucia orders the process pushed further, forcing the ship toward its maximum tolerance, but Kallom-4000 eventually stops the operation on safety grounds. Continuing would risk triggering complete decohesion of RT-874 itself.

The rescue fails. The man on the radio hears enough to understand that RT-874 is trying, and he thanks them for the effort, but frustration and fear break through the static. He realizes that RT-874 does not truly understand where it is. He begins to explain that this is not merely anomalous space, and that RT-874 should already know what kind of place they have entered. The transmission collapses precisely as he is about to clarify. His final explanation is lost in interference.

After the failed alignment attempt, KJH-444 vanishes from RT-874's Plotter. The ship disappears from their instruments as if it had never occupied the coordinates at all. Susan tries to reestablish contact. RT-874 repeats the call again and again. No answer comes back. The chapter ends with RT-874 calling into silence, having watched another crew disappear from immediate proximity without ever being able to reach them.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

KJH-444 is a Valtir & Blue omniship, a rival-corporation vessel similar enough to RT-874 for Kallom-4000 to interface with its degraded systems. Its crew originally had sixteen members; five had already disappeared before RT-874 arrived. KJH-444 is detected at the transmitted coordinates as real, active, damaged, and partially corrupted, but physically abandoned: no visible crew, no bodies, and no direct signatures matching the radio speaker or surviving crew. The speaker insists that he and the others are still inside the ship. The key technical idea is coordinate resolution: RT-874 and KJH-444 are apparently at the same coordinates, but not aligned at the finer operational precision required to share the same layer of reality. Susan obtains access credentials from the speaker despite corporate rivalry, establishing that syraki survival ethics override proprietary boundaries. Lucia authorizes a high-computation alignment attempt; Kallom stops it because continuing would risk complete RT-874 decohesion. The speaker nearly explains where they are, rejects the idea that it is merely anomalous space, and is cut off before clarifying. KJH-444 then vanishes from the Plotter, leaving RT-874 calling into silence.

H. Open Problems

Decide the name and voice texture of the KJH-444 speaker if the draft needs one. Decide how much of Valtir & Blue's corporate identity should be visible in the recovered documents. Preserve the interrupted distinction: the speaker knows this is not merely anomalous space, but the chapter must end before he names or explains the place.

A. Title

TUZ-66941 / Ukabkys Supply Chain

B. Chapter Function

Continue TUZ-66941's external investigation after the physical substrate evidence found in the Oskiparisis case. The chapter moves the investigation from damaged substrate, falsified maintenance status, and compromised supply-chain components into a direct inquiry on Ukabkys.

The chapter must establish that TUZ-66941 is no longer investigating Kymintus as an isolated anomaly. Other TUZ agents have identified additional entities with masked t-signals, false or misaligned identity structures, and recent supercycle work histories connected to one of the four major reality artistry megacorporations.

The chapter also introduces the first active operational response against TUZ-66941 after the Ukabkys lead. This response does not prove corporate guilt, does not establish criminal malice, and does not imply that ordinary syrakis are morally corrupt. Its function is narrower: it proves that the investigation has touched a monitored layer and that some chain of authorization can be used to obstruct an inquestor without producing an obvious human-style crime scene.

C. Required Context Before Chapter

TUZ-66941 has already investigated Kymintus, followed the trail through Oskiparisis, confirmed that Kymintus was not a normal syraki identity, and suffered an obstruction event that erased Oskiparisis from ordinary manifests.

After propagating the case through other TUZ agents, the investigation found physical substrate contradictions: damaged addresses, destroyed maintenance drones, falsified status boards, and supply-chain traces leading toward Ukabkys.

The reader should understand that TUZ-66941 is not reacting to KJH-444. KJH-444 is a local RT-874 event. This chapter continues TUZ-66941's independent institutional investigation through substrate, supply chain, t-signal masking, and concealed expeditionary losses.

The reader should also understand that syraki civilization is not criminal in the human sense. No local participant should be framed as malicious unless the evidence requires it. The danger comes from authorization chains, compartmentalization, information hazard protocols, and distributed coordination under severe ethical constraints.

D. Character State at Chapter Start

Primary focus entity: TUZ-66941.

Other relevant entities: Martyu-11, Sedfervor-3, additional remote TUZ agents, and unnamed protected individuals discovered by those TUZ agents.

TUZ-66941 is operating through a robotic six-armed body inside a spacecraft. In this chapter, unlike the earlier vessel-form scale, TUZ is literally piloting. This embodiment is functional, precise, and suited to investigation inside traffic-controlled industrial space.

TUZ-66941 is not emotional, frightened, angry, or personally offended by obstruction. It proceeds by evidence, Mandate, probability, authorization, and constraint. Its increasing concern is operational, not sentimental: the investigation is producing a pattern too distributed to remain local.

Martyu-11 is the legal representative of the Ukabkys company that manufactured, certified, or handled the equipment connected to the compromised maintenance chain. He uses an advanced biological, self-regenerating body, taller than TUZ's robotic body, with folded wings and no human resemblance. He receives TUZ properly and cooperates fully.

Sedfervor-3 is a syraki embodied as a spacecraft. He does not act from malice. He becomes involved through a formally valid but compartmentalized operational order.

E. Chapter Description - Pre-Draft

The chapter opens in orbit above Ukabkys. TUZ-66941 pilots a spacecraft through a robotic body with six arms, descending from space toward a moon with a thin atmosphere. Below, vast deserts, cities, traffic corridors, industrial complexes, and partially buried infrastructure move rapidly under the vessel.

While descending, TUZ processes reports from other TUZ agents. Those agents have found additional individuals beyond Kymintus who show related identity irregularities: masked t-signals, false or misaligned identity states, and post-supercycle anomalies. Some of these individuals believed themselves to be something other than what their substrate and signal analysis indicated. Unlike Kymintus, they have been placed under protective investigative observation so they cannot disappear before the Mandate reconstructs the pattern.

A preliminary commonality appears: the affected individuals worked in relatively recent supercycles for one of the four major megacorporations. This is not yet proof of collusion. At this stage it is only an unusual cross-case feature.

TUZ contacts traffic control. The exchange should resemble air-traffic procedure only in human-readable allegory: approach vector, authorization, corridor assignment, descent permission, sector transfer, and landing clearance. The actual protocol is posthuman, compressed, and administrative.

The spacecraft enters controlled atmospheric traffic. The sky contains freight vessels, passenger vessels, instrument-carrier vessels, small autonomous bodies, large industrial craft, and stranger shapes whose purposes are not immediately legible. TUZ follows the assigned approach, passes through surface traffic, and descends through a layer into a subterranean industrial sector.

The landing area is buried beneath the surface, like a lower city-layer under the moon's industrial skin. TUZ lands on a pad, leaves the spacecraft, and exits in the six-armed robotic body.

Martyu-11 receives TUZ. He is not robotic. His body is biological, self-regenerating, winged, and highly advanced. His wings remain folded. He is taller than TUZ's body and has no human structure. He receives the inquestor with full procedural respect, without fear, resentment, humiliation, or theatrical deference.

Martyu-11 leads TUZ through the facility. Inside are industrial robots, biological-bodied syrakis similar in broad category to Martyu-11, technical workers, readers, students, auditors, and maintenance specialists. The facility should read as normal, lawful, productive infrastructure, not as a hidden criminal site.

Before TUZ asks the central questions, Martyu-11 states that he has already reviewed the shipment records, maintenance histories, component certifications, accounting, and chain-of-custody documents. He found no anomaly. He opens the records to TUZ without resistance.

TUZ reviews the material. Martyu-11 is correct. The local company appears clean. The shipment is lawful. The accounts reconcile. The certification trail is valid. The replacement component entered the chain through proper procedure. The local records do not indicate fabrication, sabotage, or illegal concealment.

The first relevant anomaly is indirect. Several shipments and component lots originated from companies that are not the Ukabkys firm itself but subsidiaries connected upward to Valtir & Blue. This does not establish guilt. It shifts suspicion from the local manufacturer toward earlier layers of the supply chain.

TUZ leaves the meeting with Martyu-11. The conclusion at this stage is negative but important: Martyu-11 is not the local culprit, the facility is not visibly compromised, and the formal record is too correct to support a direct accusation.

TUZ returns to the spacecraft and departs. As the vessel rises into the controlled traffic environment, the chapter expands into a posthuman traffic sequence: freight traffic, passenger traffic, specialized craft, autonomous instruments, industrial carriers, and other vessels moving through layered corridors.

TUZ detects that one vessel is maintaining relation with its own course beyond normal traffic coincidence. TUZ performs controlled maneuvers to test whether the craft is following. The correlation persists. The pursuing vessel adjusts.

Before TUZ begins a full evasive procedure, interference enters the robotic body and the spacecraft control stack. TUZ detects progressive loss of control. Its maneuvers degrade. The interference is not ordinary mechanical failure. It is an active attempt to reach through the body-vessel interface.

The attacker attempts to extract the investigation topology: which TUZ agents are involved, which protected individuals have been identified, which hashes have been captured, which leads are under observation, and how far the Oskiparisis investigation has propagated.

TUZ attempts to block the extraction. It fails to do so completely. TUZ attempts to contact the Central Algorithm. That channel is blocked or degraded. TUZ preserves local evidentiary integrity and begins a counter-operation.

The attacking craft is not piloted by a passenger inside. The syraki is the vessel. The spacecraft is the embodied operational form of Sedfervor-3.

The conflict is not a human dogfight. It is a combined physical, algorithmic, authorization, and control battle inside live traffic. TUZ attempts to isolate the hostile vessel, seize its command layers, preserve evidence, and identify the entity. Sedfervor-3 attempts to complete the exfiltration, degrade TUZ's body-vessel control, and exit the encounter without leaving traceable origin.

The ships maneuver through traffic. TUZ diverts risk away from civilian vessels and industrial infrastructure. Sedfervor-3 does not act with sadism or reckless cruelty; the danger comes from the order's operational parameters and the fact that the encounter occurs inside active traffic space.

TUZ eventually captures control of Sedfervor-3's vessel-body. Before the entity's continuity can fully disconnect, TUZ captures an identity / continuity hash sufficient for evidentiary hold.

Sedfervor-3's conscious continuity disconnects from the vessel-body. The captured vessel remains under TUZ's control, but the entity is no longer embodied there.

At the same time, TUZ's original spacecraft loses control, strikes a wall or industrial barrier inside the traffic/egress structure, and is destroyed. TUZ survives in the captured vessel-body, preserving the hash and the evidence of the encounter.

The chapter ends with TUZ inside the captured spacecraft-body, its original vessel destroyed, and the evidence preserved but incomplete. The attacker escaped ordinary capture, but not before TUZ captured the hash needed for formal continuation.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

TUZ-66941 confirms that Kymintus was not an isolated case. Other TUZ agents have identified additional entities with masked t-signals or identity irregularities.

Those additional entities have been placed under protective investigative observation rather than punishment, imprisonment, or quarantine. The purpose is evidence preservation and prevention of disappearance, not coercion.

All identified cases share some connection to recent supercycle work for one of the four major megacorporations, but this is not yet proof of collusion.

Martyu-11 is introduced as the cooperative legal representative of the Ukabkys company connected to the compromised equipment chain. His facility appears lawful and clean. His records are opened fully and appear correct.

The Ukabkys local company is not incriminated. The relevant connection moves upward through shipments and component lots tied to subsidiaries connected to Valtir & Blue.

Sedfervor-3 attacks or obstructs TUZ through a formally structured operational event, but the chapter should not frame this as human-style malice.

TUZ captures Sedfervor-3's identity / continuity hash before Sedfervor-3 fully disconnects.

TUZ's original vessel is destroyed. TUZ remains inside the captured vessel-body.

H. Open Problems

Define the exact term for the temporary protective status applied to the additional masked individuals. Preferred candidates: protective investigative observation, evidentiary preservation, continuity preservation, or protective hold. Avoid "quarantine" unless the term is redefined away from punishment or disease logic.

Define the exact term for Sedfervor-3's captured identifier. Preferred candidates: continuity hash, identity hash, t-signal identity hash, or Mandate-valid identity hash.

Clarify how much of the exfiltration attempt succeeds. It should be serious enough to prove active response, but not enough to compromise the entire investigation.

Clarify whether the traffic control authority observes the encounter and what records remain.

Preserve the rule that syrakis are not criminals in the crude human sense. Sedfervor-3 must not be written as evil, sadistic, corrupt, or villainous.

A. Title

TUZ-66941 / Prismatic Core Pattern Analysis

B. Chapter Function

Continue directly from the Ukabkys obstruction event. The chapter must process Sedfervor-3 without turning him into a criminal villain, then move TUZ-66941 into the Prismatic Core to test the full Oskiparisis deletion dataset through an independent pattern-recognition specialist.

The function of the chapter is to take TUZ from multiple competing hypotheses to a narrow, disturbing suspicion: if the Oskiparisis deletion and related t-signal masking events were an attack, they were executed with such perfect integration into operational noise that even extremely powerful actors become insufficient explanations.

The chapter should end with TUZ-66941 considering the hypothesis that one megacorporation would not be enough. The only hypothesis that preserves the data may be coordination among all four major megacorporations. This is not yet legal proof and not yet a moral accusation. It is an investigative threshold.

C. Required Context Before Chapter

TUZ has returned from the encounter with Sedfervor-3 in possession of the captured vessel-body and Sedfervor-3's identity / continuity hash.

The original TUZ vessel was destroyed during the encounter. The investigation preserved evidence but did not capture the full operational origin of the obstruction.

The reader should already know that TUZ has several hypotheses: a local Ukabkys actor, a transport company, a Valtir & Blue subsidiary, another powerful corporation, a High Echelon individual, an old protocol, a corrupted chain of authorization, or an unknown actor using legitimate infrastructure.

At this point TUZ does not yet suspect the four megacorporations as the primary explanation. That suspicion must emerge at the end of this chapter.

D. Character State at Chapter Start

Primary focus entity: TUZ-66941.

Other relevant entities: Sedfervor-3, Vanselia, Central Algorithm authorization mechanisms, and indirect reports from other TUZ agents.

TUZ-66941 remains precise, procedural, non-emotional, and Mandate-bound. It does not punish. It does not threaten. It does not coerce. It distinguishes between evidence, suspicion, legal actionability, and moral culpability.

Sedfervor-3 is not surprised that TUZ captured the hash. He understands that an evidentiary hold may follow. He does not behave like a defeated criminal. He cooperates because the hold is legitimate, the Mandate is valid, and he recognizes that something may have used his chain of authorization.

Vanselia is a syraki in the Prismatic Core, famous for pattern recognition across massive datasets. He has won competitions, solved large-scale pattern problems, and is trusted as a specialist in distinguishing true structure from noise. He does not know the corporate context of the investigation before the analysis.

E. Chapter Description - Pre-Draft

The chapter opens after the Ukabkys traffic incident. TUZ-66941 has captured Sedfervor-3's identity / continuity hash before Sedfervor-3's conscious continuity fully escaped the seized vessel-body.

TUZ sends a formal request to the Central Algorithm for an evidentiary hold on the entity identified by that hash. The request is not imprisonment, punishment, or coercive detention. It is a temporary preservation measure justified by the obstruction event, the attempted extraction of investigation topology, and the risk of evidentiary disappearance.

The request is approved.

TUZ and Sedfervor-3 appear in a neutral procedural environment. The space may be represented as a completely white world or chamber, not because the real procedure is visually simple, but because the interface is stripped of irrelevant context.

Sedfervor-3 is not surprised. He knows his hash was captured. He understands the legitimacy of the hold.

TUZ asks who Sedfervor-3 works for. Sedfervor-3 answers: an executive transport company. TUZ inspects the statement. The claim is true. Employment records, operational history, authorization chain, vessel registration, recent tasks, and transport credentials all match.

Sedfervor-3 explains that he received an encrypted operational order from a superior chain. The order was valid within his authorization environment, compartmentalized, and not interpretable by him as an attack against a Central Algorithm inquestor. He knew the task parameters but not the full investigative significance of what he was being used to do.

TUZ verifies the claim. The records match. Sedfervor-3 is not the origin point. He is a vector. His company is not immediately incriminated. The order chain is formally legitimate but operationally suspicious.

Sedfervor-3 cooperates. He does not plead, panic, or posture. He wants the inquestor to discover what happened, because he recognizes that his own obedience to a valid chain may have been instrumentalized.

TUZ thanks Sedfervor-3 for the information and releases him from the hold once preservation requirements are satisfied. The release reinforces syraki ethics: TUZ does not detain a conscious entity when the evidentiary need no longer justifies it.

TUZ then reviews the available hypotheses. The data still allow many possible explanations: a local company, a transport-chain actor, a Valtir & Blue subsidiary, a different megacorporation, a powerful private figure, a High Echelon structure, a legacy containment protocol, or an unknown network using legitimate authorization channels.

TUZ does not yet conclude that the four megacorporations are involved.

To test the data without biasing the analyst, TUZ travels to the Prismatic Core.

The Prismatic Core must be represented allegorically. It is not a human capital, office, palace, or laboratory. It is a highly complex multidimensional reality of the Complex, and any human-readable scene is only an interface reduction.

The human-readable allegory shows Vanselia in a beautiful room, reclining among colored flowers, pillows, and refined sensory structures. Vanselia's body is multidimensional in implication but represented as a highly sensitive, pleasure-attuned form. Around Vanselia are three female-coded syrakis or sirex figures participating in care and sensory support: one feeds Vanselia, one moves fingers through Vanselia's hair, and one massages Vanselia. This is not servitude in the human degraded sense and not a harem image. It is an allegory of high-pleasure cognitive stabilization inside syraki culture.

TUZ explains the constraints. Vanselia may inspect the dataset only during the conversation. After the conversation, Vanselia will forget the confidential data because they belong to an active Central Algorithm investigation.

Vanselia accepts without difficulty.

TUZ gives Vanselia the dataset collected by the distributed TUZ investigation after Oskiparisis. The dataset includes the chain of events required to delete or remove Oskiparisis from effective traceability: drone incidents, supply-chain irregularities, falsified statuses, maintenance events, component replacements, administrative records, routing noise, timing coincidences, substrate-address movement, and many other microevents. The dataset is enormous. It contains millions of events.

TUZ does not tell Vanselia that the suspected paths may connect to megacorporations. TUZ does not tell Vanselia which companies are under consideration. Vanselia receives the data as a pattern-recognition problem, not as a corporate accusation.

Vanselia runs several approaches. He tests clustering. He tests causal-path compression. He tests source attribution. He tests supply-chain correlation. He tests temporal alignment. He tests maintenance-dependency patterns. He tests administrative anomaly detection. He tests signature extraction. He tests event-probability divergence. He tests whether the data contain hidden regularity under ordinary noise.

No approach produces a usable pattern.

Vanselia finds no corporate signature, no authorial cluster, no obvious anomaly, no repeating hand, no single-source deformation, no narrow operational fingerprint. Every event can be read as ordinary operational noise: a short circuit here, a delayed maintenance process there, a component replacement elsewhere, a legitimate authorization, a normal checksum, a plausible traffic rerouting, a routine administrative update.

The conclusion is not that nothing happened.

Vanselia states the technical conclusion: if the dataset represents an attack, then the attack was executed with an operational model so precise that the intervention entered the world as plausible noise. Whoever did it did not merely hide a pattern. They shaped the event chain so that pattern-recognition itself would find only normality.

This does not give TUZ legal proof. It removes easier explanations.

If a local company had done it, there should be local asymmetry.

If a transport company had done it, there should be transport-chain distortion.

If one subsidiary had done it, there should be corporate clustering.

If a powerful private actor had done it, there should be authorization stress.

If one megacorporation had done it alone, there should be imbalance across domains.

But Vanselia found none of that.

TUZ understands the problem. The data are suspicious because they are too well integrated into normal operation. The attack, if it was an attack, does not look like an attack. It looks like the Complex functioning.

The chapter ends with TUZ looking toward an immense consciousness-structure inside the Prismatic Core. The structure is not literally a building, but the human-readable allegory presents it as something like a building because no human framework can represent its real form. It was created jointly by the four megacorporations and stands as a symbol of their loyalty to the Complex.

TUZ has not proven anything. It cannot act legally against the corporations. It cannot accuse them. It cannot break ethical boundaries on suspicion alone.

But the hypothesis changes.

A single megacorporation would not be sufficient.

The remaining possibility is structurally absurd and, for that reason, more compatible with the data than any smaller explanation.

What if it was not one megacorporation?

What if it was all four?

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

Sedfervor-3 is not morally framed as a criminal. He acted through a formally valid, compartmentalized operational chain and cooperates once held under proper evidentiary authority.

TUZ captures and uses Sedfervor-3's identity / continuity hash for an evidentiary hold, not punishment or imprisonment.

Sedfervor-3 works for an executive transport company. His records are true. His company is not immediately proven culpable.

TUZ verifies that the order chain is legitimate in form but suspicious in effect.

Vanselia is introduced as a Prismatic Core pattern-recognition specialist. He does not know the corporate context and is only given the active-investigation dataset for the duration of the conversation.

The Prismatic Core is represented allegorically because its real form is multidimensional and not human-comprehensible.

Vanselia cannot detect a pattern despite multiple approaches. This failure becomes the key finding.

The dataset appears perfectly embedded in ordinary operational noise. If the Oskiparisis deletion was an attack, it was executed by someone or something with an extremely precise model of the operational world.

TUZ realizes that multiple smaller hypotheses become weak because they should have left detectable asymmetries.

TUZ ends the chapter with a high-level suspicion that even one megacorporation may not be sufficient to explain the attack. The chapter closes on the possibility that all four megacorporations may be involved.

This is suspicion, not legal proof.

H. Open Problems

Decide whether Vanselia forgets the data through voluntary memory pruning, temporary sealed access, or a Central Algorithm-mediated confidentiality procedure.

Define the exact name of the Prismatic Core's four-corporation consciousness-structure.

Clarify whether this chapter fully satisfies the Chronological 0055 hit or only sets up the final proof of 0055. If it satisfies 0055, the wording should make TUZ's discovery stronger. If it only prepares 0055, preserve the ending as suspicion rather than conclusion.

Clarify whether the three female-coded sirex around Vanselia are individuals, aspects of the Prismatic Core interface, or voluntarily embodied participants in Vanselia's cognitive environment.

Preserve the distinction between suspicion and actionable legal proof. TUZ may reach a high-probability hypothesis, but cannot act against the corporations without Mandate-valid evidence.

A. Title

RT-874 / KJH-444 Logs / Six Minutes

B. Chapter Function

Show the immediate aftermath of the KJH-444 encounter from inside the RT-874.

The chapter has four main functions.

First, it shows that Mike's reality jumps are becoming stranger and harder to reconcile with normal RUN boundaries. Mike briefly appears inside a private, posthuman, encrypted reality belonging to another being, a place he should not be able to enter under any ordinary model.

Second, it processes the data recovered from the KJH-444: logs, mission files, mapped locations, telemetry, and black box material. These records show that the KJH-444 was not always in crisis. Its failure began during the mission after encountering an anomaly, which caused computational demand to rise sharply, cohesion maintenance to degrade, and crew members to disappear.

Third, it reveals that the RT-874 maintains not only physical habitability but mental habitability. Kallom-4000 must temporarily reduce the emotional/cognitive stabilization layer supporting the crew, causing a six-minute collapse of emotional control.

Fourth, it ends with an unknown approaching signal that cannot be classified. The RT-874 survives the encounter by using q-probes as bait, but no one understands what the signal was.

C. Required Context Before Chapter

This chapter follows Chapter 23 - KJH-444.

The RT-874 has encountered the KJH-444, an apparently abandoned but active Valtir & Blue omniship whose surviving speaker insisted that the crew was still inside it. Kallom-4000 accessed the KJH-444's degraded systems using credentials provided by the speaker and recovered logs, mission files, telemetry, internal records, mapped locations, and black box data before the KJH-444 vanished from the Plotter.

The crew has failed to rescue the KJH-444 survivors. The event has established that the RT-874 is not alone, but it has not explained where they are or what kind of region they have entered.

The RT-874 is still moving toward Oshiro, who remains several days away. Susan continues attempting contact.

D. Character State at Chapter Start

Mike is increasingly affected by reality jumps. His jumps no longer appear limited to external worlds or unstable local environments. They can place him inside domains that should be inaccessible.

Lucia remains acting captain. She is functional, direct, and focused on maintaining operational discipline after the KJH-444 failure.

Susan continues communication attempts, especially toward Oshiro, but receives no response.

Kallom-4000 is processing the KJH-444 records while maintaining the RT-874's cohesion, route, internal environment, crew regulation, and navigation through unstable regions.

The crew is functioning, but their stability depends more heavily on Kallom-4000 than they fully understood before this chapter.

E. Chapter Description - Pre-Draft

The chapter opens with Mike narrating a strange reality jump.

This jump does not take him into a battlefield, a desert, an alien environment, or a symbolic reality. It places him inside a private posthuman world: cybernetic, beautiful, advanced, and clearly belonging to another being. The reality is fully encrypted and private. Under ordinary conditions, no outside entity should be able to enter it.

The being who owns or inhabits the world detects Mike's presence. The being understands immediately that Mike should not be there. The intrusion is not merely rude or unexpected; it is functionally impossible. The world's encryption should make unauthorized entry less likely than finding a specific subatomic particle in an arbitrary galaxy.

The being asks Mike how he entered.

Mike cannot answer. He did not choose to enter. The jump happened to him.

While they are still speaking, Mike disappears again and returns to the RT-874.

Mike later explains the event to the crew. The incident strengthens the hypothesis that the RT-874 may be moving through regions of the Complex, RUN-space, or some internal topology connected to private realities. But even that hypothesis is not enough. Moving through the Complex should not permit entry into a private encrypted world. The event suggests that the RT-874 is producing or suffering impossible intersections between domains that should remain separated.

The chapter then shifts to the KJH-444 data.

The RT-874 has imported partial records from the KJH-444: mission files, logs, mapped regions, telemetry, technical fragments, and black box material. The data are incomplete, but enough remains to reconstruct a basic sequence.

The KJH-444 did not begin its mission in a collapsed state. For a period, the mission appeared to proceed normally.

The crisis began in the middle of the mission after the KJH-444 encountered an anomaly.

After that encounter, computational demand rose sharply. The ship began routing more and more power into maintaining cohesion. Its ability to sustain a stable operational state degraded. Crew members began to disappear. The distress signal was activated during this collapse phase.

This parallels the RT-874's condition but does not duplicate it. The RT-874's story began after the crash. The KJH-444 shows a similar failure emerging mid-mission, after contact with an anomaly.

The data recovered from the KJH-444 also include several mapped locations and route fragments. These do not provide a full explanation, but they expand the crew's sense that the region they are moving through is not empty, not unique, and not safe.

Susan continues attempting communication with Oshiro. No response arrives. Oshiro remains several days away.

During this ongoing analysis, Kallom-4000 informs Lucia that the RT-874 is about to pass through a specific region requiring unusually intense computation. For a few minutes, Kallom-4000 will need to route additional processing power into navigation, cohesion preservation, and route calculation.

Lucia asks for alternatives.

Kallom-4000 explains that an alternate route is possible but carries a significantly higher risk of severe decohesion or worse long-term instability. The direct passage is dangerous but brief.

Kallom-4000 warns that, to make the passage, it must temporarily reduce part of the system that keeps the crew's human brains emotionally regulated.

Mike later compares this to ancient human spacecraft. Human spacecraft had to maintain oxygen, atmospheric pressure, temperature, gravity, and radiation protection because human bodies could not survive without those artificial conditions. The RT-874 must maintain an equivalent mental environment. The crew are syrakis, but they are operating through human bodies and human brains inside an ontologically unstable vessel. They do not merely need air, food, or temperature. They need emotional and cognitive stabilization.

Lucia authorizes the passage.

Kallom-4000 tells the crew to prepare.

The RT-874 enters the region.

The ship begins to shake as if passing through turbulence or under attack. Lights flicker. Some systems cut out. Objects fall from surfaces. Sparks appear. Minor explosions or sharp bursts occur in local systems. The bridge and nearby compartments seem to lose their ordinary reliability.

At the same time, the emotional regulation layer drops.

The crew collapses.

They do not become merely anxious. They enter sudden ontological terror. Members fall to their knees, scream, cry, strike walls, scratch themselves, cling to one another, push each other away, beg for help, and lose all operational decorum. Some react with panic, some with aggression, some with helpless pleading. The RT-874, which had seemed disciplined and controlled, becomes a chamber of human emotional collapse.

The collapse lasts approximately six minutes.

During those six minutes, the crew experiences the situation without the artificial emotional support that had kept them functional. Their minds are exposed to the weight of decohesion, reality jumps, isolation, lost crew, failed rescue, the KJH-444, and the possibility that the space around them cannot be understood.

Kallom-4000 completes the required calculations.

The stabilization layer returns.

The effect is immediate and disturbing. The crew regain control too quickly for it to be normal recovery. Lucia rises as if the collapse has ended by switch, not by psychological healing. She orders everyone back to their posts and commands full diagnostic checks.

The crew obeys immediately. They return to function. They report, inspect, verify, and resume their roles.

The ship also restores. Lights stabilize. Objects that fell return to their proper places. Local damage disappears or is corrected. The interior configuration returns to coherence. It becomes clear that the RT-874's physical order and the crew's emotional order are part of the same broader life-support system.

Diagnostics report no lasting damage. Systems appear correct. The ship is intact. The event left no conventional wreckage.

The crew understands that what happened was not ordinary damage. It was a temporary exposure of the support layers that normally keep both ship and crew coherent.

Several days after the six-minute event, while still traveling toward Oshiro and while Susan continues failing to establish contact, Kallom-4000 reports something extremely strange.

Lucia orders everyone back to their posts.

The Plotter shows a signal approaching the RT-874 very quickly.

Kallom-4000 attempts classification. It is not a t-signal. It is not a known vessel. It is not a known tissue. It is not a distress signal. It is not an ordinary object. The ship cannot determine what it is.

As the signal approaches, the RT-874 begins to tremble in an unusual way.

Kallom-4000 informs Lucia that the RT-874 has q-probes. These are remote probes normally used for distant exploration, testing, measuring, and indirect interaction. They are not fully functional because Kallom-4000 still lacks access to the Main Database, but the cargo manifest indicates approximately three hundred units aboard.

Kallom-4000 proposes using the q-probes as bait or diversion.

Lucia goes to the storage area. The probes are held in boxes or technical compartments: black technological spheres, inactive but deployable under limited control.

Lucia authorizes Kallom-4000 to transport and deploy them.

The first q-probe is launched. The approaching signal does not change course.

The RT-874 continues shaking.

Two more q-probes are launched. This produces a small effect. The signal changes relation slightly but keeps approaching.

Three additional q-probes are launched.

This time the signal diverts. It turns away from the RT-874 and moves toward the probes.

The probes remain detectable. The approaching thing does not collide with them in a conventional way. It moves toward them, then disappears from detection. The RT-874 loses the signal.

No one knows what happened. Kallom-4000 cannot classify the phenomenon.

The chapter ends with Mike reflecting that the RT-874 survived the encounter without understanding it. They did not defeat the thing. They did not identify it. They only diverted it long enough for it to vanish.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

Mike experiences a reality jump into a private encrypted posthuman world, proving that the jumps can violate domains that should be inaccessible.

The owner of that world detects Mike and asks how he entered. Mike does not know. Mike disappears before the conversation can continue.

The KJH-444 records show that its crisis began mid-mission after encountering an anomaly.

The KJH-444 suffered rising computational demand, cohesion degradation, crew disappearance, and activation of a distress signal.

The RT-874 continues toward Oshiro. Susan still cannot contact him.

Kallom-4000 reveals that the RT-874 maintains a mental/emotional life-support layer for the crew.

For approximately six minutes, Kallom-4000 reduces this layer to route computation through a dangerous region.

The crew suffers a severe, sudden emotional collapse. The ship also appears unstable.

After Kallom-4000 restores the layer, both crew and ship return to normal too quickly, showing that stability is actively maintained.

Later, an unknown signal approaches the RT-874 at high speed.

The RT-874 uses q-probes as bait or diversion.

The unknown signal diverts toward the probes and disappears.

Kallom-4000 cannot classify what the signal was.

H. Open Problems

Define the final technical term for the emotional/cognitive stabilization layer maintained by Kallom-4000.

Define whether the private encrypted posthuman world belongs to a named syraki or remains anonymous.

Define whether the q-probes should remain written as "q-probes" or "Q-probes."

Define whether any of the q-probes are lost, altered, or merely remain behind after the signal disappears.

Define how much of the KJH-444 black box can be interpreted before Oshiro is found.

A. Title

Oshiro I

B. Chapter Function

Begin the Oshiro recovery sequence without completing it.

The chapter's function is to send Mike and Lucia outside the RT-874 to investigate Oshiro's unresolved signal, establish why direct retrieval is impossible, explain why Lucia accompanies Mike instead of Felix, introduce the world where Oshiro is trapped, and reveal the alien outpost inside the partially submerged pyramid.

The chapter must end before Oshiro is found. Its final discovery is the inactive portal hidden on the pyramid's upper terrace.

C. Required Context Before Chapter

The RT-874 is traveling toward Oshiro's location after the events involving the KJH-444, the KJH-444 logs, the six-minute emotional collapse, and the q-probe diversion event.

Susan has been attempting to communicate with Oshiro but has not received a response.

Kallom-4000 can detect that Oshiro's signal is in the region but cannot establish a reliable lock-on.

The crew understands that blind retrieval is dangerous. A failed extraction could worsen decohesion or bring something into the RT-874 that only appears to be Oshiro: a wrong fragment, corrupted t-signal, anomalous structure, foreign entity, or misresolved object.

Mike is normally the safest crew member to send outside because Kallom-4000 optimized the damaged RT-874 around him after the crash.

Lucia is acting captain.

Felix is the Pilot and is essential to the RT-874's survival.

D. Character State at Chapter Start

Mike volunteers to go outside because he knows he is the least dangerous external vector for the ship.

Felix also volunteers, but Lucia refuses.

Lucia explains the operational redundancy logic in this chapter. Felix cannot go because Pilot is too critical and depends on instinctive skill, embodied experience, and immediate ship-reading that Kallom-4000 cannot fully replace under degraded conditions. Systems Operator is also important, but it has more redundancy with Mike and Kallom-4000. Therefore Lucia can accompany Mike with less structural risk to the RT-874 than Felix.

This decision also has an ethical and affective dimension. Lucia could send Mike alone, but she does not treat him as a disposable tool. Syraki command is not domination. Mike is crew, consciousness, and responsibility. Lucia calculates the safest structure and goes with him because leaving him alone in an unstable recovery field would be tactically and ethically inferior.

Lucia leaves command of the RT-874 to Ismael.

Kallom-4000 remains in contact, though its readings are limited by the region's resolution problems.

Oshiro is not encountered in this chapter.

E. Chapter Description - Pre-Draft

The RT-874 reaches the region where Oshiro's signal should be located.

Kallom-4000 reports that the recovery is unusually difficult. It cannot establish a clean lock-on. The signal exists, but its resolution is unstable. Pulling directly from the ship is too dangerous.

Lucia asks for risk categories.

Kallom-4000 explains that the danger is not only decohesion. A failed retrieval might bring the wrong thing into the RT-874. In this region, the ship cannot guarantee that a direct extraction would isolate Oshiro from whatever shares, distorts, masks, or contaminates the same apparent coordinates.

Mike volunteers to go.

Felix also volunteers.

Lucia refuses Felix. She explains that Pilot is too critical. Felix's ability is not merely a formal role that Kallom-4000 can replace; much of it is instinctive, embodied, and dependent on his direct relation to the ship's motion and state. Losing Felix or compromising him would endanger the RT-874 more than losing most other functions.

Lucia chooses to accompany Mike herself. Systems Operator remains essential, but there is greater redundancy with Mike and Kallom-4000. If Lucia leaves the ship, the RT-874 retains more recoverable operational capacity than it would if Felix left.

Lucia leaves command to Ismael.

Mike and Lucia transition out.

They arrive in a world that is anthropomorphic enough to be legible to humans but alien in color, scale, and atmosphere.

The sky is pale beige. Purple clouds move or hang in the distance. Mike and Lucia stand inside a dense forest. The trees are strange, extremely tall, and packed closely enough to make the space feel enclosed. Everything is larger than expected.

The world is quiet. There is flora everywhere, but very little visible fauna. There are no birds. There is almost no animal sound. Sometimes they hear leaves moving, but even that sounds wrong.

The life in the forest seems to hide from them.

At one point Mike sees a small monkey-like creature observing them. It is curious but afraid. When it notices that Mike has noticed it, it runs and hides.

Mike and Lucia continue moving through the forest. They remain in contact with Kallom-4000, but Kallom can only give approximate guidance. Oshiro's signal is somewhere in the region, not locked to a precise point.

The forest eventually ends.

Beyond it is a vast blue body of water. It may first read as a lake, but its scale and depth quickly make that label feel insufficient. In the center rises the top of a pyramid-like structure, similar in rough human-readable form to a Mesoamerican stepped pyramid, but not actually human. Most of it is submerged. Only the upper portion breaks the surface.

The structure appears artificial.

Mike and Lucia ask Kallom-4000 whether it can transport them closer to the pyramid, specifically to the exposed exterior path near the top.

Kallom calculates. The operation is difficult and risky. A miscalculation could place them in the water, inside the structure, under the waterline, or in another lethal or unrecoverable position. But Kallom can produce a heuristic solution with acceptable probability.

Mike and Lucia approve.

Kallom executes the transport.

They appear successfully on the exposed exterior path of the pyramid.

The path is wide. Everything about the structure is too large. The pyramid's surface falls away into the immense body of water. There is no parapet.

Mike and Lucia begin walking along the side of the pyramid. Looking over the edge produces an immediate physical discomfort. The water descends far below them. The depth is unreadable. The blue surface becomes darker in the depths, and the scale gives a strong thalassophobic effect.

The fear is not only of falling. It is the sense that something could rise from below, or that the water contains a volume too large to understand.

Lucia notices the risk and moves away from the edge. Mike follows. They keep closer to the inner side of the path.

They reach an entrance area connected to an enormous moon pool.

The moon pool is outside or partly open to the exterior structure. It is technological, huge, and built at a scale that suggests it was designed for something very large to dock, enter, or emerge. It feels large enough for a massive submarine-like vessel, though it is not human technology.

A staircase descends toward the moon pool. Part of the stairway becomes submerged. At the lower level, there is glass or a transparent barrier, and beyond it they can see the dark water outside. The external door or gate connecting the moon pool to the ocean is open. Through the barrier, they see the lower darkness of the sea.

Before entering the pyramid proper, Mike and Lucia observe movement in the water.

Four large aquatic beings approach. Three appear to belong to the same species. They are roughly orca-sized or larger, built for predation. The fourth is different: a large cephalopod-like animal with tentacles.

The three predators attack the cephalopod-like creature.

Mike and Lucia watch as the predators tear it apart, ripping tentacles away and feeding on it. The mutilated remains begin to sink. The three predators eventually swim away.

Kallom-4000 reports that, based on the readings it can obtain, the ocean appears to sustain an extremely high predation density. The local marine ecology is violent. Predation is not incidental; it appears central to the biosphere.

This confirms that the fear of the water is not irrational. Falling into it would be dangerous for reasons beyond drowning.

Mike and Lucia continue from the moon pool toward an internal entrance into the pyramid.

Inside, the structure changes from monumental exterior to alien technological interior.

The outpost appears functional, but no one is visible.

The architecture is not human and not syraki. It belongs to another civilization. Mike and Lucia encounter consoles, surfaces, wall structures, technological panels, holographic elements, strange characters, and systems that seem active or dormant-but-ready. The space feels operational rather than ruined.

They are fascinated but cautious.

Lucia contacts Kallom-4000 and asks whether it can interface with the alien systems or download information.

Kallom attempts limited access.

It can touch the systems superficially. It can detect that there is data. The volume and structure of the data are enormous. The problem is not simple storage. The RT-874 may be able to store fragments in raw form, but fully ingesting, indexing, decoding, normalizing, and making the information operationally available would require too much computation and coherence maintenance.

In the RT-874's current state, attempting to integrate the dataset could push the ship toward decohesion.

Kallom-4000 refuses full ingestion.

Mike and Lucia continue investigating with limited assistance. They infer that the structure is an outpost: not a city, not a temple, not a simple ruin, not a ship. It is a limited but advanced installation, connected to the ocean, equipped with active systems, and built for some kind of monitoring, passage, study, or operation.

At this stage, the most plausible hypothesis is that the outpost relates to the violent marine ecology. The moon pool, the scale, the ocean-facing infrastructure, and the predatory biosphere all support the idea that it may have been used to observe, study, access, or interact with the sea and its organisms.

They still cannot locate Oshiro precisely.

Mike and Lucia eventually find stairs or an internal path leading upward.

They climb to the upper terrace of the pyramid.

The top is broad and flat, exposed beneath the pale beige sky. From a distance, this region had looked empty. Up close, they see that part of the upper structure is recessed into an artificial cave-like enclosure or protected cut within the pyramid's body.

Inside that hidden recess is a portal.

It is inactive.

The discovery changes the interpretation of the outpost. If the structure were only a marine observation or ocean-interface station, the portal would be difficult to explain. It suggests transit, transfer, arrival, evacuation, communication, or connection to another domain.

Kallom-4000 cannot classify the portal immediately.

Oshiro is still not found.

The chapter ends with Mike and Lucia on the upper terrace, under the beige sky, facing the inactive portal and understanding that the outpost is stranger than their current hypothesis can explain.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

The RT-874 reaches Oshiro's region but cannot establish a reliable lock-on.

Direct retrieval is considered too dangerous because it may worsen decohesion or bring the wrong thing aboard.

Mike volunteers to go outside.

Felix volunteers but Lucia refuses because Pilot is too critical and too dependent on irreplaceable instinctive skill.

Lucia explains that Systems Operator has more redundancy with Mike and Kallom-4000, so she can accompany Mike with lower structural risk.

Lucia leaves Ismael in command.

Mike and Lucia enter a world with a pale beige sky, purple clouds, dense enormous forest, little visible fauna, and a strange monkey-like animal that hides from them.

They find a vast blue body of water and a partially submerged pyramid-like artificial structure.

Kallom-4000 transports them to the exposed path of the pyramid using a risky heuristic calculation.

The pyramid's exterior produces a strong thalassophobic effect because of the huge water depth, lack of parapet, and unknown marine environment.

They find a gigantic technological moon pool connected to the ocean.

They observe three large aquatic predators kill and eat a large tentacled creature.

Kallom-4000 reports that the local ocean has extremely high predation density.

Inside the pyramid, they find a functional alien technological outpost, not human and not syraki.

Kallom-4000 can access the alien systems superficially but cannot ingest the data without risking decohesion due to the computation/coherence cost of integration.

Mike and Lucia infer that the structure is an outpost, possibly related to the ocean or marine biosphere.

On the upper terrace, they find an inactive portal hidden in an artificial recess.

They do not find Oshiro in this chapter.

H. Open Problems

Define final alien civilization terminology, if any.

Define whether the world is natural, RUN-like, possibility-space, or unresolved at this stage.

Define whether the monkey-like creature is relevant later or only an atmospheric marker.

Define whether the aquatic predators have any future significance.

Define whether the portal is connected to Oshiro's location or only to the outpost's deeper function.

Define how much alien data Kallom-4000 can safely sample before refusing full ingestion.

A. Title

Oshiro II

B. Chapter Function

Continue the Oshiro recovery sequence after Mike and Lucia discover the inactive portal in the alien outpost.

The chapter's function is to transform the recovery problem from a search inside the outpost into a dangerous attempt to approach Oshiro through the surrounding marine ecology.

The chapter must establish that Oshiro's signal is no longer presenting as a clean syraki t-signal. It appears modulated through, or resolved as, a form of aquatic life in the world around the pyramid.

The chapter should not recover Oshiro yet.

It should end with Mike underwater, looking down into the dark medium, as a gigantic monstrous head rises from the depths toward him as if to swallow him. The chapter must not confirm whether the creature is Oshiro.

C. Required Context Before Chapter

This chapter follows Oshiro I.

Mike and Lucia have entered the world where Oshiro's unresolved signal is located. They have crossed a strange forest under a pale beige sky, reached a vast blue sea, accessed a partially submerged pyramid, observed violent marine predation through the moon pool, entered a functional alien outpost, confirmed that its data density is too dangerous for the RT-874 to ingest fully, and found an inactive portal hidden on the upper terrace.

Oshiro has not been found.

Susan has continued trying to communicate with Oshiro from the RT-874. Kallom-4000 still cannot establish a reliable lock-on.

The crew knows that direct retrieval remains too dangerous. A blind pull could worsen decohesion or bring aboard something that is not Oshiro.

D. Character State at Chapter Start

Mike is still outside the RT-874 with Lucia. He is aware that he is the safest external vector, but he is not fearless.

Lucia remains calm, operational, and protective. She treats Mike as crew and conscious being, not as a disposable tool. She makes tactical decisions through risk, function, and ethics.

Susan becomes central in this chapter. Her work is not merely calling Oshiro repeatedly. She studies the signal through the logic of the local world and begins filtering it according to the patterns observed in the marine ecology.

Kallom-4000 remains cautious. It can perform analysis, maintain partial contact, and advise, but it cannot solve the problem by force, cannot use q-probes effectively for this task, cannot build a proper alien submersible, and cannot guarantee safe extraction without proximity.

Oshiro is not consciously encountered in this chapter.

E. Chapter Description - Pre-Draft

The chapter opens with Susan reporting a new communication finding.

After studying Oshiro's unresolved signal through the logic of the world around the pyramid, Susan notices that the signal is not behaving like a clean t-signal from a crew member. It is structured in a way that resembles the surrounding aquatic life.

At first, this does not prove that Oshiro has become an animal or that he is inside an animal. It means that the signal is being modulated by biological patterns from the marine environment: rhythms, pulses, intervals, movement cycles, predatory signatures, or other aquatic structures.

Susan continues filtering. The result becomes harder to dismiss.

Oshiro appears to be resolved as some form of aquatic life.

The crew does not know exactly what kind of life. They do not know whether it is small, large, prey, predator, organism, composite, host, mask, or local biological state. But the signal is in the ocean, not inside the visible outpost.

This creates the central problem of the chapter.

Oshiro is deep.

Kallom-4000 cannot complete lock-on from the RT-874. It also cannot complete lock-on from Mike and Lucia's current distance. To recover Oshiro, Kallom needs proximity. Someone or something must get close enough to the signal for the ship to isolate it properly.

Entering the sea is almost impossible.

The medium looks like water, but Kallom-4000 warns that it is not ordinary water. It is an unknown fluid or fluid-like environment with properties the RT-874 cannot model completely. The previous predation event proves that the marine ecosystem is violent. Falling or diving into the sea without a controlled method could kill the external crew members or sever their recoverability.

The first options fail.

They cannot swim down to Oshiro's depth. It is too deep.

They cannot use q-probes for this task. The probes are not compatible with the kind of connection required and cannot establish the correct relationship to Oshiro's signal.

They cannot build a proper submarine from the RT-874. Mike and Lucia find or reconstruct part of an alien blueprint suggesting that the outpost once supported submersible or deep-medium vehicles, but Kallom-4000 determines that fabricating anything similar would be impossible. The architecture is too complex, the material requirements are unknown, and a crude approximation would waste resources without solving the actual problem.

Even if they could build a shell, that would not be enough. The medium is not ordinary water, and the alien vessel design is not merely a pressure container. It is a complete interface with that environment.

They search the outpost for a working vehicle or operating system.

Nothing usable is found.

For several days, Mike, Lucia, Susan, and Kallom study the signal, the outpost, the sea, and the local fauna.

The solution emerges from pattern analysis rather than technology.

Susan and Kallom determine that the aquatic life-form associated with Oshiro follows a vertical current cycle. Most of the time, it remains too deep to approach. But across a repeating period of days, the current brings it upward into a higher layer of the sea. The window is short. After that, it descends again.

If someone were positioned directly above the correct path during that window, and if that person entered the medium briefly, Kallom-4000 might be able to complete lock-on.

This is extremely dangerous.

If Oshiro is prey, attracting attention could cause predation before recovery. If Oshiro is not prey, they still do not know what he is. If the local predators enter the same current zone, they may kill the organism or attack Mike and Lucia. If Mike dives too deep or remains too long, he may not return.

They cannot operate from the pyramid's exposed top or moon pool alone. The calculated current path rises closer to another part of the shore.

Kallom-4000 transports Mike and Lucia to the far shore, where local materials can be used.

They begin constructing a canoe or low boat.

The choice is deliberately primitive. They cannot build a submarine. They cannot master the alien outpost. They cannot force the sea to become safe. They only need a small craft that can float or move across the surface layer long enough to place Mike over the correct current window.

The construction takes time.

During this period, Mike and Lucia observe more of the world. The monkey-like creatures from the forest return. They are cautious but curious. They watch the canoe being built.

Lucia eventually manages to touch one of them. She strokes it gently. The creature does not fully trust her, but it does not flee immediately.

This leads to a conversation between Mike and Lucia about consciousness.

If Oshiro can be resolved as aquatic life, then appearance is no longer enough. A fish-like or monstrous organism may still carry a syraki continuity state. That raises an uncomfortable question: what prevents any of the monkey-like creatures from being another displaced mind? What prevents the trees, the animals, or some other part of the local environment from being conscious in a way the crew cannot detect?

The conversation should remain technical and uncomfortable, not sentimental.

Lucia does not conclude that every animal or plant is a lost syraki. There is no evidence for that. But she agrees that they no longer have the operational right to treat living forms as mere background until they understand the rules of the domain.

The ethical consequence is immediate. They avoid harming local organisms. They do not use animals as bait. They do not treat the ecology as inert scenery. If Oshiro's signal can be biologically modulated, then biological form and conscious status have become unsafe categories.

The conversation also introduces a panpsychist pressure without turning it into a doctrine. They do not decide that everything is conscious. They recognize that consciousness, embodiment, signal, and ecology may be entangled in this place in ways their ordinary categories cannot safely separate.

Later, they observe another predation event near the shore.

A terrestrial animal approaches the strange water to drink. Before it can retreat, something erupts from below and pulls it into the sea. The attack is sudden and brutal. The animal vanishes beneath the surface.

This confirms that the danger is not limited to deep water. The shoreline itself is part of the predatory system.

The canoe is completed.

The predicted current window approaches.

Lucia says she will dive.

Mike refuses.

Lucia challenges him directly. She asks whether he is trying to protect her because she is currently in a female-coded human body. She reminds him that she is older, more experienced, and not to be treated through human gender reflexes. He cannot let human emotional noise corrupt the decision.

Mike says that is not why.

His argument is operational. If anything goes wrong, Kallom-4000 has a higher probability of recovering him than Lucia. The RT-874 is optimized around Mike. His t-signal and external transitions remain the least dangerous to the ship. Kallom-4000 confirms the assessment.

Mike also does not hide his fear. The sea is terrifying. The plan is crude. The creature or signal below them is unknown. The medium is not water. The predators are real. He is afraid, even with the RT-874's emotional regulation supporting him.

Lucia accepts the logic.

They prepare the tether.

The canoe is moved into the water.

Lucia holds the line. Mike will dive. Susan tracks the signal from the RT-874. Kallom-4000 counts the window and gives navigation corrections. The rest of the crew remains tense because the operation depends on timing, distance, and a form of life they do not understand.

The canoe moves quietly across the surface.

They try to make as little sound and disturbance as possible. The water is too still in some places and too deep everywhere. Mike feels that at any moment something could rise from beneath the canoe and swallow both of them.

Lucia feels the same danger but remains controlled.

They reach the calculated spot.

They wait.

Kallom-4000 confirms that the current is rising.

Susan reports that the Oshiro-associated signal is entering the reachable layer.

Kallom gives the order.

Mike dives.

The descent is immediately terrifying.

Mike holds his breath and goes down through the unknown medium. Visibility is poor. He cannot see a normal seafloor, cannot judge distance, and cannot tell how deep the space below him truly is. He sees only blurred lights or fuzzy shapes moving beneath him, indistinct and distorted.

The tether trails back to Lucia.

Voices reach him from above through the communication link.

Kallom-4000 tells him he is close.

Susan confirms the signal relation is improving.

Lucia tells him to continue.

Mike keeps descending.

He repeats to himself that he only needs to get close enough for Kallom-4000 to lock on. He is not trying to capture Oshiro by hand. He is only trying to enter the minimum proximity zone.

His fear intensifies. Even with emotional regulation active, the sea produces a kind of terror he can barely hold.

The voices continue.

A little farther.

Almost there.

The signal is near.

Then the voices change.

Kallom-4000 or Susan tells him that the signal is right there.

Mike looks down.

From the darkness beneath him, an enormous face begins to appear.

It is not the face of a small trapped animal. It is a gigantic monstrous head, almost draconic in impression, rising from the depths. The scale is wrong. The mouth begins to open. It is coming upward toward Mike as if to swallow him.

The chapter ends there.

Do not reveal in this chapter whether the creature is Oshiro.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

Susan determines that Oshiro's signal is modulated through patterns resembling the local aquatic life.

The crew concludes that Oshiro appears to be resolved as some form of subaquatic life, but they do not know what kind.

The q-probes are explicitly not useful for this kind of connection.

The outpost contains blueprints or indications of alien submersible technology, but Kallom-4000 cannot fabricate such a vehicle and warns that the surrounding medium is not ordinary water.

Mike, Lucia, Susan, and Kallom-4000 spend several days trying to solve the recovery problem.

They discover that the life-form associated with Oshiro follows a vertical current cycle and rises into a reachable layer only during a short periodic window.

Kallom-4000 transports Mike and Lucia to another shore where they can build a canoe.

Mike and Lucia build the canoe from local materials.

Monkey-like creatures watch them. Lucia touches one gently.

Mike and Lucia discuss the possibility that consciousness may be resolved into local biological forms, raising panpsychist pressure without confirming that every local organism is conscious.

They observe another predation event when a terrestrial animal is pulled into the water while trying to drink.

Mike and Lucia use the canoe to reach the calculated point above the rising current.

Lucia wants to dive, but Mike argues that he should do it because Kallom-4000 has a higher chance of recovering him if something goes wrong. Kallom-4000 confirms this.

Lucia holds Mike's tether from the canoe.

Mike dives into the unknown medium.

The chapter ends when Mike sees a gigantic monstrous head rising from below as if to swallow him.

The chapter does not reveal whether the creature is Oshiro.

H. Open Problems

Define the final term for the unknown water-like medium.

Define whether the canoe is made from local wood, outpost material, or a hybrid of both.

Define how long Mike can remain submerged safely.

Define whether the tether is physical, technological, or both.

Define how Susan distinguishes Oshiro's signal from the marine life patterns.

Define how much the panpsychist conversation should foreshadow later revelations without overexplaining them.

Define whether the monkey-like creatures return later.

A. Title

TUZ-66941 / Kymintus Was Not Killed

B. Chapter Function

Continue the TUZ-66941 investigation after the Prismatic Core pattern analysis and before the Siuvac-931 interrogation.

The chapter establishes that the investigation is not looking for murder in the human sense. Jabari insists that Kymintus was not killed, and TUZ-66941 finds no accessible evidence that Jabari personally ordered Kymintus's death, Oskiparisis's disappearance, or a direct violent elimination.

The function is to shift the investigation toward concealment, continuity manipulation, memory displacement, t-signal masking, corporate obfuscation, ethical compartmentalization, and distributed megacorporate involvement.

The chapter also introduces the investigative network around TUZ-66941 through TUZ-22473 and sets up Siuvac-931 as the next critical figure: not erased, not removed, but nearly unreachable through lawful privacy, administrative distance, archival noise, and legitimate protections.

C. Required Context Before Chapter

This chapter follows the latest TUZ-66941 investigation thread, after the suspicion that the Oskiparisis deletion and related t-signal masking may require coordination beyond any single local actor, company, or single megacorporation.

TUZ-66941 has already followed the trail from Kymintus through Oskiparisis, physical substrate damage, Ukabkys supply-chain anomalies, Sedfervor-3's obstruction event, and the Prismatic Core pattern analysis.

The reader should understand that the evidence is no longer pointing toward an isolated actor. Multiple fronts now suggest involvement, direct or indirect, from the four major megacorporations.

This chapter occurs before TUZ-66941 meets Siuvac-931. It explains why she becomes the next target of questioning and why the investigative network locks and reinforces the RUN where she currently lives.

D. Character State at Chapter Start

Primary focus entity: TUZ-66941.

Other relevant entities: Jabari, TUZ-22473, Siuvac-931, the Central Algorithm, other TUZ instances, authorized agents, and the four major megacorporations as emerging institutional pressure.

TUZ-66941 remains procedural, evidence-driven, Mandate-bound, and careful about the distinction between suspicion and proof. He does not treat Jabari as a criminal simply because Jabari is near the evidence.

Jabari receives TUZ-66941 without hostility. He does not behave like a criminal, a conspirator, or a cornered executive. He answers the questions placed before him and permits examination of his present state.

TUZ-22473 represents the larger investigative network. His report makes clear that TUZ-66941 is only one active component in a much wider operation.

Siuvac-931 is not seen yet. She is established through records as ancient, wealthy, relatively famous, technically important, and unusually difficult to locate.

E. Chapter Description - Pre-Draft

The chapter returns to TUZ-66941 in Howkian City.

It opens with Jabari speaking directly to TUZ-66941:

"You have my word, esteemed Inquestor, that Kymintus was not killed. We are syrakis; we do not do such."

Jabari receives TUZ-66941 without hostility. He does not behave like a criminal, a conspirator, or a cornered executive. He answers the questions placed before him and permits examination of his present state. TUZ-66941 finds no accessible evidence that Jabari personally ordered Kymintus's death, Oskiparisis's disappearance, or any direct act of violent elimination.

The conversation establishes the central ambiguity of the chapter: Kymintus was not killed, but that does not mean nothing was done to him. The investigation is no longer searching for murder in the human sense. It is searching for concealment, continuity manipulation, memory displacement, t-signal masking, corporate obfuscation, and ethical compartmentalization.

After the meeting, TUZ-66941 encounters TUZ-22473 elsewhere in Howkian City. Their conversation makes clear that TUZ-66941 is not the sole investigator. He is one active component in a much larger investigative network. Other TUZ instances and authorized agents are questioning syrakis, freezing records, mapping supply chains, interrogating administrative pathways, examining RUN dependencies, and tracing evidence across multiple corporate structures.

The evidence is no longer pointing toward an isolated actor. Multiple fronts now suggest involvement, direct or indirect, from the four major megacorporations.

TUZ-22473 reports that the investigation has located a new critical figure: Siuvac-931.

Siuvac-931 is an ancient, wealthy, and relatively famous syraki. She worked for a long time in scientific departments connected primarily to Makilectoz and Valtir & Blue. Her work was not ordinary reality artistry, but it was deeply relevant to the industry: she specialized in the manipulation of consciousness and consciousness-structures, making her knowledge indirectly central to advanced RUN design, qualia engineering, and posthuman experiential architecture.

Finding Siuvac-931 was extremely difficult.

She was not erased. Her tissue and continuity always existed. There was no deletion, no disappearance, and no simple crime of removal. Instead, she had been obfuscated. Layers of lawful privacy, old contracts, identity minimization, administrative distance, archival noise, and legitimate protections made her unusually difficult to detect. Every layer was individually defensible. Taken together, they had one clear effect: Siuvac-931 had been made nearly unreachable.

TUZ-22473 explains that she was found only because the investigation already had suspicions and could cross-reference multiple weak signals. She was not discovered by a normal search. She was excavated from a structure designed to make her vanish without actually erasing her.

Siuvac-931 had strong prospects inside the corporations. Her position, wealth, age, reputation, and technical authority all suggested continued influence. Yet several subcycles earlier, she abruptly withdrew from corporate life and entered Orbiting, preparing herself to be assimilated by another syraki.

The Orbiting is not part of the obfuscation.

It is her own personal decision. Later, it will become clear that Siuvac-931 chose assimilation because the discoveries she encountered altered her spiritual perception of existence. Her withdrawal was not merely defensive or administrative. It was existential.

But because she is important, and because she is now in a transitional state, she has become a vulnerability in the concealment structure.

Due to the precedent of Kymintus and Oskiparisis, the investigative network places a lock over the RUN where Siuvac-931 currently lives. The purpose is not punishment or imprisonment. It is continuity preservation. The lock prevents sudden migration, further concealment, unauthorized memory externalization, forced reconfiguration, accelerated completion of Orbiting, or any supply-chain disruption that might repeat what happened to Oskiparisis.

The Central Algorithm also reinforces the entire supply chain supporting Siuvac-931's RUN: substrate maintenance, administrative routing, redundancy, drone reporting, energy dependencies, continuity channels, access authorization, and integrity logging. The investigation no longer assumes that danger will strike the target directly. It assumes the attack may come through the surrounding infrastructure.

TUZ-66941 is assigned to question Siuvac-931.

The chapter ends before he meets her. TUZ-66941 moves toward her RUN while cataloging her records: her scientific career, her corporate positions, her work in consciousness manipulation, her wealth, her reputation, her withdrawal from Makilectoz and Valtir & Blue, the timing of her Orbiting, and the improbable density of obfuscation surrounding her.

The final impression is that Siuvac-931 is not a simple witness. She is an ancient and dangerous archive of knowledge, still present, never erased, but deliberately made difficult to find. And now TUZ-66941 is going to her before she can disappear into assimilation.

F. Chapter Description - Post-Draft

Not drafted yet.

G. Continuity Export

The chapter establishes that Jabari states directly that Kymintus was not killed and frames that denial through syraki ethical identity: syrakis do not do such.

TUZ-66941 finds no accessible evidence that Jabari personally ordered Kymintus's death, Oskiparisis's disappearance, or direct violent elimination.

The investigation shifts away from murder and toward concealment, continuity manipulation, memory displacement, t-signal masking, corporate obfuscation, and ethical compartmentalization.

TUZ-66941 meets TUZ-22473 in Howkian City, establishing that the investigation is distributed across many TUZ instances and authorized agents.

The evidence now suggests possible direct or indirect involvement from all four major megacorporations.

TUZ-22473 reports that the network has located Siuvac-931.

Siuvac-931 is ancient, wealthy, relatively famous, and professionally connected to scientific departments primarily linked to Makilectoz and Valtir & Blue.

Her expertise concerns manipulation of consciousness and consciousness-structures, making her relevant to advanced RUN design, qualia engineering, and posthuman experiential architecture.

Siuvac-931 was not erased. Her tissue and continuity remained present. She was obfuscated through lawful privacy, old contracts, identity minimization, administrative distance, archival noise, and legitimate protections.

Siuvac-931 withdrew from corporate life several subcycles earlier and entered Orbiting as a personal, existential decision.

The investigative network places a preservation lock over Siuvac-931's RUN and the Central Algorithm reinforces the surrounding supply chain.

TUZ-66941 is assigned to question Siuvac-931, but the chapter ends before he meets her.

H. Open Problems

Define the exact degree of Jabari's institutional proximity to the four megacorporations.

Clarify whether Howkian City has already been introduced visually or needs a short re-establishment in this chapter.

Define whether the preservation lock over Siuvac-931's RUN has a formal name.

Clarify how much TUZ-22473 can state as evidence versus suspicion when discussing the four megacorporations.

Preserve the distinction between Siuvac-931's lawful personal Orbiting and the separate obfuscation structure around her.

Preserve the chapter ending before TUZ-66941 meets Siuvac-931.