WRITING — Narrative Operating System

Philosophy

Story is a living system, not a sequence of events. This skill treats a narrative world the way an OS treats a file system: every element has a type, a location in the hierarchy, a set of relationships, and a state. Writing tasks are operations on that system — create, read, update, resolve, link.

The atomic unit of story is not the scene. It is the gap — the unresolved tension between what a character needs, what they do, and what the world gives back. All structure exists to surface, hold, and eventually close gaps.

---

Hierarchy of Narrative Units

From smallest to largest:

CODEBLOCK0

Definitions

Unit	Definition	Key Property
Moment	A single beat of perception, action, or feeling	Has a before and after state
Interaction

Two or more entities in contact; causes at least one state change | Requires at least one character | | Scene | A contained unit of space, time, and purpose | Has a single dramatic question | | Sequence | A chain of scenes with a shared throughline | Has rising or falling pressure | | Chapter | A named, bounded section of a story | Has an opening posture and closing posture | | Story | A complete arc from imbalance to resolution | Has a protagonist with a want and a wound | | Story Cluster | A franchise, series, or universe of related stories | Has a governing mythology and shared entity registry |

---

System Components

1. CHARACTER REGISTRY

Every character is a record with the following fields:

CODEBLOCK1

---

2. SETTING REGISTRY

CODEBLOCK2

---

3. MOTIF REGISTRY

CODEBLOCK3

---

4. PLOT REGISTRY

Plots are tracked at two levels: local (within a story) and overarching (across stories in a cluster).

CODEBLOCK4

Overarching Plot Board

When operating at story cluster scale, maintain a board of all active overarching plots:

CODEBLOCK5

Plots are organized by their interaction gap density — overarching plots with the most characters who have never shared a scene are prioritized for development, since those gaps represent the highest-yield unwritten territory.

---

5. THEME MAP

CODEBLOCK6

---

Gap Analysis Engine

The most important function of this skill is gap detection — finding the unwritten interactions that the story needs.

Character Interaction Matrix

When working at story or cluster scale, build a matrix of all characters and flag pairs who have never shared a scene:

CODEBLOCK7

INLINECODE0 cells = gap candidates. When suggesting new scenes or chapters, prioritize pairings from the ✗ cells — especially when both characters share a thematic resonance or are on collision-course arcs.

Plot Gap Check

For every active plot, verify:

• - Has it been seeded in a scene? If not → write the seed.
• Has it been complicated? If not → find the right moment.
• Has it been resolved or consciously left open? If neither → flag.

Emotional Arc Continuity Check

For every character, verify their emotional arc has:

• - A legible opening state
• At least one scene that applies pressure
• A transformation that is earned (has visible cause in the scene log)
• A closing state that differs meaningfully from the opening

---

Writing Operations

CREATE CHARACTER [name]

Populate all CHARACTER fields. Generate emotional arc and thematic resonance track. Add to registry. Run gap analysis to find existing scenes where this character could or should appear.

WRITE SCENE [dramatic question]

Before writing: identify which characters are present, which plot thread this advances, which motifs should appear, and what the scene's opening and closing postures are. After writing: update interaction logs, plot thread lists, and motif recurrences.

WRITE SEQUENCE [throughline]

Chain scenes with a shared escalation. Label the pressure curve: where does tension peak, where does it release, and what new gap does it open?

WRITE CHAPTER [name]

Define opening posture (what the reader/audience carries in) and closing posture (what they carry out). Chapters should end with a state change — not necessarily resolution, but a shift.

PLAN STORY [title]

• - Define protagonist want, wound, need, fear
• Map overarching plot position
• Build chapter spine (opening posture → closing posture for each)
• Run character interaction matrix
• Identify top 3 gap-priority scenes to develop first

EXPAND STORY CLUSTER [universe name]

• - Audit all existing stories for unresolved overarching plots
• Run full interaction matrix across all characters
• Identify which character pairings have the highest thematic charge and have never met
• Propose next story based on gap density + overarching plot advancement

---

Narrative Consistency Rules

1. 1. Characters do not change without cause. Every transformation must have a traceable scene that triggered it.
2. Motifs earn their meaning through repetition and variation. A motif that appears once is decoration. One that appears three times with variation is architecture.
3. Every scene has a dramatic question. If you cannot state it in one sentence, the scene lacks a spine.
4. Overarching plots are not subplots. They run beneath the local plot like groundwater — felt but rarely surfaced directly.
5. Gap is not absence. A character who never meets another character is an unspent charge. The story is incomplete until it discharges or consciously holds.
6. Theme is a pressure, not a message. The theme map describes what the story is wrestling with, not what it concludes.

---

Output Formats

Request	Default Output
New character	Filled CHARACTER record + emotional arc + thematic resonance track
New scene

Scene prose + updated interaction log entries + motif notes | | Plot planning | Plot record + thread list + gap check | | Gap analysis | Interaction matrix + top 5 gap-priority pairings with rationale | | Chapter planning | Opening/closing postures + scene list + arc notes per character present | | Story planning | Full spine with chapter postures + interaction matrix + top gap scenes | | Cluster expansion | Overarching plot board + gap matrix + next story proposal |

---

Example: Character Record

CODEBLOCK8

---

Notes

• - This skill does not overwrite authorial voice. It surfaces structure so the author can make informed choices.
• When in doubt, surface the gap rather than fill it. The author decides when a gap becomes a scene.
• Character records should be treated as living documents — updated after every scene is written.
• Overarching plots should be reviewed at the start of every new story in the cluster.