Inspect and edit story elements

Add in the right context #

Choose an available node type for the selected level of the story model and your permissions. Participants and dramatic evidence at Level 2 need an owning chapter. An empty node begins authoring without establishing an interpretation.

Author one progression manually #

Log in to MythOS and open an editable document. To start one, open Files, choose + (Create new file), enter a File name and choose Create. In Actions, use the Analytical chapters manager to select a chapter; if needed, add its season, episode and chapter with their + controls. No provider, model or generation session is needed. The embedded Hobbit example is a reading aid; it is not a document you can save edits into.

1. Choose a short passage from your work. Write the question it raises and identify one condition, obstacle, choice and immediate consequence.
2. Inspect the Seed and enter a logline for the document’s scope. In Storylines, create or select a storyline and give it a question, objective, stakes and cost.
3. In Actions, choose the analytical chapter and use + (Add actions node) to create the participants and supported states or actual phrases. Compose each phrase through its Grammatical links. Inspect the resulting clause before using it as evidence.
4. Open Action frames, choose New action frame, enter a name and Add. Select the Action frame in List all. Assign existing evidence to its checkpoints, using the checkpoint controls described below; leave unsupported checkpoints empty.
5. In the storyline’s stage list, assign that Action frame to the stage answering your question. Open Story stages to inspect the resulting rail, then follow each evidence reference.
6. Check save feedback and reopen the changed fields. You are done with this first pass when the question, Action frame and evidence agree—or the remaining uncertainty is explicit.

For an existing story, reuse participants and occurrences already recorded. See incoming connections and Action frame editing for the detailed controls.

Edit fields and relationships #

Edit supported text, actor/state kinds and structured clauses. Within the Seed, change relationship role labels and select the actors filling them. Check both role and actor before changing a reference. Renaming does not create another relationship or actor.

Seed tone opens through Mood; relationship coordinates share the role submenu. Names and four emotion coordinates describe intentions. Sliders save on release or keyboard change; one gesture is one undoable edit. Failed edits retain drafts with Retry.

Choose catalog meaning deliberately #

Coordinates select named values on applicable axes; canvas position is separate. Read catalog meanings before choosing. Retry an unavailable catalog rather than guessing.

Use the axis inventory and the action illustration. Coordinates are not quality ratings.

Edit incoming connections #

Inspectors collect incoming connections under Upstream links, with Grammatical links separate. Use +, choose a kind where offered, and select an existing source. Each kind has required fields; incomplete drafts stay local. Edit an outgoing connection from its receiving node.

Actors edit contextual facets here: choose upstream context, write a claim, and optionally select evidence. Context explains what the facet concerns; evidence supports the claim. Storyline objective targets can be states or phrases, stakes and failure mode use projected outcomes, cost accepts any of those, and target states use states.

Removing grammar preserves the participant. Automatic connections are not another set of editable links.

Edit Action frames and checkpoint evidence #

Open Action frames from the overview or Story stages. List all shows names; select one for Edit selected. New action frame needs a name and Add. Fields save independently; switching views preserves drafts. Delete removes the Action frame, assignments and checkpoint bindings after confirmation, while preserving evidence nodes.

Assign existing Action frames in storyline stage lists. Move up and Move down change order within a stage; removing an assignment leaves other uses intact.

Checkpoint rows select an Action frame, required checkpoint and evidence. Each checkpoint holds at most one phrase or state; either type can be reused. Replacing occupied evidence needs confirmation. A resolved dialectic mismatch is advisory and does not retag evidence. Chronology conflicts remain drafts with an explanation. Removing one binding leaves other uses intact.

Manually empty checkpoints may have optional explanations. Generated missing-evidence gaps require explanations. Both indicate that no evidence is assigned. An intentionally open checkpoint is a valid way to preserve a limit in the interpretation; filling every checkpoint is not an authoring requirement.

Understand the automatic graph overview #

Active Level 0 nodes supply the Seed. A Theme receives an automatic Seed connection when it has authored Authorial intent or Audience input; a Setting requires Creation context or Audience input. Storylines connect through authored Theme and Setting roles rather than directly from Seed.

The canvas simplifies redundant paths; authored links remain in incoming inspectors. Actor and storyline participation follows explicit connections. The Action frames overview does not create stage assignments or supply context. Change the underlying authored relation rather than deleting an automatic projection.

For screenwriters: edit shots and emotions #

Use a line’s three-dot menu to create or inspect a shot. On its first line, ↑ grows upward and ↓ shrinks its start; on its last, ↓ grows downward and ↑ shrinks its end. Growth includes one adjacent unassigned line, even empty. One-line shots cannot shrink. A line belongs to at most one shot. Enter adds a line; Delete line removes one except the scene’s final line. Delete shot preserves its lines.

In Upstream links, use +, select Phrase or State, then a target. Valid complete selections save automatically. Remove disconnects the row. Each shot/target pair is unique, while either can have several connections.

Audience experiences lists emotions with names, four sliders and Remove emotion. Edits save automatically; failures offer Retry. Removing the last emotion leaves the experience unknown. Incoming transition is read-only and follows adjacent shots in episode presentation order.