Phase 3J developing help system format.

PlotLine/Help/Articles/Characters/AttributeHistory.md

@@ -11,27 +11,34 @@ screenshot:
 
 # Overview
 
-Attribute History captures changes to a character that occur through the story. It is useful for injuries, disguises, emotional states, social status, possessions, abilities or any other tracked trait.
+Attribute History captures changes to a character that become true at a point in the story. It is useful for injuries, disguises, emotional states, social status, abilities, public reputation or any other tracked trait that affects later scenes.
 
-# When Should I Use This?
+Use it when the change needs to remain true after the scene where it happens. If an injury, disguise, recovery or revealed trait affects later chapters, record the moment it becomes true.
-
-Use it when a change needs to remain true after the scene where it happens. If an injury, disguise or revealed trait affects later chapters, record it.
 
 # How To Use It
 
-Review attribute entries in scene order. Use the linked scene to check whether the change is introduced clearly and whether later scenes respect it.
+Review attribute entries in story order. Use the linked scene to check whether the change is introduced clearly and whether later scenes respect it.
+
+# Understanding the Fields
+
+| Field | What it means | Example |
+| --- | --- | --- |
+| Attribute type | The kind of trait being tracked. | Injury, disguise, status, appearance, ability. |
+| Attribute value | The specific state that becomes true. | "Broken wrist", "using a false name", "publicly disgraced". |
+| Effective scene | The scene where the value becomes true. | The warehouse fight where the wrist is broken. |
+| Description | Why the attribute changed or how it should affect later scenes. | "Cannot climb easily until recovery is shown." |
 
 # Example
 
-If Rebecca injures her hand in Chapter 8, later scenes should not show her playing piano easily unless the story accounts for recovery. Attribute history helps catch that.
+If Rebecca injures her hand in Chapter 8, later scenes should not show her playing piano easily unless the story accounts for recovery. Attribute History helps catch that.
 
 # Writer Tip
 
-Record the first moment a change becomes true, not every scene where it remains true.
+Record the first moment a change becomes true, not every scene where it remains true. Add another entry when it changes again, such as recovery, disguise removal or status reversal.
 
 # Common Mistakes
 
-- Tracking minor details that never affect the story.
+- Tracking tiny details that never affect the story.
 - Forgetting to add an attribute event when a visible condition changes.
 - Mixing author planning notes with in-story changes.
 - Leaving recovery or reversal moments unrecorded.

PlotLine/Help/Articles/Characters/CurrentRelationships.md

@@ -1,40 +1,48 @@
 ---
 title: Current Relationships
 category: Characters
-tags: characters, relationships, current-state, history
+tags: characters, relationships, current-state, history, continuity
 contextKey: characters.currentRelationships
-micro: See the latest calculated relationship state after story events have been applied.
+micro: See the latest relationship state after story events have been applied.
 quickTitle: What are Current Relationships?
-quickSummary: Current Relationships show where each relationship has ended up so far, based on the initial state and later relationship events.
+quickSummary: Current Relationships show where each relationship stands now, based on the initial baseline and later relationship events.
 screenshot:
 ---
 
 # Overview
 
-Current Relationships show the latest known state between this character and others. They are calculated from the initial relationship plus relationship events in story order.
+Current Relationships answer the writing question: "Where does this relationship stand now?" The section starts from the initial relationship and then applies relationship events in story order.
 
-# When Should I Use This?
+Use it before writing scenes that depend on trust, tension, loyalty, fear, attraction, betrayal or reconciliation. It helps you avoid writing two characters as friendly if the last recorded event left them estranged.
-
-Use this section when you need a quick answer to "Where does this relationship stand now?" It is especially useful before writing scenes with emotional tension, betrayal, reconciliation or reveal fallout.
 
 # How To Use It
 
-Read the current state first, then open View History when you need the sequence that led there. Use the links to open the related character or relationship evolution page for deeper checking.
+Read the current state first, then open View History when you need to understand how the relationship arrived there. Use the related character and relationship evolution links when you need more context.
+
+Current Relationships are not a place to erase the past. They are a summary of the latest position, while the history remains visible underneath.
+
+# Understanding the Fields
+
+| Field | What it means | Example |
+| --- | --- | --- |
+| Current state | The latest relationship state after the initial baseline and later events. | Estranged, trusted, suspicious, reconciled. |
+| Confidence / intensity | The current emotional strength, certainty or pressure in the relationship. | A quiet friendship may be 4; active hatred may be 9. |
+| View History | The sequence of initial state and events that produced the current state. | Initial trust, betrayal in Chapter 12, guarded alliance in Chapter 18. |
 
 # Example
 
-Rebecca may begin as a friend, become estranged after a discovery, and later reconcile. Current Relationships should show the latest state while preserving the earlier turns in history.
+Two friends may begin with deep trust, fall out after a false accusation, then slowly rebuild an alliance. Current Relationships should show the latest state, while View History preserves the turns that made the current scene believable.
 
 # Writer Tip
 
-If the current state surprises you, that is useful. It may reveal either an exciting story turn or a missing relationship event.
+If the current state surprises you, pause before editing it. The surprise may reveal a missing event, an accidental contradiction, or a useful emotional consequence you had forgotten.
 
 # Common Mistakes
 
-- Expecting current state to overwrite history.
+- Editing the initial relationship to force the current state.
 - Forgetting that current state depends on story order.
-- Adding a new initial relationship when the change should be an event.
+- Ignoring intensity when the relationship is emotionally important.
-- Ignoring relationship confidence or intensity when emotion matters.
+- Adding a new relationship when a relationship event would better explain the change.
 
 # Related Guides
 

PlotLine/Help/Articles/Characters/Details.md

@@ -1,43 +1,56 @@
 ---
 title: Character Details
 category: Characters
-tags: characters, cast, profile, continuity
+tags: characters, cast, profile, relationships, continuity
 contextKey: characters.details
 micro: Review one character's profile, relationships, appearances, attributes and knowledge in one place.
 quickTitle: What is Character Details?
-quickSummary: The Character Details page gathers the continuity record for a single character so you can see who they are, where they appear and what changes around them.
+quickSummary: The Character Details page gathers everything known about one character so you can check continuity, prepare scenes and see how the story has changed them.
 screenshot:
 ---
 
 # Overview
 
-Character Details is the working record for one character. It brings together profile information, relationships, scene appearances, attribute changes and knowledge so you can understand the character as they exists across the story rather than only inside one scene.
+Character Details is the continuity record for one person in your story. It gathers the character's profile, relationships, scene appearances, changing attributes and knowledge so you can see the character as a living part of the manuscript, not only as a name in a cast list.
 
-# When Should I Use This?
+Use this page when you are about to write or revise a scene involving the character, when you need to check whether a relationship still makes sense, or when you want to confirm what the character knows at this point in the book or series.
 
-Use this page when you are checking continuity, revising a character arc, preparing a scene that features the character, or asking whether their relationships and knowledge still make sense at a particular point in the story.
+# Main Sections
+
+| Section | What it helps you check |
+| --- | --- |
+| Profile | Basic reference details such as short name, age, appearance and story importance. |
+| Initial Relationships | The starting point for bonds, secrets, rivalries and family ties before scenes change them. |
+| Current Relationships | Where those relationships stand now after later relationship events. |
+| Relationship Events | The scene moments that changed, revealed or intensified a relationship. |
+| Scene Appearances | The scenes where the character appears and what role or state they had there. |
+| Attribute History | Time-sensitive details such as injury, disguise, status, condition or other traits that change. |
+| Knowledge | What the character knows, believes, discovers, suspects or misunderstands. |
 
 # How To Use It
 
-Start with the profile for identity details, then move through relationships, appearances, attribute history and knowledge. Open linked scenes when you need to inspect the surrounding narrative context. Use the relationship and knowledge sections as continuity checks before major revisions.
+Start with the section that matches your writing question. If you are checking a scene, use Scene Appearances, Current Relationships and Knowledge. If you are planning a reveal, compare Initial Relationships, Relationship Events and Reader knowledge. If you are fixing a continuity warning, use Attribute History and linked scenes to find when a detail became true.
+
+This page is especially useful across a series, where a character may carry injuries, secrets, assumptions or emotional fallout from one book into another.
 
 # Example
 
