Primary data flow

InspirationsFeaturesSolutionsScenesProducts

graph LR
  Inspirations --> Features --> Solutions --> Scenes --> Products

Schema

graph LR
  Inspirations --> Features --> Solutions --> Scenes --> Products
  Characters --> Scenes
  Locations --> Scenes
  Tensions -.-> Features
  bible[Bible Passages] --> Features

Inspirations and features

It is important to distill inspirations into features and avoid directly applying inspirations to story content.

Inspirations are complex ideas.

Every inspiration has elements that don’t fit in Marloth, be they noise, distractions, out-of-scope, or bad.

Features and solutions

I’ve vacillated back and forth in how to structure the nested layers of content elements and motivation.

I’ve mostly settled on the following structure.

graph LR
  Features --> Solutions1[High-level<br/>Solutions] --> Solutions2[Mid-level<br/>Solutions] --> Solutions3[Low-level<br/>Solutions] --> Scenes
  Solutions1 --> Scenes
  Solutions2 --> Scenes

Features are mostly flat (though I have some residue of nested features).

Solutions have N* depth.

Features are intended to be high-level