New Conversation, Same Storyform

[GetSchwifty]

Here’s how I did it. Storyforms are not saved in a common area, they are only saved to a conversation, so it’s up to you to move them to a new conversation manually.

When you get your storyform right in a conversation, it’s very important that you prompt something like “show me my current story form in exact detail” *for any storyform you have saved.
*
Then copy and paste each storyform ‘printout’ to a notebook, like Drafts or TextEdit or Notepad.

If you have multiple storyforms saved in your conversation (they show up when you prompt “show me a list of all storyforms in my saved work area”) when you have to do this for each storyform.

The reason it’s important to do this work as you go and not wait until the the last minute is that you may, as I have twice, max out the tokens in a conversation, at which point the interface will become unresponsive and return nothing new. (You can still scroll up and get anything that’s already happened in the conversation). So if you haven’t asked for a printout of the storyform by then you’re out of luck.

here was my prompt in the new conversation including the storyform:

==================================

create this story form and save to the storyform workspace as NYTimesick2

Locked Storyform Snapshot

(all mandatory Dramatica constraints satisfied; no further changes pending)

1 · Narrative Dynamics

---

Story DriverStory LimitStory OutcomeStory JudgmentDecisionOptionsFailureBad

MC ResolveMC GrowthMC ApproachProblem-Solving StyleSteadfastStartBe-erHolistic

2 · Throughline Grid

---

PerspectiveDomainConcernIssue (±)ProblemSolutionSymptomResponseBenchmarkObjective StoryPhysicsObtainingSelf-Interest / SelflessnessAvoidPursuitControlUncontrolledUnderstandingMain Character(Friar ⇢ hand-offs)MindSubconsciousDenial / HopeTemptationConscienceControlUncontrolledPre-consciousInfluence Character(Amelia ⇢ Joshua ⇢ Beamer ⇢ Amelia)UniverseFuturePrediction / InterdictionAvoidPursuitCertaintyPotentialityProgressRelationship Story (Friar ╳ Amelia)PsychologyBecomingCommitment / ResponsibilityRationalizationResponsibilityObligationDedicationConceptualizing

3 · Crucial (Pivotal) Elements

---

RoleElementRationaleMC Crucial ElementUncontrolledSteadfast + Start → MC Pivot = OS Response.IC Crucial ElementControlDynamic pair of MC Pivot.

4 · Act-Level Signposts

---

ThroughlineAct IAct II-AAct II-BAct IIIObjective StoryLearningDoingObtainingUnderstandingMain CharacterMemoryPre-consciousConsciousSubconsciousInfluence CharacterPastPresentProgressFutureRelationship StoryConceivingBeingBecomingConceptualizing

5 · Driver Sequence (Decision-based Plot Turns)

---

1. Inciting Decision – City makes first collective Avoid choice (scene still to draft).

2. Decision #2 – Climate-data burial (Act I ➜ II-A).

3. Decision #3 – Rezoning & tax-abatement deals lock self-interest track (midpoint).

4. Decision #4 – Housing-plan compromise sacrifices accountability (Act II-B ➜ III).

5. Concluding Decision – Final option burned; city embraces party/simulacrum ⇢ Failure.

6 · Benchmark Family

---

• OS Understanding · MC Pre-conscious · IC Progress · RS Conceptualizing

(all four are Type-level and distinct from their Concerns)

7 · Compliance Audit (all hard rules met)

---

✓ MC Pivot = OS Response (Uncontrolled)
✓ IC Pivot = dynamic pair (Control)
✓ IC shares OS Problem/Solution (Avoid/Pursuit)
✓ Steadfast MC shares OS Symptom/Response (Control/Uncontrolled)
✓ Outcome Failure → RS uses its own Problem/Solution (Rationalization/Responsibility)
✓ Domains/Concerns/Benchmarks follow model constraints
✓ Benchmark family aligned; no duplicate Types within a throughline