-Before rewriting a reveal scene, open Beth's character record and check her recent appearances, what she already knows, and how her relationship with Rebecca has changed. This helps prevent the scene from contradicting earlier material.
+Before writing a confrontation, open the character's details and check whether they already know the secret, whether the reader knows it, and how their relationship with the other character has changed since the beginning. That prevents a scene from accidentally giving a character impossible knowledge or ignoring a previous betrayal.
 
 # Writer Tip
 
-Treat this page as a continuity lens, not a biography form. The most useful entries are the ones that explain how the story changes what the character knows, feels or can do.
+Treat this page as a story memory. It does not need every biographical fact, but it should capture the details that would cause a continuity problem if they were forgotten.
 
 # Common Mistakes
 
-- Updating profile notes but forgetting scene appearances.
+- Updating profile notes but forgetting the relationship or knowledge change that caused the new situation.
-- Treating relationship history as static.
+- Treating current relationship state as a replacement for earlier history.
-- Recording private author knowledge as if the character already knows it.
+- Recording author-only secrets as if the character already knows them.
-- Ignoring small attribute changes that matter later.
+- Ignoring small attribute changes, such as injury or disguise, that matter in later scenes.
 
 # Related Guides
 
 - [Characters](/Help/Article/characters.overview)
+- [Initial Relationships](/Help/Article/characters.initialRelationships)
 - [Scene Appearances](/Help/Article/characters.sceneAppearances)
 - [Knowledge](/Help/Article/characters.knowledge)

PlotLine/Help/Articles/Characters/Edit.md

@@ -0,0 +1,36 @@
+---
+title: Create or Edit a Character
+category: Characters
+tags: characters, profile, cast, planning
+contextKey: characters.edit
+micro: Add or update a character's basic reference details and planning visibility.
+quickTitle: What is this character form?
+quickSummary: The character form captures the core reference details for a cast member, plus planning settings such as story importance.
+screenshot:
+---
+
+# Overview
+
+Use this form to create a new character or update the basic reference details for an existing one. This is the place for stable profile information: name, short name, age, description and other details you want available across the project.
+
+# What Belongs Here
+
+Use the profile fields for information that describes the character generally. Use the Character Details page for information that changes through the story, such as relationships, scene appearances, attribute history and knowledge.
+
+# Understanding the Fields
+
+| Field | What it means | Example |
+| --- | --- | --- |
+| Story importance | How central the character is to the project structure. | Major for a protagonist, secondary for a recurring ally, minor for a brief witness. |
+| Show in quick add bar | Whether the character appears as a shortcut in planning tools. | Useful for characters you add to scenes often. |
+| Default description | A general reference note, not a scene-specific state. | "A careful solicitor with a dry sense of humour." |
+
+# Writer Tip
+
+Keep this form stable. If a detail changes because of a scene, record that change in the relevant story section rather than rewriting the general profile.
+
+# Related Guides
+
+- [Characters](/Help/Article/characters.overview)
+- [Character Details](/Help/Article/characters.details)
+- [Attribute History](/Help/Article/characters.attributeHistory)

PlotLine/Help/Articles/Characters/Fields/Awareness.md

@@ -0,0 +1,16 @@
+---
+title: Relationship Awareness
+category: Characters
+tags: characters, relationships, secrets, fields
+contextKey: characters.relationships.awareness
+micro: Track who knows about the relationship or understands its true nature.
+quickTitle: Awareness
+quickSummary: Use awareness for secrets, mistaken identities, hidden ties, concealed affairs or relationships the reader does not yet understand.
+screenshot:
+---
+
+# Awareness
+
+Awareness explains who knows about the relationship or understands its true nature. Use it when the story truth and the characters' understanding are not the same.
+
+This is useful for hidden family ties, concealed affairs, undercover roles, mistaken identities, secret hostility or relationships the reader does not yet understand.

PlotLine/Help/Articles/Characters/Fields/ConfidenceIntensity.md

@@ -0,0 +1,16 @@
+---
+title: Confidence / Intensity
+category: Characters
+tags: characters, relationships, emotion, fields
+contextKey: characters.relationships.confidenceIntensity
+micro: Set how strong, certain or emotionally charged this relationship is.
+quickTitle: Confidence / intensity
+quickSummary: Use low values for weak or uncertain connections and high values for powerful trust, hatred, fear, loyalty or emotional weight.
+screenshot:
+---
+
+# Confidence / Intensity
+
+Set how strong, certain or emotionally charged the relationship is. Intensity can be positive or negative.
+
+Low values fit distant, uncertain or barely established connections. Middle values fit relationships that are known but not emotionally dominant. High values fit strong bonds, deep trust, intense hatred, powerful fear or major emotional weight.

PlotLine/Help/Articles/Characters/Fields/InitialBook.md

@@ -0,0 +1,16 @@
+---
+title: Initial Book
+category: Characters
+tags: characters, relationships, books, fields
+contextKey: characters.relationships.initialBook
+micro: Choose where this relationship baseline begins.
+quickTitle: Initial book
+quickSummary: Choose the earliest book where this starting relationship matters.
+screenshot:
+---
+
+# Initial Book
+
+Choose where this relationship baseline begins. Use the earliest book where the starting relationship matters.
+
+If the relationship exists from the start of the project, choose the first book or leave the baseline at the project start, depending on the form option available.

PlotLine/Help/Articles/Characters/Fields/ReaderInitiallyKnows.md

@@ -0,0 +1,16 @@
+---
+title: Reader Initially Knows
+category: Characters
+tags: characters, relationships, reader-knowledge, secrets, fields
+contextKey: characters.relationships.readerInitiallyKnows
+micro: Mark whether the reader knows this relationship at the starting point.
+quickTitle: Reader initially knows
+quickSummary: Untick this for hidden family ties, secret affairs, concealed identities, false assumptions or delayed reveals.
+screenshot:
+---
+
+# Reader Initially Knows
+
+This controls whether the reader knows the relationship at the starting point. It is about reader knowledge, not whether the relationship is true.
+
+Untick it for hidden family ties, secret affairs, concealed identities, false assumptions or delayed reveals. Keep it ticked for relationships the reader is meant to understand from the start.

PlotLine/Help/Articles/Characters/Fields/Reciprocal.md

@@ -0,0 +1,16 @@
+---
+title: Reciprocal Relationship
+category: Characters
+tags: characters, relationships, fields
+contextKey: characters.relationships.reciprocal
+micro: Decide whether PlotWeaver should create the reverse relationship too.
+quickTitle: Reciprocal
+quickSummary: Turn this on when the reverse connection should also exist, such as parent and child, siblings or friends.
+screenshot:
+---
+
+# Reciprocal
+
+Reciprocal tells PlotWeaver to create the reverse relationship too. If Annie is Beth's parent, Beth is Annie's child.
+
+Use this for relationships where both directions should be tracked. Turn it off when the connection is one-sided, secret, unequal or should be handled separately.

PlotLine/Help/Articles/Characters/Fields/RelatedCharacter.md

@@ -0,0 +1,16 @@
+---
+title: Related Character
+category: Characters
+tags: characters, relationships, fields
+contextKey: characters.relationships.relatedCharacter
+micro: Choose the other character involved in this relationship.
+quickTitle: Related character
+quickSummary: Pick the other character in the relationship you are describing.
+screenshot:
+---
+
+# Related Character
+
+Choose the other character involved in this relationship. If you are viewing Annie Fletcher and choose Beth, you are describing Annie's relationship to Beth.
+
+Use the relationship type, awareness and notes fields to explain what that connection means.

PlotLine/Help/Articles/Characters/Fields/RelationshipNotes.md

