Trying a second outcome should not quietly overwrite the first. A scene in which the expedition crosses the bridge and a scene in which it takes the ridge are two branches, even if both share the same characters.
Erogen’s chat guide documents cloning the previous 100 interactions into a new chat. Dreamle’s public group view and subscription-gated world route do not establish an equivalent branch-control mechanism.
Preserve the decision point
Before the route choice, record only common facts:
- The destination is the observatory.
- The deadline is dusk.
- Iona is the adult leader; Pax studies the map; Remy checks equipment.
- Neither route has been selected.
- No one has yet crossed the bridge.
That final pair matters. If the common record already says the bridge was crossed, the ridge branch begins with an event it should not inherit.
Erogen’s clone is limited to a recent segment. A purpose or rule established before the copied 100 interactions may need a concise recap. Do not assume a new chat contains an unlimited copy of the entire project.
Give each branch a state ledger
| State item | Bridge branch | Ridge branch |
|---|---|---|
| Selected route | East bridge | North ridge |
| Known obstacle | Load limit | Longer travel time |
| Evidence needed next | Current inspection | Accurate distance |
| Event not yet established | Successful crossing | Arrival before dusk |
Keep the “not yet established” row. It prevents a fluent answer from turning a plan into a completed event.
The branch should change one decision first. If it simultaneously changes supplies, weather and destination, it no longer answers what difference the route choice made.
A saved world may have wider effects
Erogen’s plan documentation distinguishes recent context, stored history and core memory. A new chat is not automatically proof that every other persistent record is independent.
If a shared or stable record contains “we crossed the bridge,” that fact may need review before using it in an alternate route. The public clone guide does not, by itself, establish that every possible memory source is isolated in the new branch.
Dreamle’s world name likewise does not reveal whether records are copied, shared or regenerated. This review did not create a paid world or inspect its internal state controls, so no isolation guarantee is claimed.
Return with a branch-specific recap
A useful return message says: “Continue the ridge branch. The destination and dusk deadline remain; the group has not reached the observatory.” It identifies the current version and the next unresolved task.
Do not merge the branch histories simply because both produced interesting scenes. Choose an accepted outcome or deliberately write a later reconciliation, then update the project record accordingly.
For a recent conversational fork, Erogen has the more explicit documented control. For a larger Dreamle world, the internal branching mechanism remains unknown. The local state ledger is useful in either case, and no conversation or clone was executed for this article.