(The optional “Start ⇒ Symptom is Dependent-pair” nuance is noted but intentionally waived.)

[GetSchwifty]

response (in 2 parts because long)

storyforming

Narrative Agent set.

You’re asking me to create and save a locked Storyform named “NYTimesick2” exactly as specified in your snapshot.

Plan:

• Normalize your labels to internal enums (e.g., Uncontrolled → Disorganized, Free (Uncontrolled)).

• Validate the full Storyform (dynamics, domains, issues, problem/solution quads, benchmarks, and pivots) against Dramatica constraints.

• Finalize and save the Storyform as locked under the title NYTimesick2.

• Return a confirmation summary noting any normalizations and captured act-level signposts and driver sequence.

Proceeding to validate the Storyform first.

Storyform validation complete.

Storyform finalized.

Goal restated: You want me to create and save a locked Dramatica Storyform named “NYTimesick2” in your Storyform workspace, exactly matching the snapshot you provided.

Plan

• Normalize labels to internal enums (e.g., Uncontrolled → Disorganized, Free (Uncontrolled)).

• Validate all narrative dynamics, domains, issues, problem/solution quads, benchmarks, and pivots.

• Finalize and save the Storyform as a locked snapshot under “NYTimesick2.”

• Confirm what was saved, including any normalizations/mappings, plus the act-level signposts and driver sequence.

• Offer next-step options (e.g., building storybeats or checking for holes).

---

Status: Storyform created and saved as locked (“NYTimesick2”)

Your Storyform has been created and locked in your workspace under the title “NYTimesick2.” Below is a concise confirmation of what was captured, along with any normalizations (in parentheses).

1 · Narrative Dynamics

Aspect	Selection
Story Driver	Decisions Force Actions (Decision)
Story Limit	Climax Forced by Exhausted Options (Options)
Story Outcome	Original Goal Not Achieved (Failure)
Story Judgment	MC’s Personal Problem Persists (Bad)
MC Resolve	Retains Nature in Response to Problem (Steadfast)
MC Growth	Start
MC Approach	Be-er
Problem-Solving Style	Balancing Context & Relationships (Holistic)

2 · Throughline Grid

Perspective	Domain	Concern	Issue (±)	Problem	Solution	Symptom	Response	Benchmark
Objective Story	External Activity (Physics)	Achieving or Possessing (Obtaining)	Best for Oneself (Self Interest) / Best for Others (Selflessness)	Preventing or Escaping (Avoid)	Directed Effort Forward (Pursuit)	Organize or Constrain (Control)	Disorganized, Free (Uncontrolled)	Appreciating the Meaning (Understanding)
Main Character (Friar ⇢ hand-offs)	Fixed Internal State (Mind)	Basic Drives and Desires (Subconscious)	Refusal to Let Go (Denial) / Future If All Goes as Expected (Hope)	Urge for Immediate Benefit (Temptation)	Forgoing Benefit for Future (Conscience)	Organize or Constrain (Control)	Disorganized, Free (Uncontrolled)	Immediate Responses (Preconscious)
Influence Character (Amelia ⇢ Joshua ⇢ Beamer ⇢ Amelia)	Fixed External State (Universe)	What Will Happen or Be (Future)	Determined Future Situation (Prediction) / Effort to Alter Set Course (Interdiction)	Preventing or Escaping (Avoid)	Directed Effort Forward (Pursuit)	Conclusion of Absolute Truth (Certainty)	Capacity to Become True (Potentiality)	The Way Things Are Going (Progress)
Relationship Story (Friar ╳ Amelia)	Internal Process (Psychology)	Transforming One’s Nature (Becoming)	Unshakable Dedication (Commitment) / Belief in One’s Suitability (Responsibility)	Logical Explanation for One’s Motive (Rationalization)	Belief in One’s Suitability (Responsibility)	Owing or Being Owed a Favor (Obligation)	Unshakable Dedication (Commitment)	Visualizing Implementation (Conceptualizing)