@@ -0,0 +1,16 @@
+---
+title: Relationship Notes
+category: Characters
+tags: characters, relationships, notes, fields
+contextKey: characters.relationships.notes
+micro: Add hidden history, author-only context or nuance that dropdowns cannot capture.
+quickTitle: Notes
+quickSummary: Use notes for hidden history, uncertainty, emotional nuance or writer-only context that does not fit the other fields.
+screenshot:
+---
+
+# Notes
+
+Use notes for hidden history, author-only context, uncertainty, emotional nuance or anything not captured by the dropdowns.
+
+Good notes explain why the relationship matters. For example: "The reader thinks they are strangers, but Annie is Beth's mother."

PlotLine/Help/Articles/Characters/Fields/RelationshipType.md

@@ -0,0 +1,16 @@
+---
+title: Relationship Type
+category: Characters
+tags: characters, relationships, fields
+contextKey: characters.relationships.relationshipType
+micro: Choose the kind of bond between the two characters.
+quickTitle: Relationship type
+quickSummary: Choose the kind of connection, such as family, friendship, romance, rivalry, authority, work, secrecy or hostility.
+screenshot:
+---
+
+# Relationship Type
+
+Choose the kind of bond between the two characters. This might be family, friendship, romance, rivalry, authority, professional role, secrecy or hostility.
+
+Pick the type that best explains how the relationship should be read in planning views and continuity checks. Use notes for nuance that does not fit the dropdown.

PlotLine/Help/Articles/Characters/Fields/StoryImportance.md

@@ -0,0 +1,16 @@
+---
+title: Story Importance
+category: Characters
+tags: characters, profile, fields, planning
+contextKey: characters.fields.storyImportance
+micro: Choose how central this character is to the project.
+quickTitle: Story importance
+quickSummary: Story importance helps separate major, secondary and minor characters in planning views.
+screenshot:
+---
+
+# Story Importance
+
+Choose how central this character is to the project. Use a higher value for protagonists, major antagonists and characters whose choices shape the story. Use a middle value for recurring supporting characters. Use a lower value for minor characters who appear briefly or mainly support a scene.
+
+This is a planning choice, not a judgement of how interesting the character is.

PlotLine/Help/Articles/Characters/InitialRelationships.md

@@ -1,43 +1,60 @@
 ---
 title: Initial Relationships
 category: Characters
-tags: characters, relationships, starting-state, continuity
+tags: characters, relationships, starting-state, secrets, continuity
 contextKey: characters.initialRelationships
 micro: Define how characters relate to each other before the story changes them.
 quickTitle: What are Initial Relationships?
-quickSummary: Initial Relationships describe the starting state between characters before later scenes create changes, reveals or reversals.
+quickSummary: Initial Relationships set the baseline for family ties, friendships, rivalries, secrets and other bonds before later scenes change or reveal them.
 screenshot:
 ---
 
 # Overview
 
-Initial Relationships record how characters begin. They are the baseline for later relationship events, current relationship state and future relationship map views.
+Initial Relationships describe the starting point between two characters. They answer the question: "What is true about these characters before the story changes it?"
 
-# When Should I Use This?
+Use this section for relationships that already exist at the beginning of the project, the beginning of a book, or before the character first appears. This includes obvious connections, such as parent, friend or employer, and hidden connections, such as a secret affair, concealed family tie, mistaken identity or undercover role.
 
-Use initial relationships for bonds that already exist at project start or before a character first appears. Family ties, old friendships, rivalries, debts, secrets and professional roles often belong here.
+# How This Helps Continuity
 
-# How To Use It
+The initial relationship becomes the baseline for current relationship state, relationship events and later continuity checks. If a scene changes trust, hostility, awareness or emotional intensity, that change should usually be recorded as a Relationship Event rather than by rewriting the initial relationship.
 
-Choose the related character, relationship type, awareness state and confidence or intensity. Add notes for hidden history or reader knowledge, especially when the relationship is true in the world but not yet known to the reader.
+Initial Relationships can also separate story truth from reader knowledge. The writer may know two characters are related long before the reader does.
+
+# Understanding the Fields
+
+| Field | What it means | Example |
+| --- | --- | --- |
+| Related character | The other character in this relationship. | If you are viewing Annie Fletcher, choosing Beth means you are describing Annie's relationship to Beth. |
+| Relationship type | The kind of bond or role between them. | Parent, friend, rival, employer, secret lover, suspect. |
+| Awareness | Who knows about the relationship or understands its true nature. | The writer knows Beth and Maggie are sisters before the reader does. |
+| Initial book | Where this relationship baseline begins. | Book 1 if the bond exists from the start; Book 2 if the character enters the series later. |
+| Confidence / intensity | How strong, certain or emotionally charged the relationship is. | 10 for devoted family or intense hatred; 2 for a weak acquaintance. |
+| Reciprocal | Whether PlotWeaver should also create the reverse connection. | If Annie is Beth's parent, Beth is Annie's child. |
+| Reader initially knows | Whether the reader knows this relationship at the starting point. | Untick for hidden family ties, secret affairs or delayed reveals. |
+| Notes | Extra context, hidden history or author-only explanation. | "The reader thinks they are strangers, but Annie is Beth's mother." |
+
+# When To Use Initial Relationships
+
+Use an initial relationship when the connection is already true before the relevant story action begins. Use a Relationship Event instead when the bond changes during a scene, becomes known to someone, or gains new emotional weight.
 
 # Example
 
-Maggie and Beth may begin as strangers to the reader, while the writer knows there is a hidden family connection. The initial relationship can capture the author-facing truth while later events handle the reveal.
+A detective and a suspect may begin as strangers in public, while the writer knows they had a private meeting years ago. The initial relationship can record the hidden past, Reader initially knows can stay off, and a later relationship event can mark the scene where the truth is revealed.
 
 # Writer Tip
 
-Initial does not mean permanent. It is the first marker on the relationship timeline.
+Be honest about the baseline. If the story is hiding something from the reader, do not hide it from your planning record; use the reader knowledge and awareness fields to track the secret cleanly.
 
 # Common Mistakes
 
-- Using initial relationships for changes that happen during scenes.
+- Adding duplicate relationships instead of editing the existing baseline.
-- Forgetting to mark whether the reader initially knows the relationship.
+- Using Initial Relationships for changes that happen inside scenes.
-- Recording only romantic or family bonds and missing professional or hostile ones.
+- Leaving Reader initially knows ticked for a secret relationship.
-- Duplicating a relationship instead of editing the existing baseline.
+- Treating intensity as only positive; hatred, fear and rivalry can also be intense.
 
 # Related Guides
 
 - [Current Relationships](/Help/Article/characters.currentRelationships)
 - [Relationship Events](/Help/Article/characters.relationshipEvents)
-- [Relationship Map](/Help/Article/relationshipMap.overview)
+- [Character Details](/Help/Article/characters.details)

PlotLine/Help/Articles/Characters/Knowledge.md

@@ -1,25 +1,32 @@
 ---
 title: Character Knowledge
 category: Characters
-tags: characters, knowledge, secrets, continuity
+tags: characters, knowledge, secrets, reveals, continuity
 contextKey: characters.knowledge
 micro: Track what this character learns, knows, suspects or misunderstands.
 quickTitle: What is Character Knowledge?
-quickSummary: Character Knowledge helps you separate what the writer knows from what a character knows at each point in the story.
+quickSummary: Character Knowledge helps you separate what the writer knows from what a character knows, believes, discovers or misunderstands.
 screenshot:
 ---
 
 # Overview
 
-Knowledge entries record what a character knows or believes as the story unfolds. This is vital for mysteries, secrets, betrayals, investigations and any plot where information arrives unevenly.
+Knowledge entries record what a character knows, believes, discovers, suspects or misunderstands as the story unfolds. This is vital for mysteries, secrets, betrayals, investigations and any plot where information arrives unevenly.
 
-# When Should I Use This?
+Use this section before writing decisions, confrontations, reveals or deductions. It helps prevent impossible knowledge, where a character acts on information they have not yet learned.
-
-Use it when a character learns something important, misunderstands something, gains evidence, recognises an asset, or becomes aware of a plot thread.
 
 # How To Use It
 
