01
Define the unit that travels
A relay becomes easier to understand when the thing being passed is explicit. In a story workspace, it might be a scene-state card rather than the whole manuscript. In a trail, it could be a clue card. RealmRelay can use a short descriptor to identify that unit. The product should also show who supplied it and which version the recipient received. A decorative arrow between contributors says little unless the underlying record identifies the context needed for the next step and the details that remain unsettled.
02
Let realm signal imagination without borrowed lore
The realm component offers room for distinctive settings, but a sample should develop its own small vocabulary and situations. A brass token, a gate and a library can demonstrate a handoff without borrowing characters or terminology from an existing franchise. RealmRelay could develop an editorial voice that is curious and precise about continuity. The aim is to help contributors extend a setting while respecting what has already been established. A name with fantasy associations need not claim ownership of a broad genre or imply affiliation with another creative property.
03
Make successive versions easy to distinguish
A relay motif could use connected cards with a visible version label. In an actual workspace, each card should identify its source scene and whether it is a draft or accepted handoff. RealmRelay remains readable when the two capitalised words are preserved. Avoid relying solely on colour to distinguish proposed details from established ones. Short labels such as recorded, proposed and unknown help readers follow the process. The visual system should make a changed story state apparent without making an unaccepted suggestion look like a completed event.