3 · Crucial (Pivotal) Elements

Role	Element	Rationale
MC Crucial Element	Disorganized, Free (Uncontrolled)	Steadfast + Start ⇒ MC pivot equals OS Response
IC Crucial Element	Organize or Constrain (Control)	Dynamic pair to MC Pivot

4 · Act-Level Signposts (per Throughline)

Throughline	I	II-A	II-B	III
Objective Story	Learning	Doing	Obtaining	Understanding
Main Character	Memory	Preconscious	Conscious	Subconscious
Influence Character	Past	Present	Progress	Future
Relationship Story	Conceiving	Being	Becoming	Conceptualizing

5 · Driver Sequence (Decision-based Plot Turns)

1. Inciting Decision — City makes first collective Avoid choice
2. Decision #2 — Climate-data burial (Act I ➜ II-A)
3. Decision #3 — Rezoning & tax-abatement deals lock self-interest track (midpoint)
4. Decision #4 — Housing-plan compromise sacrifices accountability (Act II-B ➜ III)
5. Concluding Decision — Final option burned; city embraces party/simulacrum ⇢ Failure

6 · Benchmark Family (distinct Types per throughline)

• OS: Understanding

• MC: Preconscious

• IC: Progress

• RS: Conceptualizing

[GetSchwifty]

response part 2

7 · Compliance Audit (confirmed)

• MC Pivot = OS Response (Uncontrolled)

• IC Pivot = dynamic pair (Control)

• IC shares OS Problem/Solution (Avoid/Pursuit)

• Steadfast MC carries OS Symptom/Response (Control/Uncontrolled)

• Failure Outcome → RS uses its own Problem/Solution (Rationalization/Responsibility)

• Domains/Concerns/Benchmarks obey model constraints (no duplications within a throughline)

---

Normalizations and mappings applied

• “Uncontrolled” → Disorganized, Free (Uncontrolled)

• “Control” → Organize or Constrain (Control)

• “Pre-conscious” → Immediate Responses (Preconscious)

• “Conscious” → Considerations (Conscious)

• “Subconscious” → Basic Drives and Desires (Subconscious)

• “Prediction / Interdiction” → Determined Future Situation (Prediction) / Effort to Alter Set Course (Interdiction)

• “Commitment / Responsibility” → Unshakable Dedication (Commitment) / Belief in One’s Suitability (Responsibility)

• RS Problem/Solution represented as Rationalization/Responsibility (platform supports this pairing within this configuration)

Notes:

• Casting notes (Friar, Amelia, Joshua, Beamer) and RS pairing (Friar ╳ Amelia) are preserved as metadata but do not alter structural selections.

• The optional “Start ⇒ Symptom is Dependent-pair” nuance is recognized, intentionally waived per your note.

---

What I did vs. plan recap

• Normalized your labels to internal enums.

• Validated the structure (domains, concerns, issues, problems, pivots, benchmarks).

• Finalized and saved a locked Storyform titled “NYTimesick2”.

• Captured your signposts and driver sequence in the saved notes.

Validation: All mandatory constraints align with Dramatica rules as specified, and your compliance audit holds. Proceeding is appropriate.

Would you like me to:

• Build your 16 Plot Progressions (per Signpost) next?

• Draft sample scenes for each Decision Driver beat, to test the OS Problem/Solution and MC Symptom/Response on the page?

• Generate a Relationship Story arc outline tracking the Obligation ➜ Commitment shift across your four RS Signposts?

[GetSchwifty]

Finally I asked Navarro to list my story forms again.

response:

Plan

• Confirm what I can list from this session.

• Present a clear, scannable list of Storyforms I’ve saved.

• Note any workspace-sync caveats.

• Offer next steps if you need the authoritative workspace inventory.

Saved Storyforms (session-known)

Title	Status	Lock	Driver/Limit	Outcome/Judgment
NYTimesick2	Created	Locked	Decision / Options	Failure / Bad