-Review knowledge in story order and open linked scenes when you need to check how information was gained. Use it before writing decisions, confrontations or reveals to confirm what the character can reasonably do.
+Review knowledge in story order and open linked scenes when you need to check how the information was gained. Pay attention to whether the entry is about story truth, character belief or reader understanding.
+
+# Understanding the Fields
+
+| Field | What it means | Example |
+| --- | --- | --- |
+| Knowledge state | How the character relates to the information. | Knows, suspects, believes incorrectly, discovers. |
+| Source scene | Where the character gains, changes or reveals the knowledge. | Beth finds the letter in Chapter 12. |
+| Linked asset or thread | The object, clue, secret or plot thread the knowledge concerns. | A missing ring, a murder clue, a family secret. |
+| Description | The practical writer-facing note about what the character can now think or do. | "Beth knows the letter exists but not who wrote it." |
 
 # Example
 
@@ -27,13 +34,13 @@ Maggie may know that a letter exists before she knows who wrote it. Those are di
 
 # Writer Tip
 
-Readers forgive mystery. They notice impossible knowledge. Track the difference carefully.
+Readers forgive mystery. They notice impossible knowledge. Track the difference between author truth, character belief and reader awareness carefully.
 
 # Common Mistakes
 
 - Letting a character act on information they have not learned.
 - Recording author-only secrets as character knowledge.
-- Forgetting suspicion or partial knowledge.
+- Forgetting suspicion, partial knowledge or false belief.
 - Treating all characters as if they know the same reveal at the same time.
 
 # Related Guides

PlotLine/Help/Articles/Characters/RelationshipEvents.md

@@ -1,43 +1,51 @@
 ---
 title: Relationship Events
 category: Characters
-tags: characters, relationships, events, evolution
+tags: characters, relationships, events, evolution, scenes
 contextKey: characters.relationshipEvents
 micro: Track scene-by-scene changes in how characters relate to each other.
 quickTitle: What are Relationship Events?
-quickSummary: Relationship Events record moments in scenes where a relationship changes, becomes known, intensifies or shifts direction.
+quickSummary: Relationship Events record scene moments where a relationship changes, becomes known, intensifies or shifts direction.
 screenshot:
 ---
 
 # Overview
 
-Relationship Events are the story moments that move a relationship forward or sideways. They preserve the path from initial relationship to current relationship without erasing earlier states.
+Relationship Events are the story moments that change a relationship. They explain how the story moves from the initial baseline to the current relationship state.
 
-# When Should I Use This?
+Use this section to review changes such as a confession, betrayal, rescue, discovery, argument, reveal, apology, alliance or power shift. A relationship event should be tied to the scene where the change happens.
-
-Use a relationship event when a scene changes trust, hostility, attraction, loyalty, awareness or emotional intensity between characters.
 
 # How To Use It
 
-Create events from scene relationship editing, then review them here in story order. Check the scene, relationship type, awareness, intensity and notes to make sure the change is clear and placed correctly.
+Scan the events in story order. Each entry shows the characters involved, the scene, the relationship type, the state or awareness change and the intensity. Open the scene when you need to check whether the event is visible on the page and whether later scenes respect it.
+
+# Understanding the Fields
+
+| Field | What it means | Example |
+| --- | --- | --- |
+| Scene | The moment in the story where the relationship changes. | Chapter 8, Scene 3: Beth discovers the lie. |
+| Relationship state | The new state created by the event. | Suspicious, allied, estranged, protective. |
+| Awareness | Whether the other character knows or understands the relationship change. | One character knows the betrayal; the other still believes the friendship is intact. |
+| Confidence / intensity | How strong or emotionally charged the change is. | A mild doubt might be 3; a devastating betrayal might be 10. |
+| Description | The writer-facing explanation of what changed and why. | "Beth trusts Annie less after seeing the hidden letter." |
 
 # Example
 
-If Beth protects Maggie in Chapter 17, that scene may create a relationship event from suspicion to trust. A later betrayal can add another event without deleting the earlier trust.
+If Beth protects Maggie in Chapter 17, that scene may move the relationship from suspicion to trust. If Maggie later learns Beth had a hidden motive, add another event rather than overwriting the earlier trust.
 
 # Writer Tip
 
-Not every interaction needs an event. Use them for changes the reader, plot or character arc will need to remember.
+Not every interaction needs an event. Add one when the relationship's future behavior, reader understanding or continuity depends on remembering the change.
 
 # Common Mistakes
 
 - Recording ordinary conversation as a relationship change.
 - Forgetting to link the change to the scene where it happens.
-- Using notes without setting the relationship state.
+- Using notes without choosing the relationship state.
-- Losing reciprocal meaning when both characters are affected differently.
+- Treating both directions of a relationship as identical when one character knows more than the other.
 
 # Related Guides
 
+- [Initial Relationships](/Help/Article/characters.initialRelationships)
 - [Current Relationships](/Help/Article/characters.currentRelationships)
 - [Scene Appearances](/Help/Article/characters.sceneAppearances)
-- [Relationship Map](/Help/Article/relationshipMap.overview)

PlotLine/Help/Articles/Characters/SceneAppearances.md

@@ -1,29 +1,36 @@
 ---
 title: Scene Appearances
 category: Characters
-tags: characters, scenes, appearances, continuity
+tags: characters, scenes, appearances, role, continuity
 contextKey: characters.sceneAppearances
 micro: See where a character appears and what role they play in each scene.
 quickTitle: What are Scene Appearances?
-quickSummary: Scene Appearances show every scene linked to this character, including role, presence and useful continuity notes.
+quickSummary: Scene Appearances show every scene linked to this character, including role, presence and useful continuity details.
 screenshot:
 ---
 
 # Overview
 
-Scene Appearances connect a character to the actual story structure. They help answer when a character appears, how long they have been absent and what physical or emotional state they carried into a scene.
+Scene Appearances connect the character to the actual story structure. They show where the character appears, what role they play and what scene-specific details may matter later.
 
-# When Should I Use This?
+Use this section during revision, pacing checks, continuity reviews and character arc work. It is especially helpful when a supporting character disappears for a long stretch, returns with important knowledge, or needs enough page presence to make a later payoff feel earned.
-
-Use this section during revision, pacing checks, continuity reviews and character arc work. It is also useful when planning whether a supporting character has enough presence to earn a later payoff.
 
 # How To Use It
 
-Scan the scenes in order. Open a scene from the list when you need to adjust role, presence, location, outfit, condition, emotional state or knowledge notes.
+Scan the appearances in story order. Open a scene when you need to adjust role, presence, location, outfit, condition, emotional state or knowledge notes.
+
+# Understanding the Fields
+
+| Field | What it means | Example |
+| --- | --- | --- |
+| Scene | Where the character appears in the book or series. | Book 1, Chapter 4, Scene 2. |
+| Role | The character's dramatic function in that scene. | POV character, supporting character, mentioned character. |
+| Presence | Whether the character is physically present, mentioned, remembered or otherwise involved. | A character can influence a scene without standing in the room. |
+| Scene details | Moment-specific notes such as outfit, condition or emotional state. | "Still limping after the warehouse injury." |
 
 # Example
 
-A detective may appear in five early scenes, disappear for eight chapters, then return with crucial knowledge. Scene appearances make that absence visible before it becomes confusing.
+A detective may appear in five early scenes, vanish for eight chapters, then return with crucial knowledge. Scene Appearances make that gap visible before readers forget the detective matters.
 
 # Writer Tip
 
@@ -32,7 +39,7 @@ Use appearance notes for scene-specific truth. General personality belongs in th
 # Common Mistakes
 
 - Mentioning a character in a summary but not linking them to the scene.
-- Forgetting current location when validation warns about placement.
+- Forgetting current location or condition when validation warns about continuity.
 - Using appearance notes for permanent biography details.
 - Ignoring long absences that weaken reader memory.
 

PlotLine/Help/Articles/StoryAssets/CurrentState.md

