Fount - Screenplay writing and analysis tools in Elixir

Aloha gang,

Did one for fun, just to pass the time. Fount is an Elixir poncho repo containing screenplay writing and analysis tools. All MIT licensed, and thus fit for strip-mining or assimilation into your borg via your agentic initiatives:

A screenplay revision workshop for writers who want to experiment aggressively without losing control of the draft.

Fount lets you experiment aggressively with a screenplay without losing control of it: ask creative questions, generate real alternate pages, trace the consequences of big story changes, mix the best pieces, hear them performed, compare them to your draft, and decide what actually becomes canon.

It is built around a simple idea: rewriting a screenplay should not mean handing the whole script to a model and hoping it remembers what matters.

Fount keeps the screenplay itself, its revision history, its characters, scenes, dialogue, story evidence, alternate approaches, proposed changes, and accepted draft separate enough that you can try dangerous ideas without endangering the version you already have.

Nothing becomes part of the accepted screenplay merely because an AI generated it.

---

What You Can Actually Do With It

Fount is designed for screenplay work such as:

• Develop pages from a brief. Start with a dramatic intention, situation, constraint, or story problem and generate actual screenplay material rather than another outline about what could happen.
• Continue a draft or bridge existing scenes. Write forward from existing pages or create the missing dramatic connection between two scenes while using the surrounding screenplay as context.
• Explore genuinely different versions. Ask for multiple dramatic approaches, keep them as separate candidates, and audition the alternatives instead of forcing the system to choose one for you.
• Combine the best parts of different attempts. Keep the entrance from one version, the confrontation from another, a passage from a third, and generate only the connective writing needed to make those choices work together.
• Change a major story decision and repair the consequences. Move a reveal. Change who knows a secret. Remove an event. Alter a choice. Then inspect what earlier and later scenes depended on the old version and repair the affected material.
• Rebuild a sequence. Replace a weak run of scenes with a new dramatic progression while preserving the facts, passages, starting conditions, ending conditions, or outcomes that still need to survive.
• Rewrite a character across the draft. Change not just dialogue but choices, tactics, behavior, presence, relationships, and how other characters respond, while protecting story facts that should remain unchanged.
• Turn notes into coordinated revisions. Apply a small note locally or let a larger note produce related changes across scenes. Conflicting or unresolved notes can remain visible rather than being silently flattened into a rewrite.
• Run creative passes. Work specifically on subtext, tension, visual action, dialogue, exposition, compression, character behavior, rhythm, or another declared creative direction.
• Recover earlier writing. Find useful material from an older revision and either restore it or adapt it to the screenplay as it exists now.
• Investigate before rewriting. Ask where a story problem actually begins, whether a reveal happens too early, what depends on a scene you want to cut, whether a payoff has enough setup, whether two characters sound alike, or why a scene is not producing the intended dramatic effect.
• Hear the script. Turn screenplay dialogue into ordered table-read material with character voice mapping and pluggable speech synthesis.
• Compare before committing. Inspect screenplay changes, structural differences, reports, candidate pages, and PDFs before choosing what belongs in the accepted draft.
• Export screenplay PDFs and perform mechanical submission checks. Render candidate or accepted pages, inspect the resulting PDF, and run dated submission-oriented checks without pretending that a mechanical check replaces reading the screenplay.

The fount repo above has handoff docs for unfinished features, but there’s a superseding, more ambitious set of planned features in an complete implementation docset that you can use here:

Have fun.