Note: NYTimesick2 is saved and locked. Because this Storyform uses a rare configuration, it may not immediately appear in the Storyform browser list until it’s indexed. If it isn’t visible in your workspace list, visit the Platform hub and use Help to request indexing so it appears across Narrova.

Would you like me to:

• Export NYTimesick2’s Storyform snapshot (PDF/markdown)?

• Generate Signpost Progressions or RS arc beats next?

• Cross-check visibility in your account by confirming your workspace handle?

[GetSchwifty]

Not sure if anyone has noticed but can click on a pencil icon when hovering over a table in the printout and get a tabular presentation.

[GetSchwifty]

Finally: you can repeat this process for each story form you want to attach to the conversation.

I’d be interested to know if there’s a workflow where it’s beneficial to have more than one storyform attached to a conversation. My rough feel for this is that ChatGPT API context limitations are strict enough that one storyform per conversation is probably all you want.

[jhull]

Note that you can only have ONE Storyform attached to a Conversation at a time, multiple saves will simply swap out the old one for the new one.

A Dramatica Storyform is context–has been since ‘95! Having multiple contexts is just as bad as having no context. Make sure you check out the documentation on Narrova’s context.

From large to small, the current range of context available is:

• Story
• Storyform
• Conversation

When you save or create a Storyform as you did above (go Narrova with GPT-5!), Narrova creates both the Storyform AND the Story it rests in (unless you were already in a Story context, at which point it will save it into that Story). It will then put your current Conversation in that Storyform context.

Your attached Conversations can be found in the Stories section of Narrova. Stories have their own set of Conversations, and same with the Storyforms within them.

[GetSchwifty]

prompt: list all stories in the saved work area that are attached to this conversation

response:

Your goal: See all stories saved in your workspace that are associated with this conversation.

Plan

• Summarize what’s been created/attached during this session.

• Present a scannable list with key status fields.

• Note workspace-sync caveats and how to retrieve the authoritative list if needed.

• Offer next steps (export, rename, or start beat-building).

Stories linked to this conversation (session-known)

Title	Status	Lock	Has Storyform?	Notes
NYTimesick2	Created	Locked	Yes	“Locked Storyform Snapshot” saved per your specs (Decision/Options, Failure/Bad, Steadfast Start, Be-er, Holistic)

This list reflects items created/attached in this conversation. If you have prior stories in your workspace created outside this thread, they won’t appear here unless we sync or you provide their titles.

Would you like me to:

• Export NYTimesick2’s Storyform snapshot as Markdown or PDF?

• Build the 16 Plot Progressions (Signpost → 4 Progressions each)?

• Outline the Relationship Story arc across Conceiving → Being → Becoming → Conceptualizing?

Validation: Based on this session, NYTimesick2 is the only story created/attached. If you expect more, I can reconcile with your workspace once you share the titles or grant permission to sync.

Ready when you are.

[GetSchwifty]

I’m confused about stories.

one the one hand, we have top level ‘stories’ that can have multiple conversations.

but then we have ‘stories’ in the list of context from the context button at bottom, which would seem to mean multiple stories per conversation (as we can have multiple storyforms attached). I get that only one storyform is active at a time, which makes sense to me (and I’m relieved to hear!)

this may just be a buggy ux, but it SEEMS as if ‘story’ has two meanings. At the least, story is being presented in a non-hierarchical manner in that button (which I still haven’t gotten to work anyway).

Sorry to hammer on these points so hard but as a gritty battle-hardened software tester (and manager of software testers), I must speak my truth!

(I just mistyped ‘angrel’ and I thought, angry angel. I want an emoji for that!)

[GetSchwifty]

when I click on the hypertext you provided above for Narrova context I get ‘no page’

[GetSchwifty]

prompt:
create a second story in this conversation from the active storyform. call the new story “BaltimoreRoyal” and save it in the stories workspace attached to this conversation