@@ -0,0 +1,21 @@
+---
+title: Story Asset Current State
+category: Story Assets
+tags: assets, state, location, resolved, continuity
+contextKey: storyAssets.currentState
+micro: Check the asset's current condition, location and resolution status.
+quickTitle: Current state
+quickSummary: Current State summarises the asset's importance, condition, location and whether its story purpose has been resolved.
+screenshot:
+---
+
+# Current State
+
+Current State gives a quick answer to where the asset stands now. It combines importance, condition or status, current location and resolution status.
+
+Use it before writing or revising a scene where the asset appears. If a letter is missing, a key is recovered or a weapon has already served its story purpose, this section should make that clear.
+
+# Related Guides
+
+- [Story Asset Details](/Help/Article/storyAssets.details)
+- [Events Across Scenes](/Help/Article/storyAssets.eventsAcrossScenes)

PlotLine/Help/Articles/StoryAssets/Custody.md

@@ -0,0 +1,25 @@
+---
+title: Story Asset Custody
+category: Story Assets
+tags: assets, custody, possession, continuity
+contextKey: storyAssets.custody
+micro: Track who possesses or controls an asset over time.
+quickTitle: Custody
+quickSummary: Custody helps you follow who has a letter, weapon, evidence folder, heirloom or other important asset at each point in the story.
+screenshot:
+---
+
+# Custody
+
+Custody tracks who possesses, controls or is responsible for the asset over time. This is useful for letters, weapons, evidence folders, heirlooms, keys, vehicles and any item where possession matters.
+
+Use it to avoid continuity errors. If a character gives away a document in Chapter 8, they should not still have it in Chapter 10 unless the story shows how it came back.
+
+# Example
+
+An evidence folder might begin with the police, pass to a solicitor, be stolen by a suspect and finally return to the protagonist. Custody tracking keeps that chain visible.
+
+# Related Guides
+
+- [Story Asset Details](/Help/Article/storyAssets.details)
+- [Events Across Scenes](/Help/Article/storyAssets.eventsAcrossScenes)

PlotLine/Help/Articles/StoryAssets/Dependencies.md

@@ -0,0 +1,25 @@
+---
+title: Story Asset Dependencies
+category: Story Assets
+tags: assets, dependencies, clues, continuity
+contextKey: storyAssets.dependencies
+micro: Show how one asset depends on another asset or state.
+quickTitle: Dependencies
+quickSummary: Dependencies track when one asset only works, matters or becomes available because another asset exists or reaches a state.
+screenshot:
+---
+
+# Dependencies
+
+Dependencies explain how assets rely on one another. A key may require a lock. Evidence may require a document. A clue may only become useful after another clue has been discovered.
+
+Use dependencies when the order matters. They help you see whether the story has prepared an asset before it is used, revealed or resolved.
+
+# Example
+
+A coded letter may be blocked until the cipher page is found. The letter and the cipher are separate assets, but the meaning of one depends on the other.
+
+# Related Guides
+
+- [Story Asset Details](/Help/Article/storyAssets.details)
+- [Story Assets](/Help/Article/storyAssets.overview)

PlotLine/Help/Articles/StoryAssets/Details.md

@@ -0,0 +1,39 @@
+---
+title: Story Asset Details
+category: Story Assets
+tags: assets, continuity, events, custody, dependencies
+contextKey: storyAssets.details
+micro: Review one asset's current state, dependencies, scene events and custody history.
+quickTitle: What is Story Asset Details?
+quickSummary: Story Asset Details shows how one important object, clue or document currently stands and how it has moved or changed through the story.
+screenshot:
+---
+
+# Overview
+
+Story Asset Details is the continuity record for one important object, clue, document or story item. It shows the asset's current state, where it is, whether it has been resolved, what it depends on, how it appears across scenes and who has custody of it over time.
+
+Use this page when revising clues, checking object movement, planning a reveal or confirming whether an important item has completed its story purpose.
+
+# Main Sections
+
+| Section | What it helps you check |
+| --- | --- |
+| Current state | The asset's importance, condition, location and resolution status. |
+| Dependencies | Other assets that must exist, be found or be in a certain state first. |
+| Events across scenes | The scenes where the asset appears, changes, is used or gains significance. |
+| Custody | Who possesses or controls the asset at different points in the story. |
+
+# Example
+
+A sealed evidence folder may begin in a police office, move to a character's flat, be opened in a later scene and become resolved once its role in the mystery is complete. This page lets you check that chain without hunting through every scene manually.
+
+# Writer Tip
+
+Use this page as a continuity checkpoint before reveals and handovers. If the asset matters to the plot, the reader should be able to follow where it came from and why it matters.
+
+# Related Guides
+
+- [Story Assets](/Help/Article/storyAssets.overview)
+- [Events Across Scenes](/Help/Article/storyAssets.eventsAcrossScenes)
+- [Custody](/Help/Article/storyAssets.custody)

PlotLine/Help/Articles/StoryAssets/Edit.md

@@ -0,0 +1,34 @@
+---
+title: Edit Story Asset
+category: Story Assets
+tags: assets, objects, clues, continuity, editing
+contextKey: storyAssets.edit
+micro: Define an important story object, clue or document and how it should be tracked.
+quickTitle: What is Edit Story Asset?
+quickSummary: Edit Story Asset captures the core tracking details for important objects, clues, documents and keepsakes that matter to continuity.
+screenshot:
+---
+
+# Overview
+
+Story Assets are important things that matter to the plot, the characters or the reader's understanding of the story. They can be physical objects, such as letters, clues, evidence, vehicles, keepsakes, weapons, documents, keys or heirlooms. They can also be information-like items when the story treats them as something that appears, moves, changes or needs resolving.
+
+Use this page to define the asset clearly enough that you can track it across scenes. This helps prevent continuity mistakes such as a letter being in two places at once, a clue appearing before it is discovered, or an heirloom vanishing after it has been set up.
+
+# Main Sections
+
+The name and description identify the asset in writer-friendly terms. Kind and importance help organise it. Current state and current location show where the asset stands now. Resolved marks whether the asset has completed its story purpose. Show in Quick Add Bar makes major recurring assets easier to place while planning scenes.
+
+# Example
+
+Beth's Memory Tin might be a high-importance keepsake because it carries emotional meaning and connects several discoveries. A background pub menu might be a low-importance prop unless it later becomes evidence.
+
+# Writer Tip
+
+Track assets that would cause confusion if their state, location or meaning changed without a record. Background colour and flavour objects usually do not need this level of tracking.
+
+# Related Guides
+
+- [Story Assets](/Help/Article/storyAssets.overview)
+- [Story Asset Details](/Help/Article/storyAssets.details)
+- [Scenes](/Help/Article/scenes.overview)

PlotLine/Help/Articles/StoryAssets/EventsAcrossScenes.md

@@ -0,0 +1,29 @@
+---
+title: Events Across Scenes
+category: Story Assets
+tags: assets, events, scenes, continuity
+contextKey: storyAssets.eventsAcrossScenes
+micro: Follow how an asset appears, changes or is used across scenes.
+quickTitle: Events across scenes
+quickSummary: Events Across Scenes shows where an asset changes, moves, is used or gains story significance.
+screenshot:
+---
+
+# Events Across Scenes
+
+Events Across Scenes shows the story moments where the asset appears, changes state, moves forward in meaning or becomes useful. This is where you can check the path from setup to payoff.
+
+Use this section to catch continuity issues such as an asset being used before it is found, changing condition without a scene, or disappearing between important moments.
+
+# Example
+
+A clue may be found in one scene, misread in another and finally understood near the reveal. Those events show the clue's evolving story significance.
+
+# Writer Tip
+
+The event indicator is a quick marker for the type of asset event. Use it as a compact signal, then read the event details for the actual story meaning.
+
+# Related Guides
+
+- [Story Asset Details](/Help/Article/storyAssets.details)
+- [Current State](/Help/Article/storyAssets.currentState)

PlotLine/Help/Articles/StoryAssets/Fields/CurrentLocation.md

