PLOT LAB / INPUT COMPATIBILITY
What if a kept plot beat conflicts with my new brief?
If a kept plot beat contradicts a new brief, choose which instruction you want to change before generating again. Copy the kept event into a short comparison note, underline the incompatible new condition, and either clear that beat or rewrite the condition. Asking for both does not create a meaningful variation. It asks the outline to preserve an event while also forbidding it.
Compare events, not the mood of the instructions
Keeping an outline beat is useful when an accepted event should survive another draft. It is not a way to make incompatible requirements compatible. This exercise uses an original fictional example, not a recorded model response. The comparison happens before generation so you can decide what should be preserved without spending another request on an unresolved conflict.
Restorer Tessa needs access to a workshop before the market closes. The accepted beat says: “The caretaker gives Tessa the workshop key after she agrees to return it before closing.” The next beat has Tessa use that key to enter. You keep the handover because it connects the request, promise and entry. The brief originally allowed the caretaker to lend the key.
Now change the brief to: “The caretaker never gives Tessa any key, and Tessa receives no key from anyone else.” That condition directly forbids the accepted handover. A darker tone, a sharper argument or a new description of the workshop cannot fix the conflict. The same event cannot both occur unchanged and be excluded by the new instruction.
Route A: preserve the handover and narrow the new condition
Keep the accepted beat, but replace the new restriction with: “The caretaker refuses to let Tessa keep the workshop key after closing.” Lending a key until closing is compatible with refusing to let someone retain it afterward. Tessa still receives the key and can enter. The changed condition now creates a return obligation rather than forbidding the means of entry.
Check the following beat too. If Tessa returns the key before closing, the sequence can satisfy both the retained handover and the revised restriction. If a later beat has her keep it overnight, that later event needs another decision. Do not label the entire outline compatible merely because you repaired the first contradiction.
Route B: preserve the refusal and release the handover
If receiving no key is essential, clear the kept handover. Replace its event with a new proposal: the caretaker escorts Tessa into the workshop and keeps the key on a belt ring. Tessa has access without possession. This is a different beat, so it must not be presented as an unchanged version of the original handover.
The following entry beat also needs attention. “Tessa unlocks the workshop with the borrowed key” no longer fits. “Tessa follows the caretaker through the opened door” does. That replacement preserves the goal of entering, while changing who controls access. An unsupervised inspection later in the outline would need permission, distraction or another explicit action; it cannot silently inherit the freedom that borrowing the key once provided.
Both routes can be coherent, but they tell different stories. Route A puts pressure on Tessa's promise to return the object. Route B puts pressure on what she can inspect while accompanied. Select the conflict you intend to write instead of treating the routes as equivalent wording for the same event.
Two workarounds that only hide the contradiction
Secret spare: the new outline lets Tessa find a duplicate in her coat. That still breaks the chosen condition that she receives no key. It also adds an earlier acquisition the outline has not established. If you want the spare, revise the restriction openly and establish where it came from; do not claim the no-key version was preserved.
Renamed object: the new outline calls the borrowed key an access token, although it still opens the workshop in exactly the same way. A new noun does not repair a restriction on the event. If the intended condition forbids unsupervised entry rather than keys specifically, even a genuinely different access device would miss the point. Write the constraint at the level you actually care about.
Use a compatibility note before the next request
Accepted event: caretaker gives Tessa the key until closing. New conflicting condition: Tessa receives no key. Choose A: keep handover; forbid keeping the key after closing. Or choose B: keep no-key rule; clear handover and propose escorted entry. Check dependent beat: borrowed-key entry versus following the caretaker. Do not count: a secret spare or renamed key as satisfying the refusal. Review afterward: access, possession, supervision and return obligation.
The plot generator has a Keep this beat control on generated outline beats. Its current implementation preserves selected beat text and rejects a response that changes it; this is not a semantic check that every new instruction is consistent. Clear the selected beats before changing the structure or freeform beat count. The scene-to-outline repair guide handles a decision that has already appeared in prose; here you are resolving incompatible planning instructions before another generation.
Questions about keeping plot beats
Does changing the tone require clearing a beat?
Not automatically. A tone request can change surrounding presentation while leaving an event intact. Read the requested change: asking for a tense handover is different from asking that no handover occur. Check compatibility at the event level rather than treating every changed field as a contradiction.
Will clearing the beat guarantee a better outline?
No. It removes one preservation instruction. A new result still needs review for facts, causal links and your remaining constraints. This page demonstrates an input comparison, not a success-rate test of the writing service.
Can I keep the purpose instead of the exact wording?
For Tessa, the purpose might be gaining workshop access at a cost. The accepted handover and escorted entry can both serve that purpose, but they are not the same event. Put the purpose in the brief and release the exact beat if you want that freedom. Do not leave an exact-preservation checkbox selected while expecting its event to be replaced.
Source and scope
The Reedsy mystery plot tool provides beat locking and iterative generation; those general features are not claimed as an invention here. The StoryWish plot interface and its public script were inspected for the behavior described above. Tessa, the caretaker, both compatible routes and both failed workarounds are original editorial fiction, not generated results or evidence of exclusive coverage elsewhere.