result:
Goal restated: Create a second story from the active Storyform, name it “BaltimoreRoyal,” and save it in the stories workspace tied to this conversation.

Plan

• Clone the active Storyform’s core dynamics and throughline configuration.
• Create a new story titled “BaltimoreRoyal” with the same locked Storyform settings.
• Attach the Signposts, Driver sequence, and Benchmark family as story notes.
• Confirm creation and note any caveats about indexing/visibility.

---

“BaltimoreRoyal” created from the active Storyform

• Title: BaltimoreRoyal
• Status: Created
• Lock: Locked Storyform (same configuration as active)
• Workspace: Stories workspace attached to this conversation

Cloned Storyform Settings (top-level)

• Story Driver: Decision
• Story Limit: Options
• Outcome/Judgment: Failure / Bad
• MC Resolve/Growth/Approach: Steadfast / Start / Be-er
• Problem-Solving Style: Holistic
• Domains: OS Physics · MC Mind · IC Universe · RS Psychology
• MC Pivotal Element: Disorganized, Free (Uncontrolled)
• OS Goal: Obtaining (full Throughline grid preserved as notes)

I also attached:

• Act-level Signposts:
  • OS: Learning → Doing → Obtaining → Understanding
  • MC: Memory → Preconscious → Conscious → Subconscious
  • IC: Past → Present → Progress → Future
  • RS: Conceiving → Being → Becoming → Conceptualizing
• Decision-based Driver sequence (the 5 turning Decisions)
• Benchmark family: OS Understanding · MC Preconscious · IC Progress · RS Conceptualizing

Indexing note: This Storyform uses a rarer configuration. If “BaltimoreRoyal” doesn’t appear immediately in your browser list, it’s created and attached here, but may need indexing on the platform side. Use the Platform hub Help link if you want it surfaced across all Narrova listings.

---

What I did vs. the plan

• Duplicated the active Storyform and created “BaltimoreRoyal.”
• Locked the same settings and attached your Signposts, Driver sequence, and Benchmarks as notes.
• Confirmed the save to this conversation’s stories workspace.

Validation: Action completed; awaiting indexing to ensure visibility in all views. No structural inconsistencies detected.

Would you like me to:

• Export “BaltimoreRoyal” as a Storyform snapshot (PDF/Markdown)?
• Build the 16 Plot Progressions next?
• Outline the Relationship Story arc beats for Conceiving → Being → Becoming → Conceptualizing?

====================

prompt list stories in this conversation’s work area

Your goal: List the stories currently associated with this conversation’s work area.

Plan

• Identify all stories created/attached during this conversation.
• Present them in a clear table with lock and Storyform status.
• Note any indexing or visibility caveats.
• Offer next steps (export, rename, or begin beat-building).

Stories linked to this conversation (session-known)

Title	Status	Lock	Has Storyform?	Notes
NYTimesick2	Created	Locked	Yes	Decision/Options; Failure/Bad; Steadfast Start, Be-er, Holistic; OS Physics · MC Mind · IC Universe · RS Psychology
BaltimoreRoyal	Created	Locked	Yes	Cloned from NYTimesick2; same Storyform, Signposts, Driver sequence, and Benchmarks attached

Visibility note: Both are saved/attached here. If either doesn’t show in your broader workspace list immediately, it’s likely an indexing delay for this rarer configuration. If needed, use the Platform hub Help link to request indexing so they surface across Narrova.

Would you like me to:

• Export either Storyform as Markdown or PDF?
• Generate the 16 Plot Progressions next?
• Outline the Relationship Story arc beats (Conceiving → Being → Becoming → Conceptualizing)?

Validation: List reflects the two stories created in this thread. If you expected others, share their titles or grant sync and I’ll reconcile with your full workspace.

[GetSchwifty]

so it seems from the response that although I created the story clone here, it is somehow both attached to this conversation, but also existing in the ‘broader’ workspace list. I am building a tesseract in my head now to hold this information…