@@ -0,0 +1,16 @@
+---
+title: Asset Current Location Field
+category: Story Assets
+tags: assets, fields, location, continuity
+contextKey: storyAssets.fields.currentLocation
+micro: Choose where the asset currently is.
+quickTitle: Current location
+quickSummary: Current Location helps you track where an important object is for continuity and scene planning.
+screenshot:
+---
+
+# Current Location
+
+Choose where the asset currently is. This is useful when an object moves between rooms, buildings, vehicles or characters' spaces.
+
+Use it before writing scenes where the asset is needed, discovered, hidden or transferred.

PlotLine/Help/Articles/StoryAssets/Fields/CurrentState.md

@@ -0,0 +1,16 @@
+---
+title: Asset Current State Field
+category: Story Assets
+tags: assets, fields, state, continuity
+contextKey: storyAssets.fields.currentState
+micro: Choose the asset's current condition or status.
+quickTitle: Current state
+quickSummary: Current State records whether an asset is sealed, opened, damaged, missing, recovered or in another meaningful condition.
+screenshot:
+---
+
+# Current State
+
+Choose the asset's current condition or status. Examples include sealed, opened, damaged, missing, recovered, hidden or destroyed.
+
+Use this when the asset's condition affects what characters can do, what readers understand or whether a continuity check should flag a problem.

PlotLine/Help/Articles/StoryAssets/Fields/Importance.md

@@ -0,0 +1,16 @@
+---
+title: Story Asset Importance
+category: Story Assets
+tags: assets, fields, importance, planning
+contextKey: storyAssets.fields.importance
+micro: Set how important this asset is to the story.
+quickTitle: Importance
+quickSummary: High values mark assets central to plot progression or emotion; low values mark minor or background assets.
+screenshot:
+---
+
+# Importance
+
+Set how important this asset is to the story. High values indicate assets central to plot progression or emotional significance. Low values indicate minor or background assets.
+
+For example, `10` might fit Beth's Memory Tin if it carries major emotional and plot weight. `2` might fit a background pub menu unless it later becomes evidence.

PlotLine/Help/Articles/StoryAssets/Fields/Kind.md

@@ -0,0 +1,16 @@
+---
+title: Story Asset Kind
+category: Story Assets
+tags: assets, fields, organisation
+contextKey: storyAssets.fields.kind
+micro: Choose the type of asset being tracked.
+quickTitle: Kind
+quickSummary: Kind categorises the asset so objects, clues, documents, evidence and other story items stay organised.
+screenshot:
+---
+
+# Kind
+
+Choose the type of asset being tracked. This might be a clue, document, weapon, vehicle, keepsake, key, heirloom or another kind used by your project.
+
+Categorising assets helps lists, reports and planning views stay readable when the story contains many important objects.

PlotLine/Help/Articles/StoryAssets/Fields/QuickAdd.md

@@ -0,0 +1,16 @@
+---
+title: Show in Quick Add Bar
+category: Story Assets
+tags: assets, fields, quick-add, planning
+contextKey: storyAssets.fields.quickAdd
+micro: Make this asset easier to place while planning scenes.
+quickTitle: Show in Quick Add Bar
+quickSummary: Show in Quick Add Bar makes major recurring assets available as quick planning shortcuts.
+screenshot:
+---
+
+# Show in Quick Add Bar
+
+Turn this on for assets you use often while planning scenes. It makes frequently used assets easier to place on the Timeline.
+
+This is intended for major recurring assets, not every background object.

PlotLine/Help/Articles/StoryAssets/Fields/Resolved.md

@@ -0,0 +1,16 @@
+---
+title: Story Asset Resolved
+category: Story Assets
+tags: assets, fields, resolved, clues
+contextKey: storyAssets.fields.resolved
+micro: Mark whether the asset has fulfilled its story purpose.
+quickTitle: Resolved
+quickSummary: Resolved helps track whether a clue, object or plot device has completed its role in the story.
+screenshot:
+---
+
+# Resolved
+
+Use Resolved when the asset has fulfilled its story purpose. This is especially useful for clues, evidence, promises and plot devices that create questions for the reader.
+
+For example, a murder weapon may become resolved once its role in the mystery is complete. Leave it unresolved while it still needs discovery, explanation or payoff.

PlotLine/Help/HelpAuthoringGuidelines.md

@@ -0,0 +1,60 @@
+---
+title: Help Authoring Guidelines
+category: Internal
+tags: help, authoring, guidelines
+contextKey: internal.helpAuthoringGuidelines
+micro: Internal guidance for writing PlotWeaver contextual help.
+quickTitle: Help authoring guidelines
+quickSummary: Internal guidance for applying the three-level help pattern across PlotWeaver Studio.
+screenshot:
+---
+
+# Three-Level Help Pattern
+
+Use this guideline when adding contextual help to a new PlotWeaver Studio area. The goal is to help authors understand the writing purpose of a page, section or field without exposing implementation details.
+
+# Level 1: Page Help
+
+Place page help beside the main H1. It should explain what the whole page is for, why an author would use it, how it fits the writing workflow and what the main sections mean.
+
+Context key pattern: `area.page`, such as `characters.details`.
+
+# Level 2: Section Help
+
+Place section help beside H2 headings or major card headings. It should explain a specific feature, when to use it, how it affects story planning or continuity and what to avoid.
+
+Context key pattern: `area.section`, such as `characters.initialRelationships`.
+
+If a section contains several controls, include a `# Understanding the Fields` section with a simple table.
+
+# Level 3: Field Help
+
+Place field help beside labels or unclear controls. Keep it short, practical and specific. Field help should answer what the field means, what to choose, how it affects the story model and what mistake to avoid.
+
+Context key pattern: `area.feature.field`, such as `characters.relationships.awareness`.
+
+# When To Add Help
+
+Add help when an author may ask what a field means, what choice to make, whether something is visible to readers, whether a value is story truth or character belief, or when a change becomes true in the story.
+
+# When Not To Add Help
+
+Do not add help to obvious fields such as name, short name, plain description fields or simple buttons. Do not add help just to decorate a page.
+
+# Article Structure
+
+Every article needs front matter with `title`, `category`, `tags`, `contextKey`, `micro`, `quickTitle`, `quickSummary` and `screenshot`. Leave `screenshot` blank unless a real screenshot file exists.
+
+Use Help Centre links by context key, such as `/Help/Article/characters.details`. Do not link directly to `.md` files.
+
+# Tone
+
+Write for authors. Prefer concrete story examples over technical descriptions. Explain why a feature matters for scenes, continuity, reader knowledge, character belief, reveals or revision.
+
+# Examples
+
+Page key: `characters.details`
+
+Section key: `characters.initialRelationships`
+
+Field key: `characters.relationships.readerInitiallyKnows`

PlotLine/TagHelpers/HelpIconTagHelper.cs

