99. 🧾 Narrative Control Ledger
Narrative execution ledger for concrete book fixes, open requirements, and completed corrections.
Explanation
This document is a control ledger for narrative work that still needs execution. It is not a memory file, not a lore note, not a brainstorming dump, and not a place to preserve canon. Use it only for concrete tasks that still need to be checked, corrected, inserted, removed, clarified, placed, or applied somewhere in the book.
Each entry should be short, objective, and actionable. Some entries are specific fixes tied to a known chapter, scene, note, outline item, flow sequence, character entry, or place entry. Other entries are unplaced narrative requirements: things that must appear in the book, but whose chapter, scene, or structural location is not known yet. Both are valid here, as long as the entry names the task clearly and explains why it matters.
Unresolved tasks use an empty checkbox. Resolved tasks use a checked checkbox and are visually highlighted in green by the Emacs view, so completed work is visible at a glance. Do not rewrite resolved tasks as new memory. If a resolved task created canon, the canon belongs in the correct database note; this ledger only records that the task was handled.
Recommended format:
Short task title
- Location
known chapter, scene, note, database file, outline item, flow item, or Unplaced / TBD
- Specific affected part
exact paragraph, line, phrase, beat, image, or structural element, if known
- Task
concrete change that must be made
- Reason
why the change matters
Resolved format:
Short task title
- Location
known chapter, scene, note, database file, outline item, flow item, Unplaced / TBD, or final placement
- Specific affected part
exact paragraph, line, phrase, beat, image, or structural element, if known
- Task
concrete change that was requested
- Reason
why the change mattered
- Resolution
what was changed and where
Example unresolved specific fix:
Clarify Jabari's White Citatel replacer
- Location
4. Memories / The Letter
- Specific affected part
Jabari's description during the White Citatel meeting.
- Task
Make sure Jabari's visible replacer respects the White Citatel standard: pale body, white hair, white eyes, and no private ornament.
- Reason
The place note defines the White Citatel as requiring standardized presentation.
Example unresolved unplaced requirement:
Seed the cost of benevolent secrecy
- Location
Unplaced / TBD
- Specific affected part
…
- Task
Add a moment somewhere before the RT-874 reveal showing that ethical agents can still conceal information when disclosure itself is dangerous.
- Reason
The book needs early preparation for game-theoretic failure without malice.
Example resolved task:
Clarify Jabari's White Citatel replacer
- Location
4. Memories / The Letter
- Specific affected part
Jabari's visible replacer during the White Citatel meeting.
- Task
Add short cues that Jabari is using a standardized White Citatel replacer.
- Reason
The place note requires pale standardized presentation.
- Resolution
Added two short passages describing the traditional ajaka model adapted to the White Citatel replacer pattern.
Content
Test
- Location
Unplaced / TBD
- Specific affected part
…
- Task
…
- Reason
…
Write TUZ-66941's future encounter with Kymintus
- Location
Unplaced / TBD
- Specific affected part
Future TUZ-66941 investigation scene involving the entity presenting itself as Kymintus.
- Task
Create a future scene in which TUZ-66941 encounters the entity presenting itself as Kymintus in a pleasure environment, likely a bar or social RUN-space, where "Kymintus" appears relaxed, amused, and immersed in ordinary syraki enjoyment. TUZ must not expose the t-signal fraud yet. Instead, he should begin with a deceptively simple question: whether Kymintus truly feels pleasure. Kymintus answers naturally that of course he does; he is eating, laughing, choosing, desiring, and returning to what pleases him. The conversation should become a philosophical inquiry into qualia: whether the performance, memory, preference, and functional architecture of pleasure are the same as pleasure itself.
- Reason
The scene must show that Kymintus is not lying and not pretending. He believes in his own pleasure because his self-model, memories, behavior, and t-signal-compatible structure all report pleasure. Yet TUZ senses an absence beneath the correct forms. The dialogue should not resolve the question dialectically; it should leave Kymintus briefly reflective, unable to prove whether he feels pleasure or only instantiates the shape of pleasure. This foreshadows the later technical revelation: the being called Kymintus is not a syraki with qualia states, but a nenthor/proxy mapped with extraordinary sophistication to sustain the missing syraki's continuity.
Write TUZ-66941's concealed omniship base chapter
- Location
Unplaced / TBD
- Specific affected part
Future TUZ-66941 chapter involving a Theravada insider, concealed omniship construction bases, the Missing Crews archive, and a damaged recovered syraki.
- Task
Create a future chapter in which TUZ-66941 is escorted by an important insider, not yet fixed as Jabari or another high-ranking figure, into one of Theravada's concealed omniship construction bases. TUZ should see multiple omniships under parallel construction, not as isolated vessels but as an accelerating technological lineage: each hull, core, route system, and cohesion architecture improves upon the failures of the previous generation. The insider must explain that Theravada remains the most advanced builder, while the other three reality artistry megacorporations are also constructing their own vessels. TUZ should receive enough technical briefing to understand that the omniship program is not reckless adventurism, but an enormous rescue-and-containment effort consuming computation, research labor, and institutional fear at a scale almost beyond ordinary corporate logic.
- Reason
The chapter must reframe the corporations as actors trapped under an information hazard rather than simple enemies of the Complex. Its horror center should be the restricted archive concerning the Missing Crews: reports, partial mission logs, recovered distress fragments, and recordings from crews before disappearance, implying that some crews encountered conditions resembling Hellworlds or something adjacent to them. The insider should be visibly burdened, not cold or conspiratorial, and should make clear that the disappeared have not been abandoned. The chapter should culminate with TUZ asking to speak with one recovered syraki whose recording showed extreme terror. That syraki was not recovered whole: his continuity remains damaged, his mind is held in a downgraded human-compatible state because full restoration risks decohesion, and balancing algorithms keep him stable. TUZ enters a therapeutic realm full of pleasure, comfort, and stabilizing stimuli, but the recovered syraki sits distant inside it, quiet and almost absent. The chapter should end on TUZ's conversation with him, closing with a short phrase or revelation that makes the cosmic horror concrete.
Write Susan slapping Ismael scene
- Location
Unplaced / TBD
- Specific affected part
Future RT-874 crew conflict scene between Susan and Ismael.
- Task
Create a later scene aboard the RT-874 in which Susan and Ismael have a disagreement that escalates into Susan slapping Ismael. This should be the only direct physical aggression between crew members in the book. The slap is physically minor by human standards, and Ismael is in a male human body much stronger than Susan's female body, but he collapses, places his hand on his face, and begins to cry and sob almost like a hurt child. The scene should make clear that the damage is not physical: the slap causes an abrupt collapse in his Prif scale because interpersonal aggression inside an intimate bond is profoundly destabilizing to a syraki.
- Reason
The scene should show how alien syrakis are to human retaliation and dominance dynamics. Susan immediately understands the gravity of what she has done, does not blame Ismael, and experiences the act as an atrocity caused by her instability inside a downgraded human body. She rushes to him, embraces him, apologizes, and asks forgiveness. Kallom-4000 reports the sharp Prif drop and stabilizes Ismael. Ismael recovers, understands why Susan lost control, forgives her, and they embrace and kiss. The scene must show sensitivity to aggression, remorse, stabilization, understanding, forgiveness, and restored affection.