diff --git a/PlotLine/Help/Articles/SceneInspector/Assets.md b/PlotLine/Help/Articles/SceneInspector/Assets.md
index 9b604aa..f3927ec 100644
--- a/PlotLine/Help/Articles/SceneInspector/Assets.md
+++ b/PlotLine/Help/Articles/SceneInspector/Assets.md
@@ -19,6 +19,12 @@ Asset states record what condition or story status the object has. Dependencies
Assets create continuity obligations. If a letter is burned, it should not be read later unless another copy exists. If a weapon is with one character, another character needs a reason to use it. If evidence is hidden, discovery should happen in a recorded scene.
+# What To Track
+
+Track objects that affect plot, knowledge, conflict or continuity: letters, weapons, keys, evidence, documents, phones, vehicles, heirlooms, medicines, disguises and records.
+
+Use state changes for what the object becomes, location for where it is, and custody for who controls it. These three ideas often overlap but they are not the same.
+
# Related Guides
- [Timeline Asset Events](/Help/Article/timeline.assetEvents)
diff --git a/PlotLine/Help/Articles/SceneInspector/Attachments.md b/PlotLine/Help/Articles/SceneInspector/Attachments.md
index 9b5ee07..d6bc91b 100644
--- a/PlotLine/Help/Articles/SceneInspector/Attachments.md
+++ b/PlotLine/Help/Articles/SceneInspector/Attachments.md
@@ -14,3 +14,9 @@ screenshot:
Attachments are for supporting material: research links, images, maps, interview notes, historical references, sketches or source documents.
Use notes to explain why the attachment matters. Future-you should not have to reopen every file to remember what it was for.
+
+# Storage And Best Practice
+
+Files can affect storage usage and subscription limits. Attach the material that genuinely supports the scene, and prefer links when the source can safely remain external.
+
+Good attachments include a floor plan for a locked-room scene, a photo reference for clothing, a research article for a medical detail, a map for travel logic or a note explaining a real-world source.
diff --git a/PlotLine/Help/Articles/SceneInspector/CharacterAttributes.md b/PlotLine/Help/Articles/SceneInspector/CharacterAttributes.md
index 845a525..310a9a2 100644
--- a/PlotLine/Help/Articles/SceneInspector/CharacterAttributes.md
+++ b/PlotLine/Help/Articles/SceneInspector/CharacterAttributes.md
@@ -19,6 +19,12 @@ Use them when a scene changes how a character should be described or understood
Attribute changes become part of the character's story history. Future scenes can then be checked against what has already been established. If a character is injured in one scene and perfectly fine in the next without explanation, PlotDirector has evidence to help you notice.
+# What To Track
+
+Track details that create future obligations: injuries, disguises, clothing that will be recognised, emotional state that affects later behaviour, new skills, lost abilities, scars, pregnancy, intoxication, fatigue or anything the reader would expect to remain true.
+
+Do not use attributes for ordinary description that has no continuity consequence. The best attribute events are the ones future-you will be glad to see.
+
# Related Guides
- [Characters](/Help/Article/sceneInspector.characters)
diff --git a/PlotLine/Help/Articles/SceneInspector/Characters.md b/PlotLine/Help/Articles/SceneInspector/Characters.md
index f3c15dd..d323107 100644
--- a/PlotLine/Help/Articles/SceneInspector/Characters.md
+++ b/PlotLine/Help/Articles/SceneInspector/Characters.md
@@ -15,6 +15,16 @@ The Characters section records who appears in the scene, how they participate an
Role tells you whether a character is the point of view, a main participant, a supporting presence or only mentioned. Presence and location details help the story remember who was actually there.
+# Why Adding Characters Matters
+
+Characters drive many PlotDirector systems. Once a character is attached to a scene, they can appear in Timeline lanes, character-focused filters, relationship review, knowledge tracking, attribute history and continuity checks.
+
+You do not need to fill every character field every time. Add the details that matter: POV when reader access matters, role when participation matters, location when movement or continuity matters, and notes when the scene changes what future scenes need to remember.
+
+# Continuity Implications
+
+Character location and movement help answer whether someone could witness an event, hold an object, know a secret or appear in the next scene without a travel gap.
+
# Related Guides
- [Character Appearances](/Help/Article/timeline.characterAppearances)
diff --git a/PlotLine/Help/Articles/SceneInspector/Checklist.md b/PlotLine/Help/Articles/SceneInspector/Checklist.md
index 4443882..25e04a5 100644
--- a/PlotLine/Help/Articles/SceneInspector/Checklist.md
+++ b/PlotLine/Help/Articles/SceneInspector/Checklist.md
@@ -14,3 +14,9 @@ screenshot:
The checklist is for concrete scene tasks: add sensory detail, check the alibi, rewrite the argument, verify the date, add the missing clue, or trim the ending.
Use it for actions you want to complete, not for permanent story facts. Story facts belong in the relevant scene, character, thread or asset fields.
+
+# Editable Tasks
+
+Checklist labels are editable because scene tasks often change as you revise. "Fix ending" might become "Make Beth choose to lie before Arun enters." Keep the label as specific as the work requires.
+
+Tick completion when the task is done. Remove items that no longer matter so the checklist stays trustworthy.
diff --git a/PlotLine/Help/Articles/SceneInspector/Custody.md b/PlotLine/Help/Articles/SceneInspector/Custody.md
index e59592c..b05f56f 100644
--- a/PlotLine/Help/Articles/SceneInspector/Custody.md
+++ b/PlotLine/Help/Articles/SceneInspector/Custody.md
@@ -19,6 +19,12 @@ Custody can differ from location. A car may be parked outside, but one character
Custody helps PlotDirector spot impossible possession. If Beth gives the key to Arun in one scene, Beth should not use it later unless it returns to her or a duplicate exists.
+# Ownership Versus Possession
+
+Ownership is who the object belongs to. Possession is who has it now. Control is who can use or access it. These can be different: a stolen car, borrowed keys, guarded evidence or a document locked in someone else's safe.
+
+Use custody events for transfers, thefts, handoffs, losses, recoveries and moments where control changes.
+
# Related Guides
- [Assets](/Help/Article/sceneInspector.assets)
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/AssetEventType.md b/PlotLine/Help/Articles/SceneInspector/Fields/AssetEventType.md
new file mode 100644
index 0000000..bb23326
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/AssetEventType.md
@@ -0,0 +1,14 @@
+---
+title: Asset Event Type
+category: Scene Inspector
+tags: scene inspector, fields, assets
+contextKey: sceneInspector.fields.assetEventType
+micro: Describe what happens to the asset in this scene.
+quickTitle: Asset event type
+quickSummary: Asset event type records whether an object is found, moved, revealed, damaged, used, hidden or otherwise changed.
+screenshot:
+---
+
+# Overview
+
+Choose the event that best describes the object's story beat. This is what appears in Timeline asset lanes and helps continuity understand why the asset's state changed.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/AssetKind.md b/PlotLine/Help/Articles/SceneInspector/Fields/AssetKind.md
new file mode 100644
index 0000000..9cf4c0d
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/AssetKind.md
@@ -0,0 +1,14 @@
+---
+title: Asset Kind
+category: Scene Inspector
+tags: scene inspector, fields, assets
+contextKey: sceneInspector.fields.assetKind
+micro: Classify a new story asset.
+quickTitle: Asset kind
+quickSummary: Asset kind helps distinguish evidence, weapons, documents, keys, vehicles and other important objects.
+screenshot:
+---
+
+# Overview
+
+Use kind to make assets easier to find and review later. The category should describe how the object functions in the story.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/AssetLocation.md b/PlotLine/Help/Articles/SceneInspector/Fields/AssetLocation.md
new file mode 100644
index 0000000..70a17c8
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/AssetLocation.md
@@ -0,0 +1,14 @@
+---
+title: Asset Location
+category: Scene Inspector
+tags: scene inspector, fields, assets, locations
+contextKey: sceneInspector.fields.assetLocation
+micro: Record where an asset is in this scene.
+quickTitle: Asset location
+quickSummary: Asset location fields support last-known-location tracking and continuity checks.
+screenshot:
+---
+
+# Overview
+
+Use asset location when an object's place matters separately from who holds it. A letter can be in a drawer, a vehicle in a garage, or evidence under a floorboard.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/AssetSelector.md b/PlotLine/Help/Articles/SceneInspector/Fields/AssetSelector.md
new file mode 100644
index 0000000..2d14499
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/AssetSelector.md
@@ -0,0 +1,14 @@
+---
+title: Asset Selector
+category: Scene Inspector
+tags: scene inspector, fields, assets
+contextKey: sceneInspector.fields.assetSelector
+micro: Choose the asset this scene changes or places.
+quickTitle: Asset selector
+quickSummary: Asset selectors connect scene events to important objects, clues, evidence, documents, weapons, keys or vehicles.
+screenshot:
+---
+
+# Overview
+
+Choose an existing asset when this scene changes a known object. Create a new asset when the object should be tracked beyond this scene.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/AssetState.md b/PlotLine/Help/Articles/SceneInspector/Fields/AssetState.md
new file mode 100644
index 0000000..0c686f4
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/AssetState.md
@@ -0,0 +1,14 @@
+---
+title: Asset State
+category: Scene Inspector
+tags: scene inspector, fields, assets, state
+contextKey: sceneInspector.fields.assetState
+micro: Record an asset state before or after this event.
+quickTitle: Asset state
+quickSummary: Asset state transitions help continuity know whether an object is hidden, found, damaged, destroyed, active or otherwise changed.
+screenshot:
+---
+
+# Overview
+
+Use From state when the event depends on where the asset started. Use To state when the event changes what should be true afterward. Leave state blank when the object matters but its condition does not change.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/AttachmentType.md b/PlotLine/Help/Articles/SceneInspector/Fields/AttachmentType.md
new file mode 100644
index 0000000..54b16d6
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/AttachmentType.md
@@ -0,0 +1,14 @@
+---
+title: Attachment Type
+category: Scene Inspector
+tags: scene inspector, fields, attachments, research
+contextKey: sceneInspector.fields.attachmentType
+micro: Classify scene research or reference material.
+quickTitle: Attachment type
+quickSummary: Attachment type helps distinguish research, images, maps, notes, references and other scene-specific resources.
+screenshot:
+---
+
+# Overview
+
+Use attachment type to keep references findable. Files and links can count against storage or subscription limits, so attach material that genuinely supports this scene.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/AttributeType.md b/PlotLine/Help/Articles/SceneInspector/Fields/AttributeType.md
new file mode 100644
index 0000000..48ef922
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/AttributeType.md
@@ -0,0 +1,14 @@
+---
+title: Character Attribute Type
+category: Scene Inspector
+tags: scene inspector, fields, character attributes
+contextKey: sceneInspector.fields.attributeType
+micro: Choose what kind of character state changes here.
+quickTitle: Attribute type
+quickSummary: Attribute type identifies whether the scene changes appearance, injury, emotion, skill or another trackable state.
+screenshot:
+---
+
+# Overview
+
+Choose the attribute type that best describes what future scenes need to remember. Attribute events are most useful for changes that persist, such as injuries, disguises, emotional state, visible clothing or learned skills.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/AttributeValue.md b/PlotLine/Help/Articles/SceneInspector/Fields/AttributeValue.md
new file mode 100644
index 0000000..3493dbc
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/AttributeValue.md
@@ -0,0 +1,14 @@
+---
+title: Character Attribute Value
+category: Scene Inspector
+tags: scene inspector, fields, character attributes
+contextKey: sceneInspector.fields.attributeValue
+micro: Record the new state created by this scene.
+quickTitle: Attribute value
+quickSummary: Attribute value is the concise state future scenes should remember.
+screenshot:
+---
+
+# Overview
+
+Use a short value such as "bruised ribs", "black dress", "furious but hiding it" or "can pick simple locks". Add detail only when it will help future continuity.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/CharacterLocation.md b/PlotLine/Help/Articles/SceneInspector/Fields/CharacterLocation.md
new file mode 100644
index 0000000..99b1fb6
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/CharacterLocation.md
@@ -0,0 +1,14 @@
+---
+title: Character Location Fields
+category: Scene Inspector
+tags: scene inspector, fields, characters, locations
+contextKey: sceneInspector.fields.characterLocation
+micro: Track where a character is, enters from and exits to.
+quickTitle: Character location
+quickSummary: Character location fields support movement, travel and continuity checks across future scenes.
+screenshot:
+---
+
+# Overview
+
+Current location records where the character is during this scene. Entry and exit locations record movement into and out of the scene. Use them when geography or continuity matters; leave them unset when location is irrelevant.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/CharacterPresence.md b/PlotLine/Help/Articles/SceneInspector/Fields/CharacterPresence.md
new file mode 100644
index 0000000..5a32f55
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/CharacterPresence.md
@@ -0,0 +1,14 @@
+---
+title: Character Presence
+category: Scene Inspector
+tags: scene inspector, fields, characters, presence
+contextKey: sceneInspector.fields.characterPresence
+micro: Record whether the character is physically present, mentioned or otherwise involved.
+quickTitle: Character presence
+quickSummary: Presence helps distinguish being in the room from being referenced, absent or indirectly affecting the scene.
+screenshot:
+---
+
+# Overview
+
+Use presence to clarify what "appears" means. A character can drive a scene through a letter, memory or phone call without physically standing there.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/CharacterRole.md b/PlotLine/Help/Articles/SceneInspector/Fields/CharacterRole.md
new file mode 100644
index 0000000..4233bd7
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/CharacterRole.md
@@ -0,0 +1,14 @@
+---
+title: Character Role
+category: Scene Inspector
+tags: scene inspector, fields, characters, role
+contextKey: sceneInspector.fields.characterRole
+micro: Describe what the character does in this scene.
+quickTitle: Character role
+quickSummary: Role distinguishes POV, main participant, supporting presence and minor mentions for Timeline and review.
+screenshot:
+---
+
+# Overview
+
+Use role to show how actively the character participates. A POV or main participant carries more story weight than a mentioned character, and that difference matters in appearance lanes and character-focused review.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/CharacterSelector.md b/PlotLine/Help/Articles/SceneInspector/Fields/CharacterSelector.md
new file mode 100644
index 0000000..d42c7ff
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/CharacterSelector.md
@@ -0,0 +1,14 @@
+---
+title: Character Selector
+category: Scene Inspector
+tags: scene inspector, fields, characters
+contextKey: sceneInspector.fields.characterSelector
+micro: Choose which character the scene detail applies to.
+quickTitle: Character selector
+quickSummary: Character selectors connect scene evidence to the right person for Timeline, continuity and character history.
+screenshot:
+---
+
+# Overview
+
+Choose an existing character when this scene updates someone already in the project. Create a new character from the scene only when the person should become part of the project record.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/ChecklistCompletion.md b/PlotLine/Help/Articles/SceneInspector/Fields/ChecklistCompletion.md
new file mode 100644
index 0000000..6dafc8c
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/ChecklistCompletion.md
@@ -0,0 +1,14 @@
+---
+title: Checklist Completion
+category: Scene Inspector
+tags: scene inspector, fields, checklist
+contextKey: sceneInspector.fields.checklistCompletion
+micro: Mark whether a scene task is done.
+quickTitle: Checklist completion
+quickSummary: Checklist completion tracks practical scene tasks; labels stay editable so the task can evolve.
+screenshot:
+---
+
+# Overview
+
+Tick a checklist item when the task is complete. Edit the label as the task becomes clearer. Remove items that no longer matter so the checklist stays useful.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/Custodians.md b/PlotLine/Help/Articles/SceneInspector/Fields/Custodians.md
new file mode 100644
index 0000000..f50c037
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/Custodians.md
@@ -0,0 +1,14 @@
+---
+title: Custodians
+category: Scene Inspector
+tags: scene inspector, fields, custody, characters
+contextKey: sceneInspector.fields.custodians
+micro: Choose who has or controls the asset.
+quickTitle: Custodians
+quickSummary: Custodians identify the characters who possess, guard, control or are responsible for an asset.
+screenshot:
+---
+
+# Overview
+
+Choose existing characters when possible so continuity can connect custody to character appearances and future actions. Use names only for off-page, unknown or temporary custodians.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/CustodyEventType.md b/PlotLine/Help/Articles/SceneInspector/Fields/CustodyEventType.md
new file mode 100644
index 0000000..5c1a7ab
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/CustodyEventType.md
@@ -0,0 +1,14 @@
+---
+title: Custody Event Type
+category: Scene Inspector
+tags: scene inspector, fields, custody
+contextKey: sceneInspector.fields.custodyEventType
+micro: Describe the custody change for an asset.
+quickTitle: Custody event type
+quickSummary: Custody event type records possession, transfer, loss, theft, handoff or control of an important asset.
+screenshot:
+---
+
+# Overview
+
+Choose the custody event that explains who controls the object after this scene. Custody can mean possession, access, responsibility or control, not only legal ownership.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/CustodyRole.md b/PlotLine/Help/Articles/SceneInspector/Fields/CustodyRole.md
new file mode 100644
index 0000000..2fa6a2e
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/CustodyRole.md
@@ -0,0 +1,14 @@
+---
+title: Custody Role
+category: Scene Inspector
+tags: scene inspector, fields, custody
+contextKey: sceneInspector.fields.custodyRole
+micro: Choose how the custodian relates to the asset.
+quickTitle: Custody role
+quickSummary: Custody role distinguishes holder, owner, guardian, thief, borrower or other control relationship.
+screenshot:
+---
+
+# Overview
+
+Use role to explain the nature of possession. A character may own a car, borrow a key, steal a letter or guard evidence for someone else.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/DependencyControls.md b/PlotLine/Help/Articles/SceneInspector/Fields/DependencyControls.md
new file mode 100644
index 0000000..cdcb14c
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/DependencyControls.md
@@ -0,0 +1,14 @@
+---
+title: Scene Dependency Controls
+category: Scene Inspector
+tags: scene inspector, fields, dependencies
+contextKey: sceneInspector.fields.dependencyControls
+micro: Record why scene order matters.
+quickTitle: Dependency controls
+quickSummary: Dependency controls explain whether this scene relies on another scene, or another scene relies on this one.
+screenshot:
+---
+
+# Overview
+
+Use direction to express the dependency in plain English, then choose the related scene and type. Mark it hard only when the order is essential for story logic.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/DurationUnit.md b/PlotLine/Help/Articles/SceneInspector/Fields/DurationUnit.md
new file mode 100644
index 0000000..8f523bf
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/DurationUnit.md
@@ -0,0 +1,14 @@
+---
+title: Duration Unit
+category: Scene Inspector
+tags: scene inspector, fields, time, duration
+contextKey: sceneInspector.fields.durationUnit
+micro: Choose the unit for the scene's duration.
+quickTitle: Duration unit
+quickSummary: Duration helps pacing, travel and chronology make sense when scene length matters.
+screenshot:
+---
+
+# Overview
+
+Use duration when the amount of time consumed by the scene matters. Minutes may matter in a chase; days may matter for travel, recovery or relationship distance.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/KnowledgeState.md b/PlotLine/Help/Articles/SceneInspector/Fields/KnowledgeState.md
new file mode 100644
index 0000000..d07c415
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/KnowledgeState.md
@@ -0,0 +1,14 @@
+---
+title: Knowledge State
+category: Scene Inspector
+tags: scene inspector, fields, knowledge, awareness
+contextKey: sceneInspector.fields.knowledgeState
+micro: Record what the character knows at this point.
+quickTitle: Knowledge state
+quickSummary: Knowledge state tracks whether a character is unaware, suspicious, partly informed or fully aware.
+screenshot:
+---
+
+# Overview
+
+Use knowledge state to capture the character's current awareness. This supports mysteries, dramatic irony and warnings when someone acts on information they should not have yet.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/KnowledgeSubject.md b/PlotLine/Help/Articles/SceneInspector/Fields/KnowledgeSubject.md
new file mode 100644
index 0000000..e959046
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/KnowledgeSubject.md
@@ -0,0 +1,14 @@
+---
+title: Knowledge Subject
+category: Scene Inspector
+tags: scene inspector, fields, knowledge
+contextKey: sceneInspector.fields.knowledgeSubject
+micro: Connect knowledge to an asset or plot thread when relevant.
+quickTitle: Knowledge subject
+quickSummary: Knowledge subjects explain what the character's awareness is about: an object, clue, secret or plot thread.
+screenshot:
+---
+
+# Overview
+
+Choose an asset when the knowledge concerns an object or evidence. Choose a plot thread when it concerns a question, secret or storyline. Leave one blank when the knowledge is broader.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/MoveControls.md b/PlotLine/Help/Articles/SceneInspector/Fields/MoveControls.md
new file mode 100644
index 0000000..aa260c4
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/MoveControls.md
@@ -0,0 +1,14 @@
+---
+title: Move Controls
+category: Scene Inspector
+tags: scene inspector, fields, move, reorder
+contextKey: sceneInspector.fields.moveControls
+micro: Choose where the scene should move.
+quickTitle: Move controls
+quickSummary: Move controls preview structural changes before changing the scene's chapter position.
+screenshot:
+---
+
+# Overview
+
+Choose the target chapter and whether the scene should go at the start or end. Renumber scenes when the chapter order should be cleaned up after the move.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/NoteType.md b/PlotLine/Help/Articles/SceneInspector/Fields/NoteType.md
new file mode 100644
index 0000000..b5d658b
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/NoteType.md
@@ -0,0 +1,14 @@
+---
+title: Scene Note Type
+category: Scene Inspector
+tags: scene inspector, fields, notes
+contextKey: sceneInspector.fields.noteType
+micro: Classify a working note by purpose.
+quickTitle: Note type
+quickSummary: Note type keeps drafting thoughts, research reminders and revision questions easier to scan.
+screenshot:
+---
+
+# Overview
+
+Use note type to separate kinds of working memory. A research reminder, revision question and drafting idea may all belong to the same scene, but they ask for different follow-up.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/PrimaryLocation.md b/PlotLine/Help/Articles/SceneInspector/Fields/PrimaryLocation.md
new file mode 100644
index 0000000..9a6e977
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/PrimaryLocation.md
@@ -0,0 +1,14 @@
+---
+title: Primary Location
+category: Scene Inspector
+tags: scene inspector, fields, locations, continuity
+contextKey: sceneInspector.fields.primaryLocation
+micro: Choose the main place where the scene happens.
+quickTitle: Primary location
+quickSummary: Primary location anchors the scene for Timeline review, location continuity and travel reasoning.
+screenshot:
+---
+
+# Overview
+
+Choose the location the reader would treat as the scene's main place. Use asset locations and custody for object-specific placement when the object is elsewhere.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/RelationshipCharacters.md b/PlotLine/Help/Articles/SceneInspector/Fields/RelationshipCharacters.md
new file mode 100644
index 0000000..dd76f11
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/RelationshipCharacters.md
@@ -0,0 +1,14 @@
+---
+title: Relationship Characters
+category: Scene Inspector
+tags: scene inspector, fields, relationships
+contextKey: sceneInspector.fields.relationshipCharacters
+micro: Choose the people involved in a relationship event.
+quickTitle: Relationship characters
+quickSummary: Character A and Character B define the direction of the relationship event.
+screenshot:
+---
+
+# Overview
+
+Direction matters for one-sided feelings, mistaken trust, secrecy and asymmetrical conflict. Choose the order that best represents whose relationship state is changing.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/RelationshipKnown.md b/PlotLine/Help/Articles/SceneInspector/Fields/RelationshipKnown.md
new file mode 100644
index 0000000..76f2858
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/RelationshipKnown.md
@@ -0,0 +1,14 @@
+---
+title: Other Character Knows
+category: Scene Inspector
+tags: scene inspector, fields, relationships, knowledge
+contextKey: sceneInspector.fields.relationshipKnown
+micro: Mark whether the relationship change is known to the other person.
+quickTitle: Other character knows
+quickSummary: This is useful for one-sided attraction, secret resentment, hidden loyalty or dramatic irony.
+screenshot:
+---
+
+# Overview
+
+Tick this when the other character is aware of the relationship state or change. Leave it unticked for hidden feelings, secret betrayal or private assumptions.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/RelationshipSelector.md b/PlotLine/Help/Articles/SceneInspector/Fields/RelationshipSelector.md
new file mode 100644
index 0000000..9cb05f2
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/RelationshipSelector.md
@@ -0,0 +1,14 @@
+---
+title: Relationship Selector
+category: Scene Inspector
+tags: scene inspector, fields, relationships
+contextKey: sceneInspector.fields.relationshipSelector
+micro: Choose an existing relationship or create one from the event.
+quickTitle: Relationship selector
+quickSummary: Relationship selector links this scene event to the relationship history it changes.
+screenshot:
+---
+
+# Overview
+
+Choose an existing relationship if this scene changes a known bond. Create or choose characters only when the relationship does not exist yet. You do not need to fill every relationship field for every event.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/RelationshipState.md b/PlotLine/Help/Articles/SceneInspector/Fields/RelationshipState.md
new file mode 100644
index 0000000..442e1b2
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/RelationshipState.md
@@ -0,0 +1,14 @@
+---
+title: Relationship State
+category: Scene Inspector
+tags: scene inspector, fields, relationships
+contextKey: sceneInspector.fields.relationshipState
+micro: Record the relationship's state after this scene.
+quickTitle: Relationship state
+quickSummary: Relationship state captures the current condition of the bond after the scene's change.
+screenshot:
+---
+
+# Overview
+
+Use state to mark what has changed: trust, conflict, attraction, estrangement, alliance or another relationship condition. Leave detail in the description only when the nuance matters.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/RelationshipType.md b/PlotLine/Help/Articles/SceneInspector/Fields/RelationshipType.md
new file mode 100644
index 0000000..70257de
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/RelationshipType.md
@@ -0,0 +1,14 @@
+---
+title: Relationship Type
+category: Scene Inspector
+tags: scene inspector, fields, relationships
+contextKey: sceneInspector.fields.relationshipType
+micro: Identify the kind of relationship being changed.
+quickTitle: Relationship type
+quickSummary: Relationship type describes the bond: family, friendship, romance, rivalry, mentorship, professional or another category.
+screenshot:
+---
+
+# Overview
+
+Choose type when the kind of bond matters to the story. It helps later review separate romance beats from professional loyalty, rivalry, family conflict or friendship.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/RevisionStatus.md b/PlotLine/Help/Articles/SceneInspector/Fields/RevisionStatus.md
new file mode 100644
index 0000000..c2c308a
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/RevisionStatus.md
@@ -0,0 +1,14 @@
+---
+title: Scene Revision Status
+category: Scene Inspector
+tags: scene inspector, fields, revision, workflow
+contextKey: sceneInspector.fields.revisionStatus
+micro: Mark where this scene is in the writing process.
+quickTitle: Revision status
+quickSummary: Revision status feeds writing queues, project overview and revision workflow without changing story continuity.
+screenshot:
+---
+
+# Overview
+
+Use revision status to show whether the scene is planned, drafted, revising, ready or otherwise in progress. It helps workflow views decide what needs attention next.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/ThreadSelector.md b/PlotLine/Help/Articles/SceneInspector/Fields/ThreadSelector.md
new file mode 100644
index 0000000..696d24f
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/ThreadSelector.md
@@ -0,0 +1,14 @@
+---
+title: Plot Thread Selector
+category: Scene Inspector
+tags: scene inspector, fields, threads
+contextKey: sceneInspector.fields.threadSelector
+micro: Choose the plot line and thread this event belongs to.
+quickTitle: Thread selector
+quickSummary: Thread selectors connect this scene beat to the storyline it starts, develops, twists or resolves.
+screenshot:
+---
+
+# Overview
+
+Choose the plot line first, then an existing thread if one already carries this question or promise. Create a new thread only when the scene introduces a distinct unresolved concern.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/ThreadTarget.md b/PlotLine/Help/Articles/SceneInspector/Fields/ThreadTarget.md
new file mode 100644
index 0000000..58fc5f5
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/ThreadTarget.md
@@ -0,0 +1,14 @@
+---
+title: Thread Event Targets
+category: Scene Inspector
+tags: scene inspector, fields, threads, branches, merges
+contextKey: sceneInspector.fields.threadTarget
+micro: Choose target plot lines for branch, split or merge events.
+quickTitle: Thread targets
+quickSummary: Targets explain where a thread branches, splits or merges so Timeline lanes can show the story shape.
+screenshot:
+---
+
+# Overview
+
+Use a target plot line when an event creates or joins story lanes. Branch points to a new related lane, split can target several lanes, and merge shows where separate concerns come together.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/ThreadType.md b/PlotLine/Help/Articles/SceneInspector/Fields/ThreadType.md
new file mode 100644
index 0000000..d332b75
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/ThreadType.md
@@ -0,0 +1,14 @@
+---
+title: Thread Type
+category: Scene Inspector
+tags: scene inspector, fields, threads
+contextKey: sceneInspector.fields.threadType
+micro: Classify a new thread by narrative purpose.
+quickTitle: Thread type
+quickSummary: Thread type helps distinguish mystery questions, relationship arcs, promises, subplots and other unresolved story concerns.
+screenshot:
+---
+
+# Overview
+
+Use thread type to make later review easier. A mystery thread, emotional promise and relationship subplot may all need different kinds of development and payoff.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/TimeConfidence.md b/PlotLine/Help/Articles/SceneInspector/Fields/TimeConfidence.md
new file mode 100644
index 0000000..5efb497
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/TimeConfidence.md
@@ -0,0 +1,14 @@
+---
+title: Time Confidence
+category: Scene Inspector
+tags: scene inspector, fields, time, confidence
+contextKey: sceneInspector.fields.timeConfidence
+micro: Mark how settled the scene timing is.
+quickTitle: Time confidence
+quickSummary: Time confidence separates firm chronology from provisional planning.
+screenshot:
+---
+
+# Overview
+
+Use lower confidence when timing is a placeholder. Use higher confidence when the timing is part of story truth and continuity checks should treat it as reliable.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/TimeMode.md b/PlotLine/Help/Articles/SceneInspector/Fields/TimeMode.md
new file mode 100644
index 0000000..fb3177e
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/TimeMode.md
@@ -0,0 +1,16 @@
+---
+title: Time Mode
+category: Scene Inspector
+tags: scene inspector, fields, time, continuity
+contextKey: sceneInspector.fields.timeMode
+micro: Choose how precisely the scene's time is known.
+quickTitle: Time mode
+quickSummary: Time mode controls whether exact date, exact date-time or relative timing fields are used for chronology and continuity.
+screenshot:
+---
+
+# Overview
+
+Use exact date-time when hour-level order matters, such as alibis, travel, deadlines or overlapping scenes. Use exact date when the day matters but the hour does not. Use relative or loose timing when the draft only needs "later that night" or "three weeks later".
+
+The visible date and time inputs change with the mode. More precise modes give continuity checks stronger evidence; looser modes are useful while outlining.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/UpdateAssetLocation.md b/PlotLine/Help/Articles/SceneInspector/Fields/UpdateAssetLocation.md
new file mode 100644
index 0000000..1fded56
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/UpdateAssetLocation.md
@@ -0,0 +1,14 @@
+---
+title: Update Current Location
+category: Scene Inspector
+tags: scene inspector, fields, assets, locations
+contextKey: sceneInspector.fields.updateAssetLocation
+micro: Decide whether this scene should become the asset's current location.
+quickTitle: Update current location
+quickSummary: Tick this when the scene establishes the asset's new last-known location for future continuity.
+screenshot:
+---
+
+# Overview
+
+Leave this ticked when the object really moves or is confirmed here. Untick it when the scene only mentions a past location or hypothetical location.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/WarningActions.md b/PlotLine/Help/Articles/SceneInspector/Fields/WarningActions.md
new file mode 100644
index 0000000..d090aea
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/WarningActions.md
@@ -0,0 +1,14 @@
+---
+title: Warning Actions
+category: Scene Inspector
+tags: scene inspector, fields, warnings
+contextKey: sceneInspector.fields.warningActions
+micro: Decide how to handle a continuity warning.
+quickTitle: Warning actions
+quickSummary: Validate, dismiss and intentional actions help you investigate warnings without losing deliberate story choices.
+screenshot:
+---
+
+# Overview
+
+Validate after major scene changes. Dismiss a warning when it is no longer useful. Mark intentional when the apparent contradiction is a deliberate author choice you still want recorded.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/WriterBlocked.md b/PlotLine/Help/Articles/SceneInspector/Fields/WriterBlocked.md
new file mode 100644
index 0000000..2e1b785
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/WriterBlocked.md
@@ -0,0 +1,14 @@
+---
+title: Writer Blocked
+category: Scene Inspector
+tags: scene inspector, fields, writer workspace, blockers
+contextKey: sceneInspector.fields.writerBlocked
+micro: Mark a scene as blocked when writing cannot proceed normally.
+quickTitle: Blocked scene
+quickSummary: Blocked scenes can be surfaced in writing workflow so you can resolve the reason before drafting.
+screenshot:
+---
+
+# Overview
+
+Tick Blocked when the scene needs research, a plot decision, continuity repair or another dependency before it can move forward. Use the reason field to name the obstacle.
diff --git a/PlotLine/Help/Articles/SceneInspector/Fields/WriterPriority.md b/PlotLine/Help/Articles/SceneInspector/Fields/WriterPriority.md
new file mode 100644
index 0000000..d8f06f3
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Fields/WriterPriority.md
@@ -0,0 +1,14 @@
+---
+title: Writer Priority
+category: Scene Inspector
+tags: scene inspector, fields, writer workspace
+contextKey: sceneInspector.fields.writerPriority
+micro: Set how urgent this scene is for drafting or revision.
+quickTitle: Writer priority
+quickSummary: Priority helps writing queues and project workflow surface the scenes that need attention first.
+screenshot:
+---
+
+# Overview
+
+Use higher priority for blocked structural scenes, scenes needed before others can be drafted, or revision work that unlocks the next pass.
diff --git a/PlotLine/Help/Articles/SceneInspector/Knowledge.md b/PlotLine/Help/Articles/SceneInspector/Knowledge.md
index f7ef3b6..7c3e709 100644
--- a/PlotLine/Help/Articles/SceneInspector/Knowledge.md
+++ b/PlotLine/Help/Articles/SceneInspector/Knowledge.md
@@ -37,6 +37,12 @@ Reader knowledge is separate from character knowledge. If the reader knows the v
Use knowledge events for reveals, discoveries, corrected assumptions, regressions and secrets changing hands. Continuity warnings can then help find scenes where a character acts on information they should not yet have, or fails to know something they already learned.
+# Mystery And Dramatic Irony
+
+Knowledge is especially useful for mysteries, thrillers, conspiracies and romance secrets. It lets you separate what the reader knows from what each character knows. That makes fair clues, hidden motives, mistaken beliefs and delayed reveals much easier to audit.
+
+You do not need to record every fact. Track knowledge when it changes what a character can reasonably say, suspect, hide, reveal or act on.
+
# Related Guides
- [Continuity Warnings](/Help/Article/warnings.overview)
diff --git a/PlotLine/Help/Articles/SceneInspector/Locations.md b/PlotLine/Help/Articles/SceneInspector/Locations.md
index 4681a2b..f26cde4 100644
--- a/PlotLine/Help/Articles/SceneInspector/Locations.md
+++ b/PlotLine/Help/Articles/SceneInspector/Locations.md
@@ -15,6 +15,12 @@ Asset locations record where an important object is during this scene. Use them
This is useful for hidden evidence, parked vehicles, locked rooms, documents left on a desk or objects that can be found later.
+# Movement And Last Known Location
+
+When you update an asset's current location, this scene becomes evidence for where the object should be after this point. That helps future continuity checks catch objects that appear somewhere else without a recorded move.
+
+If the scene only mentions an old location, do not update current location. Use the description to explain the reference instead.
+
# Related Guides
- [Assets](/Help/Article/sceneInspector.assets)
diff --git a/PlotLine/Help/Articles/SceneInspector/Move.md b/PlotLine/Help/Articles/SceneInspector/Move.md
new file mode 100644
index 0000000..f6f96d9
--- /dev/null
+++ b/PlotLine/Help/Articles/SceneInspector/Move.md
@@ -0,0 +1,22 @@
+---
+title: Move and Reorder
+category: Scene Inspector
+tags: scene inspector, move, reorder, structure
+contextKey: sceneInspector.move
+micro: Move a scene while preserving its planning links.
+quickTitle: Move and reorder
+quickSummary: Move and reorder controls help restructure chapters while keeping scene-linked characters, threads, assets, metrics and warnings with the scene.
+screenshot:
+---
+
+# Overview
+
+Move and Reorder is for structural editing. Use it when a scene belongs in a different chapter or should sit at the start or end of the current chapter.
+
+Moving a scene does not mean rewriting its planning data. The scene keeps its characters, assets, plot thread events, metrics, notes, warnings and attachments. After moving, review chronology, dependencies and continuity warnings because the same event may now occur at a different point in the story.
+
+# Related Guides
+
+- [Timeline](/Help/Article/timeline.overview)
+- [Scene Dependencies](/Help/Article/sceneInspector.dependencies)
+- [Continuity Warnings](/Help/Article/sceneInspector.warnings)
diff --git a/PlotLine/Help/Articles/SceneInspector/Relationships.md b/PlotLine/Help/Articles/SceneInspector/Relationships.md
index 4bd5a52..8ab7def 100644
--- a/PlotLine/Help/Articles/SceneInspector/Relationships.md
+++ b/PlotLine/Help/Articles/SceneInspector/Relationships.md
@@ -29,6 +29,12 @@ Intensity records relationship strength. A low-intensity rivalry might be irrita
Use events when the relationship state changes in this scene. This helps you see whether a breakup has setup, whether forgiveness arrives too quickly, or whether a character behaves as if a relationship has changed before the scene that actually changes it.
+# How Much To Fill In
+
+You do not need to populate every field for every relationship event. If the scene only nudges an existing friendship, choose the relationship and state. If the scene creates a new bond, choose the characters and type. If one person knows and the other does not, use direction and knowledge deliberately.
+
+The goal is to capture meaningful relationship movement, not to turn every conversation into admin.
+
# Related Guides
- [Characters](/Help/Article/characters.overview)
diff --git a/PlotLine/Help/Articles/SceneInspector/Threads.md b/PlotLine/Help/Articles/SceneInspector/Threads.md
index e4332d3..5c7ecf9 100644
--- a/PlotLine/Help/Articles/SceneInspector/Threads.md
+++ b/PlotLine/Help/Articles/SceneInspector/Threads.md
@@ -19,6 +19,12 @@ Use importance to show how central a thread is. Use lifecycle events to show whe
Thread events prevent story promises from becoming invisible. If a clue is planted, mark it. If the reader receives a reveal, mark it. If a subplot is intentionally abandoned, mark that too so thread health knows the silence is deliberate.
+# Thread Health
+
+Thread health uses the pattern of events to highlight possible neglected, dangling, questionable or abandoned threads. These are prompts for revision, not automatic mistakes.
+
+For example, a clue thread that starts in chapter two and then disappears for ten scenes may be a deliberate slow burn, or it may be a forgotten promise. Marking progress, reveal, merge, resolve or abandon events helps the Timeline show the difference.
+
# Related Guides
- [Plot Thread Lanes](/Help/Article/timeline.plotThreadLanes)
diff --git a/PlotLine/Help/Articles/SceneInspector/Time.md b/PlotLine/Help/Articles/SceneInspector/Time.md
index 9a22401..1a60298 100644
--- a/PlotLine/Help/Articles/SceneInspector/Time.md
+++ b/PlotLine/Help/Articles/SceneInspector/Time.md
@@ -15,6 +15,20 @@ Time fields tell PlotDirector when a scene happens. Use exact dates when chronol
Accurate time helps continuity checks find impossible sequences, age issues, travel gaps and story events that happen in the wrong order.
+# Time Modes
+
+Exact date-time is best when hours or minutes matter: alibis, overlapping scenes, travel deadlines, injuries, messages, curfews or timed reveals.
+
+Exact date is best when the day matters but the hour does not. This is often enough for birthdays, school days, public events, journeys or multi-day investigations.
+
+Relative or loose timing is useful while planning. "Later that night" may be more helpful than a precise date during early drafting.
+
+The visible date and time fields change depending on the mode. More precise timing gives Timeline, age checks and continuity validation stronger evidence. Looser timing keeps the outline flexible.
+
+# Writer Tip
+
+Do not force precision too early. Use exact timing when the story depends on it; otherwise use confidence and relative time to show that the chronology is still being shaped.
+
# Related Guides
- [Continuity Warnings](/Help/Article/warnings.overview)
diff --git a/PlotLine/Help/Articles/SceneInspector/Warnings.md b/PlotLine/Help/Articles/SceneInspector/Warnings.md
index 922c8ed..5b0c42e 100644
--- a/PlotLine/Help/Articles/SceneInspector/Warnings.md
+++ b/PlotLine/Help/Articles/SceneInspector/Warnings.md
@@ -14,3 +14,13 @@ screenshot:
Warnings are prompts for review. They point to places where PlotDirector's recorded evidence suggests something may be missing, contradictory or worth checking.
Dismiss a warning when it is no longer useful. Mark it intentional when the apparent contradiction is a deliberate author choice.
+
+# How Warnings Are Generated
+
+Warnings are generated from recorded story evidence: scene order, time, characters, assets, custody, locations, knowledge, dependencies and related continuity data. A warning usually means either the story has a contradiction or PlotDirector needs more evidence to understand the intended logic.
+
+Severity helps triage. Investigate high-severity warnings first, then review lower-severity prompts during cleanup passes.
+
+# Investigation Workflow
+
+Read the warning, inspect the scene data, then decide whether to fix the underlying story evidence, add missing detail, dismiss the warning or mark it intentional.
diff --git a/PlotLine/Help/Articles/SceneInspector/Writer.md b/PlotLine/Help/Articles/SceneInspector/Writer.md
index 75769ff..e392b10 100644
--- a/PlotLine/Help/Articles/SceneInspector/Writer.md
+++ b/PlotLine/Help/Articles/SceneInspector/Writer.md
@@ -14,3 +14,9 @@ screenshot:
Writer Workspace fields are practical drafting tools. They help you decide what to write next, estimate effort, record progress and mark blockers.
These fields do not change story continuity. They support the working process around the scene.
+
+# How It Connects
+
+Writer Workspace information can support project overview, writing progress, revision workflow, writing plans and Word Companion workflows. Use it to record whether the scene is ready to draft, blocked, in revision, or already worked on.
+
+Priority and blockers help surface what needs attention. Word counts and worked-on dates help progress tracking. Revision status belongs with the scene because it describes the scene's writing state.
diff --git a/PlotLine/Help/Articles/Timeline/Fields/ChapterRange.md b/PlotLine/Help/Articles/Timeline/Fields/ChapterRange.md
new file mode 100644
index 0000000..0a3a74b
--- /dev/null
+++ b/PlotLine/Help/Articles/Timeline/Fields/ChapterRange.md
@@ -0,0 +1,14 @@
+---
+title: Timeline Chapter Range
+category: Timeline
+tags: timeline, fields, filters, chapters
+contextKey: timeline.fields.chapterRange
+micro: Limit the Timeline to a chapter span.
+quickTitle: Chapter range
+quickSummary: Chapter range filters show only the selected structural span while keeping matching context inside that range.
+screenshot:
+---
+
+# Overview
+
+Use chapter range filters when you are reviewing one act, sequence or revision pass rather than the whole book. Scenes outside the selected chapter span are hidden from the filtered view; the story data itself is unchanged.
diff --git a/PlotLine/Help/Articles/Timeline/Fields/Density.md b/PlotLine/Help/Articles/Timeline/Fields/Density.md
new file mode 100644
index 0000000..8c86ffc
--- /dev/null
+++ b/PlotLine/Help/Articles/Timeline/Fields/Density.md
@@ -0,0 +1,14 @@
+---
+title: Timeline Density
+category: Timeline
+tags: timeline, fields, density, view
+contextKey: timeline.fields.density
+micro: Choose how compact the Timeline appears.
+quickTitle: Density
+quickSummary: Density changes how much space each scene card and lane uses without changing story data.
+screenshot:
+---
+
+# Overview
+
+Use compact density for scanning a large book. Use expanded density when you need more readable scene summaries and lane detail.
diff --git a/PlotLine/Help/Articles/Timeline/Fields/DragAssetDependency.md b/PlotLine/Help/Articles/Timeline/Fields/DragAssetDependency.md
new file mode 100644
index 0000000..32934b7
--- /dev/null
+++ b/PlotLine/Help/Articles/Timeline/Fields/DragAssetDependency.md
@@ -0,0 +1,14 @@
+---
+title: Timeline Asset Dependency Drop
+category: Timeline
+tags: timeline, fields, assets, dependencies, drag drop
+contextKey: timeline.fields.dragAssetDependency
+micro: Connect two assets when one depends on the other.
+quickTitle: Asset dependency drop
+quickSummary: Asset dependency fields describe how one asset's state affects another object's availability or meaning.
+screenshot:
+---
+
+# Overview
+
+Use dependencies for linked objects: a key unlocks a box, a document validates a clue, a battery powers a device, or evidence blocks a false alibi.
diff --git a/PlotLine/Help/Articles/Timeline/Fields/DragAssetEvent.md b/PlotLine/Help/Articles/Timeline/Fields/DragAssetEvent.md
new file mode 100644
index 0000000..decfa09
--- /dev/null
+++ b/PlotLine/Help/Articles/Timeline/Fields/DragAssetEvent.md
@@ -0,0 +1,14 @@
+---
+title: Timeline Asset Drop Event
+category: Timeline
+tags: timeline, fields, assets, drag drop
+contextKey: timeline.fields.dragAssetEvent
+micro: Record what happens to a dropped asset in the scene.
+quickTitle: Dropped asset event
+quickSummary: Asset drop fields turn a quick Timeline action into continuity evidence for object state, location and custody.
+screenshot:
+---
+
+# Overview
+
+Use event type to describe what happens to the object. Use state transition when its story condition changes, such as hidden to found, intact to damaged, or unknown to revealed.
diff --git a/PlotLine/Help/Articles/Timeline/Fields/DragCharacterRole.md b/PlotLine/Help/Articles/Timeline/Fields/DragCharacterRole.md
new file mode 100644
index 0000000..1048b1f
--- /dev/null
+++ b/PlotLine/Help/Articles/Timeline/Fields/DragCharacterRole.md
@@ -0,0 +1,14 @@
+---
+title: Timeline Character Drop Role
+category: Timeline
+tags: timeline, fields, characters, drag drop
+contextKey: timeline.fields.dragCharacterRole
+micro: Choose how a dropped character participates in the scene.
+quickTitle: Dropped character role
+quickSummary: Role and presence decide whether a character is a POV, main participant, background presence or mentioned figure.
+screenshot:
+---
+
+# Overview
+
+When dropping a character onto a scene, choose role and presence to record how the scene uses them. This affects character lanes, POV review and continuity.
diff --git a/PlotLine/Help/Articles/Timeline/Fields/DragLocationRelationship.md b/PlotLine/Help/Articles/Timeline/Fields/DragLocationRelationship.md
new file mode 100644
index 0000000..b4e601f
--- /dev/null
+++ b/PlotLine/Help/Articles/Timeline/Fields/DragLocationRelationship.md
@@ -0,0 +1,14 @@
+---
+title: Timeline Location Relationship Drop
+category: Timeline
+tags: timeline, fields, locations, drag drop
+contextKey: timeline.fields.dragLocationRelationship
+micro: Describe how two locations connect.
+quickTitle: Location relationship drop
+quickSummary: Location relationship fields help continuity understand hearing, visibility and travel between places.
+screenshot:
+---
+
+# Overview
+
+Use these fields when spatial relationships matter. If two rooms share a wall, a hallway connects them, or a character can hear through a door, the relationship can support later continuity reasoning.
diff --git a/PlotLine/Help/Articles/Timeline/Fields/JumpControls.md b/PlotLine/Help/Articles/Timeline/Fields/JumpControls.md
new file mode 100644
index 0000000..d9c3224
--- /dev/null
+++ b/PlotLine/Help/Articles/Timeline/Fields/JumpControls.md
@@ -0,0 +1,14 @@
+---
+title: Timeline Jump Controls
+category: Timeline
+tags: timeline, fields, jump, navigation
+contextKey: timeline.fields.jumpControls
+micro: Move quickly to scenes, warnings or lane items.
+quickTitle: Jump controls
+quickSummary: Jump controls are navigation shortcuts for large timelines; they do not change filters or story data.
+screenshot:
+---
+
+# Overview
+
+Use scene jump when you know the scene. Use warning jump during continuity review. Use lane item jump when you want the first visible occurrence of a character, asset or plot line.
diff --git a/PlotLine/Help/Articles/Timeline/Fields/LocationFilter.md b/PlotLine/Help/Articles/Timeline/Fields/LocationFilter.md
new file mode 100644
index 0000000..3ec8c4b
--- /dev/null
+++ b/PlotLine/Help/Articles/Timeline/Fields/LocationFilter.md
@@ -0,0 +1,14 @@
+---
+title: Timeline Location Filter
+category: Timeline
+tags: timeline, fields, filters, locations
+contextKey: timeline.fields.locationFilter
+micro: Show scenes connected to a location.
+quickTitle: Location filter
+quickSummary: Location filters help you follow where scenes happen and where continuity may depend on place.
+screenshot:
+---
+
+# Overview
+
+Use the location filter when geography matters: who could hear something, whether a character can travel in time, or where an asset was last seen. Matching scenes remain visible; unrelated scenes are dimmed or hidden by the current filter lens.
diff --git a/PlotLine/Help/Articles/Timeline/Fields/PovCharacterFilter.md b/PlotLine/Help/Articles/Timeline/Fields/PovCharacterFilter.md
new file mode 100644
index 0000000..edd370f
--- /dev/null
+++ b/PlotLine/Help/Articles/Timeline/Fields/PovCharacterFilter.md
@@ -0,0 +1,14 @@
+---
+title: Timeline POV Character Filter
+category: Timeline
+tags: timeline, fields, pov, characters
+contextKey: timeline.fields.povCharacter
+micro: Focus on scenes told through a point-of-view character.
+quickTitle: POV character
+quickSummary: POV filters help you review viewpoint balance, character access to information and reader experience.
+screenshot:
+---
+
+# Overview
+
+Use the POV character filter to review who is carrying the reader through the story. It is especially useful for multi-POV books, mysteries where knowledge is limited, and scenes where reader access matters.
diff --git a/PlotLine/Help/Articles/Timeline/Fields/RevisionStatusFilter.md b/PlotLine/Help/Articles/Timeline/Fields/RevisionStatusFilter.md
new file mode 100644
index 0000000..20dcb81
--- /dev/null
+++ b/PlotLine/Help/Articles/Timeline/Fields/RevisionStatusFilter.md
@@ -0,0 +1,14 @@
+---
+title: Timeline Revision Status Filter
+category: Timeline
+tags: timeline, fields, revision, filters
+contextKey: timeline.fields.revisionStatus
+micro: Focus the Timeline by drafting or revision state.
+quickTitle: Revision status
+quickSummary: Revision status filters help you review scenes that are planned, drafted, revised or ready.
+screenshot:
+---
+
+# Overview
+
+Use revision status filters to plan work. For example, show only outline scenes before drafting, or show only revision-needed scenes before a polishing pass.
diff --git a/PlotLine/Help/Articles/Timeline/Fields/ScenePurposeFilter.md b/PlotLine/Help/Articles/Timeline/Fields/ScenePurposeFilter.md
new file mode 100644
index 0000000..cff54d0
--- /dev/null
+++ b/PlotLine/Help/Articles/Timeline/Fields/ScenePurposeFilter.md
@@ -0,0 +1,14 @@
+---
+title: Timeline Scene Purpose Filter
+category: Timeline
+tags: timeline, fields, scene purpose, filters
+contextKey: timeline.fields.scenePurpose
+micro: Show scenes with a particular narrative job.
+quickTitle: Scene purpose
+quickSummary: Purpose filters help you find reveals, payoffs, transitions, action beats or relationship scenes.
+screenshot:
+---
+
+# Overview
+
+Use purpose filters to inspect story balance. If a section has too many setup scenes and not enough payoff, or if relationship development disappears, this filter helps you see it.
diff --git a/PlotLine/Help/Articles/Timeline/Fields/SceneRange.md b/PlotLine/Help/Articles/Timeline/Fields/SceneRange.md
new file mode 100644
index 0000000..afd48a6
--- /dev/null
+++ b/PlotLine/Help/Articles/Timeline/Fields/SceneRange.md
@@ -0,0 +1,14 @@
+---
+title: Timeline Scene Range
+category: Timeline
+tags: timeline, fields, filters, scenes
+contextKey: timeline.fields.sceneRange
+micro: Limit the Timeline to a scene span.
+quickTitle: Scene range
+quickSummary: Scene range filters help you inspect a tight run of scenes without changing the story order.
+screenshot:
+---
+
+# Overview
+
+Use scene range filters for close revision: a chase sequence, a clue chain, a relationship turn or the run-up to a chapter ending. Scenes outside the range are hidden only for the current Timeline view.
diff --git a/PlotLine/Help/Articles/Timeline/Fields/WarningOptions.md b/PlotLine/Help/Articles/Timeline/Fields/WarningOptions.md
new file mode 100644
index 0000000..8e3d635
--- /dev/null
+++ b/PlotLine/Help/Articles/Timeline/Fields/WarningOptions.md
@@ -0,0 +1,14 @@
+---
+title: Timeline Warning Options
+category: Timeline
+tags: timeline, fields, warnings, filters
+contextKey: timeline.fields.warningOptions
+micro: Choose which warning states appear in the Timeline.
+quickTitle: Warning options
+quickSummary: Warning options let you include only active warnings or also review dismissed and intentional warnings.
+screenshot:
+---
+
+# Overview
+
+Use "Warnings only" for a continuity pass. Include dismissed warnings when you want to audit old decisions. Include intentional warnings when a contradiction is deliberate but still worth seeing in context.
diff --git a/PlotLine/Help/Articles/Timeline/Fields/WarningSeverityFilter.md b/PlotLine/Help/Articles/Timeline/Fields/WarningSeverityFilter.md
new file mode 100644
index 0000000..23dd3ff
--- /dev/null
+++ b/PlotLine/Help/Articles/Timeline/Fields/WarningSeverityFilter.md
@@ -0,0 +1,14 @@
+---
+title: Timeline Warning Severity Filter
+category: Timeline
+tags: timeline, fields, warnings, filters
+contextKey: timeline.fields.warningSeverity
+micro: Focus on warnings by seriousness.
+quickTitle: Warning severity
+quickSummary: Severity filters help you review critical continuity issues before lower-risk reminders.
+screenshot:
+---
+
+# Overview
+
+Use severity when you want to triage warnings. High-severity warnings usually deserve attention before smaller consistency prompts. The filter changes the warning review lens, not the underlying warnings.
diff --git a/PlotLine/Help/Articles/Timeline/Fields/WarningTypeFilter.md b/PlotLine/Help/Articles/Timeline/Fields/WarningTypeFilter.md
new file mode 100644
index 0000000..7dd70b3
--- /dev/null
+++ b/PlotLine/Help/Articles/Timeline/Fields/WarningTypeFilter.md
@@ -0,0 +1,14 @@
+---
+title: Timeline Warning Type Filter
+category: Timeline
+tags: timeline, fields, warnings, filters
+contextKey: timeline.fields.warningType
+micro: Focus on one kind of continuity issue.
+quickTitle: Warning type
+quickSummary: Warning type filters help you review one class of continuity issue at a time.
+screenshot:
+---
+
+# Overview
+
+Use warning type when you are doing a targeted pass, such as locations, asset custody, knowledge, age or unresolved threads. This keeps the review focused and reduces noise.
diff --git a/PlotLine/Help/Articles/Timeline/Fields/Zoom.md b/PlotLine/Help/Articles/Timeline/Fields/Zoom.md
new file mode 100644
index 0000000..de8ee71
--- /dev/null
+++ b/PlotLine/Help/Articles/Timeline/Fields/Zoom.md
@@ -0,0 +1,14 @@
+---
+title: Timeline Zoom
+category: Timeline
+tags: timeline, fields, zoom, view
+contextKey: timeline.fields.zoom
+micro: Choose the level of Timeline detail.
+quickTitle: Zoom
+quickSummary: Zoom changes whether the Timeline feels like a book overview, chapter review or scene-level inspection.
+screenshot:
+---
+
+# Overview
+
+Use book zoom to see overall shape, chapter zoom for structural review, and scene detail when you are checking individual beats.
diff --git a/PlotLine/Views/Scenes/_SceneInspector.cshtml b/PlotLine/Views/Scenes/_SceneInspector.cshtml
index 7e65044..4367b57 100644
--- a/PlotLine/Views/Scenes/_SceneInspector.cshtml
+++ b/PlotLine/Views/Scenes/_SceneInspector.cshtml
@@ -116,7 +116,7 @@