@@ -8,10 +8,12 @@ namespace PlotLine.TagHelpers;
 public sealed class HelpIconTagHelper(IHelpService help) : TagHelper
 {
     public string Key { get; set; } = string.Empty;
+    public string? Mode { get; set; }
 
     public override void Process(TagHelperContext context, TagHelperOutput output)
     {
         var article = help.GetByContextKey(Key);
+        var isInline = string.Equals(Mode, "inline", StringComparison.OrdinalIgnoreCase);
         var micro = string.IsNullOrWhiteSpace(article?.Micro)
             ? "Help article not found."
             : article.Micro;
@@ -24,7 +26,9 @@ public sealed class HelpIconTagHelper(IHelpService help) : TagHelper
 
         output.TagName = "span";
         output.TagMode = TagMode.StartTagAndEndTag;
-        output.Attributes.SetAttribute("class", "plotweaver-help-icon-wrapper");
+        output.Attributes.SetAttribute("class", isInline
+            ? "plotweaver-help-icon-wrapper plotweaver-help-icon-wrapper-inline"
+            : "plotweaver-help-icon-wrapper");
         output.Attributes.SetAttribute("data-help-icon", "true");
         output.Attributes.SetAttribute("data-help-key", Key);
         output.Attributes.SetAttribute("data-help-title", quickTitle);

PlotLine/Views/Characters/Details.cshtml

@@ -113,7 +113,7 @@
                                     <input type="hidden" name="CharacterID" value="@initialSourceId" />
                                     <input type="hidden" name="ReturnCharacterID" value="@Model.Character.CharacterID" />
                                     <div class="col-md-6">
-                                        <label class="form-label">Related character</label>
+                                        <label class="form-label">Related character <help-icon key="characters.relationships.relatedCharacter" mode="inline" /></label>
                                         <select class="form-select form-select-sm" name="RelatedCharacterID" required>
                                             @foreach (var option in Model.CharacterOptions.Where(x => x.Value != initialSourceId.ToString()))
                                             {
@@ -122,7 +122,7 @@
                                         </select>
                                     </div>
                                     <div class="col-md-6">
-                                        <label class="form-label">Relationship type</label>
+                                        <label class="form-label">Relationship type <help-icon key="characters.relationships.relationshipType" mode="inline" /></label>
                                         <select class="form-select form-select-sm" name="RelationshipTypeID">
                                             @foreach (var option in Model.RelationshipTypeOptions)
                                             {
@@ -131,7 +131,7 @@
                                         </select>
                                     </div>
                                     <div class="col-md-6">
-                                        <label class="form-label">Awareness</label>
+                                        <label class="form-label">Awareness <help-icon key="characters.relationships.awareness" mode="inline" /></label>
                                         <select class="form-select form-select-sm" name="InitialRelationshipStateID">
                                             <option value="">No awareness state</option>
                                             @foreach (var option in Model.RelationshipStateOptions)
@@ -141,7 +141,7 @@
                                         </select>
                                     </div>
                                     <div class="col-md-6">
-                                        <label class="form-label">Initial book</label>
+                                        <label class="form-label">Initial book <help-icon key="characters.relationships.initialBook" mode="inline" /></label>
                                         <select class="form-select form-select-sm" name="InitialBookID">
                                             <option value="">Project start</option>
                                             @foreach (var option in Model.BookOptions)
@@ -151,23 +151,23 @@
                                         </select>
                                     </div>
                                     <div class="col-md-8">
-                                        <label class="form-label">Confidence / intensity <output>@(relationship.InitialIntensity ?? 5)</output></label>
+                                        <label class="form-label">Confidence / intensity <output>@(relationship.InitialIntensity ?? 5)</output> <help-icon key="characters.relationships.confidenceIntensity" mode="inline" /></label>
                                         <input class="form-range" name="InitialIntensity" type="range" min="1" max="10" step="1" value="@(relationship.InitialIntensity ?? 5)" oninput="this.previousElementSibling.querySelector('output').value = this.value" />
                                     </div>
                                     <div class="col-md-4">
                                         <label class="form-check mt-4">
                                             <input type="hidden" name="IsReciprocal" value="false" />
                                             <input class="form-check-input" name="IsReciprocal" type="checkbox" value="true" checked="@relationship.IsReciprocal" />
-                                            <span class="form-check-label">Reciprocal</span>
+                                            <span class="form-check-label">Reciprocal <help-icon key="characters.relationships.reciprocal" mode="inline" /></span>
                                         </label>
                                         <label class="form-check">
                                             <input type="hidden" name="ReaderInitiallyKnows" value="false" />
                                             <input class="form-check-input" name="ReaderInitiallyKnows" type="checkbox" value="true" checked="@relationship.ReaderInitiallyKnows" />
-                                            <span class="form-check-label">Reader initially knows</span>
+                                            <span class="form-check-label">Reader initially knows <help-icon key="characters.relationships.readerInitiallyKnows" mode="inline" /></span>
                                         </label>
                                     </div>
                                     <div class="col-12">
-                                        <label class="form-label">Notes</label>
+                                        <label class="form-label">Notes <help-icon key="characters.relationships.notes" mode="inline" /></label>
                                         <textarea class="form-control form-control-sm" name="Notes" rows="2">@relationship.Notes</textarea>
                                     </div>
                                     <div class="col-12">
@@ -192,7 +192,7 @@
                 <input type="hidden" name="CharacterID" value="@Model.Character.CharacterID" />
                 <input type="hidden" name="ReturnCharacterID" value="@Model.Character.CharacterID" />
                 <div class="col-md-6">
-                    <label class="form-label">Related character</label>
+                    <label class="form-label">Related character <help-icon key="characters.relationships.relatedCharacter" mode="inline" /></label>
                     <select class="form-select form-select-sm" name="RelatedCharacterID" required>
                         <option value="">Choose character</option>
                         @foreach (var option in Model.CharacterOptions.Where(x => x.Value != Model.Character.CharacterID.ToString()))
@@ -202,39 +202,39 @@
                     </select>
                 </div>
                 <div class="col-md-6">
-                    <label class="form-label">Relationship type</label>
+                    <label class="form-label">Relationship type <help-icon key="characters.relationships.relationshipType" mode="inline" /></label>
                     <select class="form-select form-select-sm" name="RelationshipTypeID" asp-items="Model.RelationshipTypeOptions"></select>
                 </div>
                 <div class="col-md-6">
-                    <label class="form-label">Awareness</label>
+                    <label class="form-label">Awareness <help-icon key="characters.relationships.awareness" mode="inline" /></label>
                     <select class="form-select form-select-sm" name="InitialRelationshipStateID" asp-items="Model.RelationshipStateOptions">
                         <option value="">No awareness state</option>
                     </select>
                 </div>
                 <div class="col-md-6">
-                    <label class="form-label">Initial book</label>
+                    <label class="form-label">Initial book <help-icon key="characters.relationships.initialBook" mode="inline" /></label>
                     <select class="form-select form-select-sm" name="InitialBookID" asp-items="Model.BookOptions">
                         <option value="">Project start</option>
                     </select>
                 </div>
                 <div class="col-md-8">
-                    <label class="form-label">Confidence / intensity <output>5</output></label>
+                    <label class="form-label">Confidence / intensity <output>5</output> <help-icon key="characters.relationships.confidenceIntensity" mode="inline" /></label>
                     <input class="form-range" name="InitialIntensity" type="range" min="1" max="10" step="1" value="5" oninput="this.previousElementSibling.querySelector('output').value = this.value" />
                 </div>
                 <div class="col-md-4">
                     <label class="form-check mt-4">
                         <input type="hidden" name="IsReciprocal" value="false" />
                         <input class="form-check-input" name="IsReciprocal" type="checkbox" value="true" checked />
-                        <span class="form-check-label">Reciprocal</span>
+                        <span class="form-check-label">Reciprocal <help-icon key="characters.relationships.reciprocal" mode="inline" /></span>
                     </label>
                     <label class="form-check">
                         <input type="hidden" name="ReaderInitiallyKnows" value="false" />
                         <input class="form-check-input" name="ReaderInitiallyKnows" type="checkbox" value="true" checked />
-                        <span class="form-check-label">Reader initially knows</span>
+                        <span class="form-check-label">Reader initially knows <help-icon key="characters.relationships.readerInitiallyKnows" mode="inline" /></span>
                     </label>
                 </div>
                 <div class="col-12">
-                    <label class="form-label">Notes</label>
+                    <label class="form-label">Notes <help-icon key="characters.relationships.notes" mode="inline" /></label>
                     <textarea class="form-control form-control-sm" name="Notes" rows="2"></textarea>
                 </div>
                 <div class="col-12">

PlotLine/Views/Characters/Edit.cshtml

@@ -6,7 +6,7 @@
 <div class="page-heading compact">
     <div>
         <p class="eyebrow">Character</p>
-        <h1>@ViewData["Title"]</h1>
+        <h1>@ViewData["Title"] <help-icon key="characters.edit" /></h1>
     </div>
 </div>
 
@@ -45,7 +45,7 @@
             <input asp-for="EyeColour" class="form-control" />
         </div>
         <div class="col-md-6">
-            <label asp-for="CharacterImportance" class="form-label"></label>
+            <label asp-for="CharacterImportance" class="form-label">Story importance <help-icon key="characters.fields.storyImportance" mode="inline" /></label>
             <select asp-for="CharacterImportance" asp-items="Model.ImportanceOptions" class="form-select"></select>
             <div class="form-text">Controls timeline grouping for major, secondary/supporting, and minor characters.</div>
         </div>

PlotLine/Views/StoryAssets/Details.cshtml

@@ -29,7 +29,7 @@
 <div class="page-heading">
     <div>
         <p class="eyebrow">@Model.Asset.KindName</p>
-        <h1>@Model.Asset.AssetName</h1>
+        <h1>@Model.Asset.AssetName <help-icon key="storyAssets.details" /></h1>
         <p class="lead-text">@Model.Asset.Description</p>
     </div>
     <div class="button-row">
@@ -46,7 +46,7 @@
 
 <section class="asset-detail-grid">
     <article class="plain-card">
-        <h2>Current state</h2>
+        <h2>Current state <help-icon key="storyAssets.currentState" /></h2>
         <p><strong>Importance:</strong> @Model.Asset.Importance / 10</p>
         <p><strong>State:</strong> @(Model.Asset.CurrentStateName ?? "No state")</p>
         <p><strong>Location:</strong> @(Model.Asset.CurrentLocationPath ?? "No location")</p>
@@ -54,7 +54,7 @@
     </article>
 
     <article class="plain-card">
-        <h2>Dependencies</h2>
+        <h2>Dependencies <help-icon key="storyAssets.dependencies" /></h2>
         @if (!Model.Dependencies.Any())
         {
             <p class="muted">No dependencies yet.</p>
@@ -116,7 +116,7 @@
 </section>
 
 <section class="list-section mt-3">
-    <h2>Events across scenes</h2>
+    <h2>Events across scenes <help-icon key="storyAssets.eventsAcrossScenes" /></h2>
     @if (!Model.Events.Any())
     {
         <p class="muted">No scene events yet.</p>
@@ -126,9 +126,9 @@
         <div class="asset-mini-list">
             @foreach (var assetEvent in Model.Events)
             {
-                <div class="asset-mini-item">
+                <div class="asset-mini-item story-asset-event-item">
                     <span class="asset-event-marker">@assetEvent.MarkerText</span>
-                    <div>
+                    <div class="story-asset-event-details">
                         <strong>@assetEvent.EventTitle</strong>
                         <span>@assetEvent.BookTitle / Ch @assetEvent.ChapterNumber / Scene @assetEvent.SceneNumber: @assetEvent.SceneTitle</span>
                         <span>@assetEvent.FromStateName -> @assetEvent.ToStateName</span>
@@ -141,7 +141,7 @@
 </section>
 
 <section class="list-section mt-3">
-    <h2>Custody</h2>
+    <h2>Custody <help-icon key="storyAssets.custody" /></h2>
     @if (!Model.CustodyEvents.Any())
     {
         <p class="muted">No custody events yet.</p>

PlotLine/Views/StoryAssets/Edit.cshtml

@@ -6,11 +6,11 @@
 <div class="page-heading compact">
     <div>
         <p class="eyebrow">Story asset</p>
-        <h1>@ViewData["Title"]</h1>
+        <h1>@ViewData["Title"] <help-icon key="storyAssets.edit" /></h1>
     </div>
 </div>
 
-<form asp-action="Save" method="post" class="edit-panel">
+<form asp-action="Save" method="post" class="edit-panel story-asset-edit-panel">
     <input asp-for="StoryAssetID" type="hidden" />
     <input asp-for="ProjectID" type="hidden" />
 
@@ -21,13 +21,13 @@
             <span asp-validation-for="AssetName" class="text-danger"></span>
         </div>
         <div class="col-md-4">
-            <label asp-for="AssetKindID" class="form-label"></label>
+            <label asp-for="AssetKindID" class="form-label">Kind <help-icon key="storyAssets.fields.kind" mode="inline" /></label>
             <select asp-for="AssetKindID" asp-items="Model.AssetKindOptions" class="form-select"></select>
         </div>
         <div class="col-md-4">
-            <div class="metric-slider asset-importance-slider">
+            <div class="metric-slider asset-importance-slider story-asset-importance-control">
                 <div class="metric-slider-label">
-                    <label asp-for="Importance"></label>
+                    <label asp-for="Importance">Importance <help-icon key="storyAssets.fields.importance" mode="inline" /></label>
                     <output>@Model.Importance</output>
                 </div>
                 <input asp-for="Importance" type="range" class="form-range" min="1" max="10" oninput="this.previousElementSibling.querySelector('output').value = this.value" />
@@ -35,27 +35,27 @@
             <span asp-validation-for="Importance" class="text-danger"></span>
         </div>
         <div class="col-md-4">
-            <label asp-for="CurrentStateID" class="form-label"></label>
+            <div class="story-asset-state-group">
-            <select asp-for="CurrentStateID" asp-items="Model.AssetStateOptions" class="form-select">
+                <label asp-for="CurrentStateID" class="form-label">Current state <help-icon key="storyAssets.fields.currentState" mode="inline" /></label>
-                <option value="">No state</option>
+                <select asp-for="CurrentStateID" asp-items="Model.AssetStateOptions" class="form-select">
-            </select>
+                    <option value="">No state</option>
+                </select>
+                <div class="form-check story-asset-resolved-check">
+                    <input asp-for="IsResolved" class="form-check-input" />
+                    <label asp-for="IsResolved" class="form-check-label">Resolved <help-icon key="storyAssets.fields.resolved" mode="inline" /></label>
+                </div>
+            </div>
         </div>
         <div class="col-md-4">
-            <label asp-for="CurrentLocationID" class="form-label"></label>
+            <label asp-for="CurrentLocationID" class="form-label">Current location <help-icon key="storyAssets.fields.currentLocation" mode="inline" /></label>
             <select asp-for="CurrentLocationID" asp-items="Model.LocationOptions" class="form-select">
                 <option value="">No location</option>
             </select>
         </div>
-        <div class="col-md-4 d-flex align-items-end">
-            <div class="form-check mb-2">
-                <input asp-for="IsResolved" class="form-check-input" />
-                <label asp-for="IsResolved" class="form-check-label"></label>
-            </div>
-        </div>
         <div class="col-md-4 d-flex align-items-end">
             <div class="form-check mb-2">
                 <input asp-for="ShowInQuickAddBar" class="form-check-input" />
-                <label asp-for="ShowInQuickAddBar" class="form-check-label"></label>
+                <label asp-for="ShowInQuickAddBar" class="form-check-label">Show in Quick Add Bar <help-icon key="storyAssets.fields.quickAdd" mode="inline" /></label>
                 <div class="form-text">Makes this item available as a draggable shortcut on the Timeline page.</div>
             </div>
         </div>

PlotLine/wwwroot/css/plotline-theme.css

@@ -1622,6 +1622,13 @@ a:focus-visible {
   vertical-align: text-top;
 }
 
+.plotweaver-help-icon-wrapper-inline .plotweaver-help-icon {
+  width: 1rem;
+  height: 1rem;
+  margin-left: 0.25rem;
+  font-size: 0.68rem;
+}
+
 .plotweaver-help-icon:hover,
 .plotweaver-help-icon:focus {
   color: #2f6f63;

PlotLine/wwwroot/css/site.css

@@ -1602,6 +1602,34 @@ body.timeline-inspector-resizing {
   background: rgba(47, 111, 99, 0.05);
 }
 
+.story-asset-importance-control {
+  background: var(--plotline-surface);
+}
+
+.story-asset-state-group {
+  display: grid;
+  gap: 8px;
+}
+
+.story-asset-resolved-check {
+  margin-bottom: 0;
+}
+
+.story-asset-event-item {
+  justify-content: flex-start;
+  gap: 8px;
+}
+
+.story-asset-event-item .asset-event-marker {
+  flex: 0 0 auto;
+  min-width: 1.55rem;
+  width: auto;
+}
+
+.story-asset-event-details {
+  min-width: 0;
+}
+
 .scene-inspector-root {
   display: grid;
   gap: 12px;