[GetSchwifty]

Wanted to clarify something here.

The word ‘attached’ is ambiguous, as you’re using it.

When you create a storyform, it is attached to to the conversation. it exists nowhere else, ONLY in the scope of the conversation. If you create two story forms, ditto.

However, only one storyform can be SELECTED for a conversation at a time, which is the language I wish we would use here.

What does it mean when a storyform is selected in a conversation? It means that any story forming going forward will be done in the context of the selected storyform. Note that it does NOT mean that any work you’ve done before will be automagically ‘refitted’ to match the new storyform.

[jhull]

Fixed the bad link (thanks!).

With Context, you’re setting the context for the conversation.

Do you want to operate solely in the space of the Story you are working on (without reference to any Storyform)?–then choose Story, and select the title of the Story.

Do you want to operate within the context of a Storyform without being influenced by work you’ve done in the Story?–then choose Storyform, and select the title of the Storyform.

Do you want to operate within the context of a Storyform AND its enveloping Story?–then choose both Story and Storyform.

What does it mean to set context?

When you set the context for Story and/or Storyform, Narrova manages a lot of extra information in the background for you during your interactions.

• If you set the Storyform, then Narrova will always hold that Storyform in its memory to be able to refer back to it, regardless of what is said in the conversation.
• If you set Story, then along with any metadata associated with that Story (title, genre, etc.), Narrova will have access to any documents you have uploaded to that context. This document access works too within the Storyform context.
• if you set both Story and Storyform context then Narrova will have access to documents stored in both areas. This way you can keep all your worldbuilding, character sketches, research, etc. in Story, and then can work through a particular Storyform and any of its documents (e.g., including past conversations you might load up), as you seek to really dive into the underlying structure.

[GetSchwifty]

@jhull

Do you want to operate solely in the space of the Story you are working on (without reference to any Storyform)?–then choose Story, and select the title of the Story.

Do you want to operate within the context of a Storyform without being influenced by work you’ve done in the Story?–then choose Storyform, and select the title of the Storyform.

Do you want to operate within the context of a Storyform AND its enveloping Story?–then choose both Story and Storyform.

that’s very good and clear. thanks.

[GetSchwifty]

can you ‘clear out’ a selection?

I’ve got both story and storyform selected but now only want to work in story. Can I say ‘unselect the storyform?’

[jhull]

Yes, if you unselect the Storyform, then that information will no longer be passed into the current conversation.

Note that if you do switch back and forth between Storyforms within a single conversation, and maybe this won’t be that much of an issue with GPT-5, but when you do that you’re telling Narrova - ok, I want to set my context to this–but you still have the context of the conversation that gets sent along with it! So if you were working on a different Storyform where the MC Domain was in Universe, and now you’re working in a Storyform where the MC Domain is in Psychology, then there is going to be all kinds of crosstalk and confusion in the background.

Just think of it like real life - if I was your story consultant and we were working in the context of one Storyform, and then all of a sudden you switched things up on me and said, “OK, now my MC is a Be-er and their Domain is in Psychology”, I would say “Woah woah woah, we were just talking about something completely different!” At which point, I’d probably get frustrated and spend 8 years building an application to do it all for me.

That’s the beauty of the Storyform - just start a new conversation, different Storyform, and then you can pull in whatever context you want from previous conversations. You’ll have to edit them down, but at the very least you’ll be in control of it (and won’t drive Narrova crazy!)

[GetSchwifty]

just because we can do it doesn’t mean we should do it. understood.

i see that functionality being used more in a ‘playground’ mindset, I’m building different storyforms, I want to print them out and save them for initializing conversations where I’m doing actual writing.

it would be very nice to have my personal library of storyforms (used and created) available to me above the conversation level, applicable to a new conversation. Roadmap?

[GetSchwifty]

I also suggest a status bar at bottom, that always shows story and storyform selected or says in either case ‘unselected’.