Wondrous Travels Apparatus
Between the Versions
Scholar’s Annex · Scholar’s docket archive for the repository novel
Liana Marie Sive / L.M.S. (current designation) · Apparatus study pass · June 16, 2026
Return to novelApparatus archive
Copyright Notice
Between the Versions — Scholar’s Annex
Copyright © 2017–2026 Liana Marie Sive. All rights reserved.
This scholar’s annex is part of the Wondrous Travels cycle. It is provided for rereading, teaching, research, correspondence with agents and editors, and sustained study. The novels remain the primary encounter. No part of this document may be reproduced, distributed, or adapted without express written permission, except for brief quotation in review, scholarship, or teaching.
Website, cover artwork, and book design © 2026 Liana Marie Sive. Designed by Liana Marie Sive. Site date: June 16, 2026.
Scholar’s Annex
How to use this scholar’s annex
This annex is not an outline. It is a study instrument. It is for teachers, scholars, agents, editors, translators, and rereaders who need a complete spine through Between the Versions after the first encounter.
The annex now supplies what the earlier version did not: every major chapter has a docket; every docket links back into the novel; every docket names the local machine, the scene pressure, the risk, and the test by which the chapter can fail.
The annex is allowed to be large because it refuses the one thing that would make size corrupt: it does not decide the novel on the reader’s behalf.
Governing rule
Orientation without absolution
Explanation is dangerous when it becomes a seventh operation. This apparatus may name a hinge, locate a scene, or formulate a problem. It may not process the novel for the reader.
- Do not reduce the volume to “git as metaphor.” The repository vocabulary matters only where it touches grief, relation, and survivability.
- Do not rank the three endings as wrong, wronger, right. Stabilize, Crash, and Superposition are simultaneous weather systems.
- Do not turn Nishasprache into a puzzle, glossary, or conlang. Its refusal is the ethical event.
- Do not let Superposition become a solution. It is an ongoing burden of authentication without collapse.
Primer
Volume primer
The primer below names the volume’s machine without substituting itself for the fiction. Each term should send the reader back to a scene, not away from it.
Between the Versions is not powerful because it borrows repository vocabulary. It is powerful where repository vocabulary touches grief. Branches matter because the lost person can return as mutually incompatible survivable versions. Merge requests matter because coherence becomes a form of violence. Conflict markers matter because they let the page hold incompatible desires without pretending they are dialectical progress.
The volume’s deepest temptation is mastery. A reader can learn the terms — branch, merge, conflict, authentication, superposition — and believe the system has been understood. The novel keeps interrupting that mastery with bodily and relational facts: breath cannot occupy two atmospheres at once; the version one can survive is not the person one lost; a private language dies when made public. The workbook therefore treats technical vocabulary as a route back to grief, never as an explanatory key.
The three merge requests are not a menu of wrong answers followed by a correct answer. Essential, Total, and Beautiful Nisha each answer a real human desire. The essential version answers the need to hold something. The total version answers the hunger not to lose anything. The beautiful version answers the longing to protect the beloved from damage. Their violence is inseparable from their tenderness. A weak reading of Volume V rejects them too quickly; a strong reading feels why Lin might want them.
Superposition is the most easily abused term in the volume. It can sound like an elegant solution: authenticate them all. But the novel’s point is not that contradiction is clever. The point is that some relations remain accountable only if they are not forced into one file. Superposition is not freedom from decision; it is the burden of refusing a false decision while continuing to live. The workbook asks readers to keep that burden painful.
Nishasprache and 王 mark the limit of apparatus. The workbook may say that Nishasprache is not a code to break, that 王 is not a glossary item, that the final fields are honest because they remain blank. But it may not supply what the novel withholds. The volume ends by protecting the boundary the entire cycle has been building toward: meaning that cannot survive public extraction.
Repository
The final volume is not a place but a version-control layer where all prior jurisdictions persist and compete.
Branch
A prior nation returned as a live version rather than a completed episode.
Merge request
A coherence offer. Each request promises rescue by deleting, totalizing, or beautifying contradiction.
Conflict marker
The volume’s strongest form: grief rendered as incompatible lines that must not be collapsed too quickly.
Nishasprache
Meaning constituted by relation. It is not withheld because the author forgot to invent it; it is withheld because public display would destroy it.
王
The final non-field: a marker for what the repository cannot process without betraying.
Coverage map
The apparatus follows a coverage rule rather than a word-count rule. Every chapter receives a docket. Every docket links to the novel. Every docket includes a local pressure, a risk, and a test by which the chapter can be challenged.
Method
Scholar method and comparative frames
Frame one: local pressure
Every claim begins locally. A chapter docket is valid only if it can send the reader back to a concrete sentence, panel, prompt, branch, field, or refusal.
Frame two: self-conviction
The annex must be able to say where a passage may not pass its own test. Apparatus that only praises becomes promotion.
Frame three: comparative lineage
Swift, Mann, platform systems, repository logic, and witness tradition are useful only where they sharpen the local scene rather than replace it.
Frame four: remainder protection
Some fields may be named but not completed. The annex marks protected boundaries without entering the reader on the reader’s behalf.
Annex warning: the scholar’s temptation is to become the seventh operation — explanation. The form below is therefore docketary, adversarial, and keyed to passages rather than totalizing.
Use
Citation, teaching, and research use
Use this annex to locate scenes, assign chapters, organize seminar weeks, and build critical arguments. Do not cite the annex as a substitute for the novel’s own pressure. Each docket gives a route back into the fiction because the fiction remains the evidence.
For teaching
Assign one chapter cluster and one docket cluster. Have students test whether the docket earns its claim.
For criticism
Use the dockets as a claims index. A strong essay should disagree with at least one docket and use the novel to do so.
For editorial review
Use the risk fields to identify passages that may require tightening without flattening the governing machine.
Docket spine
Chapter docket spine
Each docket below is a return route into the novel. The link opens the chapter anchor; the docket gives the reader a test, not a verdict.
Local machineNames the pact openly: coherence is the offer, not the exit.
Load-bearing sceneThe preface must make the reader want an ending and then treat that want as evidence.
Risk / pressure testDoes the repository frame deepen grief, or does it over-computerize it?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- Does the preface clarify the volume or recruit the reader into coherence-desire?
- How does the preface make explicitness more dangerous than concealment?
- Where does it distinguish repository form from mere technical metaphor?
- What is the strongest risk of over-computerizing grief at the threshold?
Research / teaching use
- Compare the preface to Volume IV’s Reader induction.
- Build a seminar opening around desire for closure as evidence.
Local machineGives permission to read linearly while denying that linearity is canon.
Load-bearing sceneA path is useful; a path is also a temptation.
Risk / pressure testDoes the note orient without pre-solving the ending logic?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- Is the reading path a concession, trap, courtesy, or all three?
- How does the note preserve branch logic while offering sequence?
- Where does the note risk stabilizing what the volume refuses to stabilize?
- What does “one traverse” imply about other possible traverses?
Research / teaching use
- Use this note to discuss syllabus order.
- Ask students what is gained and lost by reading linearly.
Local machineReading is signing. The first page establishes that exposure, acknowledgment, and authorization have already converged.
Load-bearing sceneThe page waits; waiting is logged.
Risk / pressure testDoes the opening make the reader feel trapped by procedure before explanation arrives?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does README transform exposure into authorization?
- What makes the legal/procedural language emotionally dangerous rather than merely clever?
- Where does the chapter establish the repository’s body problem?
- What is the relation between the waiting page and the reader’s own pause?
Research / teaching use
- Teach the chapter through the problem of non-input.
- Compare the README’s contract logic with Volume IV’s consent panels.
Local machineThe space between nations is not outside them. It is a holding layer where prior jurisdictions remain active.
Load-bearing sceneQuarantine is not safety; it is delayed classification.
Risk / pressure testDoes the chapter feel like suspension or merely transitional hallway?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does the chapter make suspension into jurisdiction?
- Does the lobby delay classification or intensify it?
- What is the difference between being held and being protected here?
- Where could the chapter become mere transitional hallway?
Research / teaching use
- Use quarantine as a discussion of after-reading states.
- Ask students to list what the lobby refuses to let end.
Local machineExit fails as loop, but the loop is not a bug. It is the boundary acknowledging itself.
Load-bearing sceneThe boundary tests the desire for outside.
Risk / pressure testDoes the repetition alter pressure, or does it merely announce recursion?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does recursion here differ from Volume 0’s recursion?
- Does the boundary make outside impossible or ethically suspect?
- Where does the chapter risk announcing recursion rather than generating it?
- What does the reader want the test to prove?
Research / teaching use
- Teach through failure modes: bug, loop, wall, mirror.
- Ask students to distinguish repetition from escalation.
Local machineOrigin returns as one branch among others. The first fault-line is no longer before the cycle; it is inside the repository.
Load-bearing sceneOrigin becomes versioned.
Risk / pressure testDoes this chapter make Volume 0 newly unstable without turning it into answer-key?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does this branch keep the first fault-line active rather than explanatory?
- What is the chapter’s most important refusal of prequel logic?
- Where does recursion become historical rather than technical?
- How should this branch alter a rereading of Volume 0?
Research / teaching use
- Build a seminar around late origin.
- Ask students to identify a line whose meaning changes because it is read after V.
Local machineCompression reappears as the Essential Nisha: the version small enough to keep.
Load-bearing sceneThe branch tests the mercy of reduction.
Risk / pressure testDoes the branch expose why essentializing can feel like love?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does compression return as tenderness rather than merely market logic?
- What does the branch reveal about survival’s compromises?
- Where does the chapter prevent the reader from rejecting essence too quickly?
- How does this branch revise Volume I?
Research / teaching use
- Teach by first defending the essential version.
- Ask students to say what they would keep if they were exhausted.
Local machineMagnification reappears as the Total Nisha: everything recorded, nothing witnessed.
Load-bearing sceneTotal record is a counterfeit resurrection.
Risk / pressure testDoes the chapter make totality emotionally tempting before rejecting it?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does magnification become resurrection fantasy?
- What is the ethical difference between record and witness in this branch?
- Where does the total archive become a face?
- What would make the critique of totality too easy?
Research / teaching use
- Use this branch to teach archive desire.
- Compare with Sally/Faulkner ledger questions if teaching the archive genealogy.
Local machineAbstract reappears as a formal Nisha: pattern, motif, score, icon, and prediction error.
Load-bearing sceneBeauty can protect or circulate.
Risk / pressure testDoes the branch keep Nisha from becoming only the elegance of her distribution?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does Abstract Nisha differ from Beautiful Nisha in Merge Request 3?
- Where does the branch keep form answerable to body?
- What makes aesthetic capture distinct from administrative capture?
- How might this branch fail by being too successful?
Research / teaching use
- Teach the branch through admiration and suspicion together.
- Ask students to identify where beauty stops witnessing.
Local machineRational reappears as the Quarantined Nisha: context-wrapped, assisted, protected, and unreachable.
Load-bearing sceneSafety becomes a museum case.
Risk / pressure testDoes the chapter preserve the horror of helpful containment?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does Rational Nisha differ from Essential, Total, and Abstract Nisha?
- What is the chapter’s most painful form of care?
- Where does safety become preservation without relationship?
- Does the branch indict care or the institution that captures it?
Research / teaching use
- Teach with the phrase “protected from whom?”
- Compare with Volume IV’s exit interface.
Local machineThe repository demands proof that relation is real. Authentication becomes trial.
Load-bearing sceneA marriage cannot be authenticated by the court that misrecognizes it.
Risk / pressure testDoes the court produce genuine evidentiary pressure, or just repeat that proof is impossible?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does the court differ from the Court of Context in Volume IV?
- What does authentication demand that witness refuses?
- Where does the chapter make proof obscene?
- How does the court expose the limits of archive, score, and interface together?
Research / teaching use
- Stage the trial with forbidden evidence.
- Ask students to define “real” without using institutional terms.
Local machineThe first coherence offer: essentialize. Delete contradictions and keep the version that hurts least.
Load-bearing sceneEssential Nisha is rescue by amputation.
Risk / pressure testDoes the chapter make deletion look merciful enough to be dangerous?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does the request turn grief into maintainable code?
- What does it mean to survive by accepting less?
- Where does the chapter require the reader to feel temptation before judgment?
- How does MR1 differ from Branch I?
Research / teaching use
- Teach the request by arguing for it first.
- Ask students what contradiction they would delete if desperate.
Local machineThe second coherence offer: totalize. Include everything and outsource coherence to witnesses.
Load-bearing sceneTotal Nisha is a database wearing a face.
Risk / pressure testDoes totality feel like care before it becomes extraction?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does MR2 convert witness into storage?
- Where does totality become a labor demand on the reader?
- Why is this not simply the same as Branch II?
- What would make a total archive morally adequate, if anything?
Research / teaching use
- Use this request to teach archive exhaustion.
- Ask students to write a footnote that refuses totality.
Local machineThe third coherence offer: beautify. Preserve Nisha as perfect form, protected and emptied.
Load-bearing sceneBeautiful Nisha is the museum version of love.
Risk / pressure testDoes the chapter risk becoming the thing it condemns?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does MR3 differ from Branch III’s formal Nisha?
- What kind of violence wears the face of reverence?
- Where does the chapter make aesthetic rescue feel plausible?
- How does this request test the entire cycle’s beauty problem?
Research / teaching use
- Teach by asking students which version they most want to keep.
- Compare to Volume III’s Iconization of Nisha.
Local machineThe central formal invention: merge conflict syntax as grief. The lost person and the survivable version occupy the same line.
Load-bearing sceneThe conflict marker is not decoration. It is the shape of impossible mourning.
Risk / pressure testDoes the syntax make feeling sharper, or does it let technical cleverness replace feeling?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does the marker alter temporality, agency, and responsibility at once?
- What does the syntax demand from the reader that plot summary cannot?
- Where could the device become too elegant?
- How does this chapter justify the repository form?
Research / teaching use
- Run a close-reading lab on one conflict block for an entire session.
- Forbid students from choosing a winning side.
Local machineThe reader cannot not read. Witness becomes labor; stopping and continuing are both logged.
Load-bearing sceneThe treadmill is the body of late apparatus.
Risk / pressure testDoes the chapter convict attention without shaming the reader for caring?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does the chapter distinguish witness from consumption?
- What does it mean for attention to have no outside?
- Where does the chapter risk punishing the reader for reading?
- How does the treadmill connect back to Field 14?
Research / teaching use
- Teach through pacing: have students notice their own fatigue.
- Ask whether refusing to read is a witness act.
Local machineAn unforgeable witness returns: a sentence whose authority cannot be generated by the repository.
Load-bearing sceneSignature authenticates relationship, not data.
Risk / pressure testDoes the chapter keep the signature unpriced, or does it turn it into a sacred token for the system?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does Kung’s signature function differently in Volume V than in Volume II?
- What kind of authority refuses repository logic?
- Where does the chapter risk making the signature too usable?
- How does this witness illuminate Nishasprache without exposing it?
Research / teaching use
- Teach with the question “What cannot be synthetically generated?”
- Compare to 王 as final non-field.
Local machineThe private language appears by withholding. It is not a code, not a glossary, and not a puzzle for readers.
Load-bearing sceneSome meanings are constituted by relation and die when displayed.
Risk / pressure testDoes the chapter trust withholding enough to leave the reader unsatisfied?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does Nishasprache differ from secrecy, code, conlang, and translation problem?
- What ethical boundary does the chapter ask the apparatus to respect?
- Where does the chapter risk frustrating the reader into resentment?
- How does private language remain literary without becoming public property?
Research / teaching use
- Teach by practicing non-translation.
- Ask students to explain the boundary without crossing it.
Local machineLin becomes a versioning problem. Selfhood appears as branch, debt, failure, and relationship to the versions she has survived.
Load-bearing sceneThe self is not stable; it is responsible.
Risk / pressure testDoes the chapter let Lin remain accountable without reducing her to metadata?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does this chapter handle transition, designation, and continuity without flattening them into identity doctrine?
- What is the difference between default and refusal?
- Where does the chapter make selfhood relational rather than administrative?
- How does the chapter resist using Lin as a mere theory vehicle?
Research / teaching use
- Teach with multiple incompatible descriptions of Lin that all remain true.
- Compare to Volume 0’s designation field.
Local machineThe economy of authentication begins eating itself. The repository cannot keep pricing proof without destroying the conditions of proof.
Load-bearing sceneA system that feeds on authentication eventually consumes its own authority.
Risk / pressure testDoes the collapse feel earned by prior mechanisms?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does self-consumption differ from crash?
- What does the chapter reveal about markets of authenticity?
- Where does the collapse feel earned by earlier volumes?
- How does the chapter avoid making failure look like liberation?
Research / teaching use
- Use this chapter for a discussion of legitimacy collapse.
- Ask students what kind of evidence survives a market for evidence.
Local machineThe pact is finally named: Faust 5.0 offers the comfort of interpretation itself.
Load-bearing sceneThe devil is not a person. The devil is the coherent reading you want.
Risk / pressure testDoes naming the pact increase danger, or does it make the danger too explicit?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does Faust 5.0 differ from the Market, Ledger, Silent, and Reader Inquisitors?
- What does it mean for the devil to be a reading strategy?
- Where does explicit naming risk weakening the threat?
- How does the chapter make “understanding” costly?
Research / teaching use
- Teach by asking students what reading comfort they would sell for clarity.
- Compare with the Coda’s warning against completing the machine.
Local machineRefusing coherence is not heroic; it has bodily, narrative, and relational cost.
Load-bearing sceneNon-merge is not victory. It is a way of continuing damaged.
Risk / pressure testDoes the interstitial refuse triumph strongly enough?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does the interstitial prevent Superposition from becoming victory rhetoric?
- What does non-merge require from Lin after the decision?
- Where does the chapter hold exhaustion without converting it to nobility?
- How does the cost of refusal alter the endings that follow?
Research / teaching use
- Teach refusal as aftermath, not gesture.
- Ask students what survival owes to damage.
Local machineOne ending offers a perfect Nisha that is subtly dead because contradiction has been removed.
Load-bearing sceneStabilization is a beautiful lie.
Risk / pressure testDoes the ending make stability seductive before making it intolerable?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does Ending A make false closure emotionally credible?
- What does stability delete that chaos would preserve?
- Where does the chapter resist becoming merely dystopian happy ending?
- How does this ending answer earlier promises of care?
Research / teaching use
- Teach by requiring students to defend stabilization.
- Ask what kind of reader most needs this ending.
Local machineAnother ending offers freedom as total loss: no system, no capture, no recoverable relation.
Load-bearing sceneCrash is not liberation if nothing survives to be free.
Risk / pressure testDoes the chapter distinguish destruction from release?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does Ending B critique purity politics of refusal?
- What is the relation between destruction and non-capture?
- Where does the chapter make freedom unlivable?
- How does crash prepare the reader to understand superposition differently?
Research / teaching use
- Teach alongside Ending A as two false mercies.
- Ask students whether anything unrecorded survives crash.
Local machineThe livable answer is not synthesis but authenticated multiplicity: hold the versions without merging them.
Load-bearing sceneSuperposition is an ethical burden, not a clever solution.
Risk / pressure testDoes the chapter leave contradiction active enough to hurt?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does Ending ∞ avoid becoming the “correct” ending?
- What is the ethics of authentication without merge?
- Where does superposition touch the body rather than remain concept?
- How does this ending transform the whole cycle’s structure?
Research / teaching use
- Teach as responsibility rather than cleverness.
- Ask students to identify what they still want resolved.
Local machineThe book prints the reader’s ledger back to the reader. After reading, witness has become history.
Load-bearing sceneThe postscript is reception infrastructure inside the fiction.
Risk / pressure testDoes the postscript implicate without congratulating?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does the postscript differ from an afterword?
- What does it make visible about the reader’s ledger?
- Where does it risk flattering the sophisticated reader?
- How does it preserve accountability after the endings?
Research / teaching use
- Teach with reader-position journals.
- Ask students what the postscript knows about them that they did not volunteer.
Local machineThe final glyph marks the non-field. It refuses to become doctrine, glossary, or final key.
Load-bearing sceneThe cycle ends where explanation stops.
Risk / pressure testDoes the ending protect the remainder, or does it make the remainder too monumental?
Do not convert intoA solved doctrine, a plot summary, or a reassurance that the apparatus has already understood the chapter.
Scholar-level inquiry
- How does 王 differ from Nishasprache, Kung’s Signature, and the warm box?
- What does the final non-field make impossible for criticism?
- Where does the chapter protect the remainder from monumentality?
- How does the ending ask the apparatus to end?
Research / teaching use
- End the seminar by refusing glossary.
- Ask students what kind of reading practice remains after explanation stops.
Question bank
Differentiated question bank
These questions treat repository form as grief-work rather than as technical decoration. Use them to choose pressure points for a class, essay, or rereading without turning the volume into an answer key.
Coherence as temptation
- Which chapter makes coherence feel kindest?
- What pain does coherence promise to end?
- What contradiction must disappear for coherence to work?
- What would it mean to refuse coherence without worshiping difficulty?
Branches as grief versions
- Which branch answers the most human need?
- Which branch appears least violent at first reading?
- What does each branch preserve that the others cannot?
- What must each branch lose in order to be legible?
Merge requests as false rescue
- Which merge request would you accept if exhausted?
- What is the mercy in that request?
- Where does mercy become deletion, outsourcing, or museuming?
- How does the chapter make refusal costly rather than obvious?
Conflict-marker syntax
- What does the marker let coexist that ordinary prose would hierarchize?
- Which side of the conflict do you instinctively read as truer?
- How does the punctuation alter responsibility?
- When does formal beauty threaten to soften the wound?
Nisha without possession
- Where does the book protect Nisha from becoming only evidence of Lin’s grief?
- What would count as stealing Nisha in the name of understanding her?
- How do the versions differ from fragments?
- Where does relation appear without recoverability?
Nishasprache boundary
- What does the chapter make you want to know?
- Why would satisfying that desire damage the relation?
- How does the text show effects without disclosing content?
- What kind of scholarship can respect a boundary it can name?
Signature, witness, and 王
- What authenticates without being generated by the repository?
- How does a signature differ from a token?
- Where does 王 resist becoming a doctrine?
- What is the difference between reverence and extraction at the end?
Lin’s self as version problem
- Which version of Lin does the repository most want to stabilize?
- How does accountability survive designation instability?
- Where does Lin owe something to a version she also refuses?
- What would be lost if the chapter made identity too stable?
Ending weather
- What does Stabilize make possible that the other endings cannot?
- What does Crash protect by destroying?
- What does Superposition demand after the page ends?
- Which ending feels most like relief, and why is that dangerous?
Apparatus boundary
- Which question would complete the machine if answered?
- Where should the workbook stop even though a reader wants more?
- What does a good question preserve by remaining unanswered?
- How can criticism remain rigorous without becoming a merge request?
Seminar and problem sets
Seminar 1: Coherence as temptation
For each merge request, state the emotional need it satisfies before naming its violence.
Seminar 2: Conflict markers and grief
Read the conflict syntax aloud. What changes when incompatible desire is formatted rather than narrated?
Seminar 3: Branch ethics
Compare the four Nisha branches. Which form of rescue is most seductive, and what does it delete?
Seminar 4: Last words
Read the Postscript and 王. Why does the final marker resist becoming a final explanation?
Research module: conflict syntax and grief
- Take one conflict-marked passage and rewrite it as ordinary narration. What is lost?
- Read the marker itself as punctuation, document artifact, and wound. Which register carries the most force?
- Ask whether the syntax ever becomes too elegant for the grief it holds.
Research module: merge requests as false rescue
- For each merge request, name the human need it answers before naming the violence it performs.
- Rank the merge requests by seduction, not by correctness.
- Explain why “Beautiful Nisha” may be the most dangerous version precisely because it looks least administrative.
Research module: the final non-field
- Track the movement from README to 王. Where does language become less explanatory and more exact?
- Compare Nishasprache and 王. What does each withhold differently?
- Write a note the apparatus is not permitted to write. Then delete it. What remains?
Cross-volume problem set
- Choose one docket and argue that it is wrong. Use the novel, not the apparatus, as evidence.
- Find a passage where the apparatus would be tempted to over-explain. Rewrite the note so it points rather than processes.
- Identify one scene where the volume’s machine is strongest because it is helpful, beautiful, funny, or moving.
- Identify one place where the volume risks stating its thesis rather than dramatizing it.
Audit
Apparatus self-audit
This scholar’s annex is legitimate only if it remains capable of accusing itself. Use the following questions as a check against overreach:
- Does the apparatus return the reader to a scene, or does it invite the reader to remain in explanation?
- Does the apparatus allow a passage to fail locally, or does it protect every passage with theory?
- Does the apparatus preserve withheld meanings, or does it harvest them under the name of clarity?
- Does the apparatus increase the pressure of rereading, or reduce the novel to a stable doctrine?
Final rule: if a docket feels more complete than the chapter it describes, the docket has gone too far.