Production

Lore

Jalaran Lore is a character bible that records what each script has actually established, so a long-running series does not contradict itself.

Who Lore is for

For serialised creators past the point where they can hold the canon in their head. If you have ever had to rewatch your own episode to check what colour something was, or whether a character had already met another one, Lore is that problem written down.

What Lore does

Lore keeps a character bible and, beneath it, a log of confirmed facts — each one linked to the script that established it, so you can always ask not just what is true but where it became true. Facts are proposed by the AI after a script is generated and confirmed by you, never written silently. Lore also generates scripts from a character bible and a topic, and the generated script comes out with voice markup already embedded, so it is immediately something you can paste into Voice rather than something you have to annotate first.

  • Per-character fact log with provenance back to the establishing script
  • AI-proposed facts you confirm or reject — never silent writes
  • Script generation with voice markup already embedded
  • A locked reference image that Puppet and Premiere both reuse

How Lore works

  1. Define a character

    The bible: who they are, how they speak, and a reference image the rest of the pipeline uses.

  2. Generate a script

    A character plus a topic becomes a structured script with voice markup already in place.

  3. Confirm what it established

    The AI proposes facts the script introduced; you confirm or reject each one. Confirmed facts carry a link back to their script.

  4. Export verbatim

    Markdown export keeps the voice markup intact, because the export is what you paste into Voice.

What Lore does not do

Lore records what your scripts established; it does not enforce consistency at write time, so it will not stop you writing a contradiction — it gives you the log to notice one. It holds facts, not plans; what you still intend to write belongs in Arc, and the separation is deliberate. Generated scripts need editing, and the module treats them as drafts. It does not import an existing series: the log starts when you start it.

Common questions

How is Lore different from Arc?

Lore is a record and Arc is a plan. A Lore fact is confirmed continuity established by a script that exists; an Arc beat can exist before any script does. Keeping them apart is what lets a plan legitimately run ahead of the work.

Does it add facts automatically?

No. After a script is generated the AI proposes facts it introduced, and each one waits for you to confirm or reject it. Nothing enters the canon without an explicit decision.

Why does the export keep the voice tags in?

Because the export exists to be pasted into Voice. Stripping the markup to make the Markdown prettier would destroy exactly what the file is for.