Add contextual help across Story Intelligence pages

PlotLine.Tests/Program.cs

@@ -836,7 +836,7 @@ static void StoryIntelligenceReviewCentreUsesIndependentTileGrid()
         "\"Characters\"",
         "\"Assets\"",
         "\"Knowledge\"",
-        "<h2>Locations</h2>",
+        "<h2>Locations ",
         "ReviewPlotSynthesis()",
         "\"Relationships\"",
         "ReviewMetrics"
@@ -1011,7 +1011,8 @@ static void StoryIntelligenceReviewModulePagesOmitWizardChrome()
         var view = File.ReadAllText(Path.Combine(root, "Views/Onboarding", viewName));
         Assert(view.Contains("<p class=\"eyebrow\">Story Intelligence</p>", StringComparison.Ordinal), $"{viewName} should use a simple module header eyebrow.");
         Assert(view.Contains("StoryIntelligenceReviewCentre", StringComparison.Ordinal), $"{viewName} should return to Review Centre.");
-        Assert(view.Contains($">{title}</h1>", StringComparison.Ordinal), $"{viewName} should keep its focused module title.");
+        var headingMarkup = System.Text.RegularExpressions.Regex.Replace(view, @"\s*<help-icon\b[^>]*/>", string.Empty);
+        Assert(headingMarkup.Contains($">{title}</h1>", StringComparison.Ordinal), $"{viewName} should keep its focused module title alongside contextual help.");
         Assert(view.Contains("summary class=\"story-review-card-header\"", StringComparison.Ordinal), $"{viewName} should give each candidate panel a clear shared header.");
         Assert(!view.Contains("StoryIntelligenceComplete", StringComparison.Ordinal), $"{viewName} should not route to the old final wizard step.");
         foreach (var marker in forbidden)

PlotLine/Help/Articles/StoryIntelligence/Admin/ChapterResult.md

@@ -0,0 +1,18 @@
+---
+title: Chapter Analysis Result
+category: Story Intelligence Admin
+tags: story intelligence, admin, chapterResult
+contextKey: storyIntelligence.admin.chapterResult
+micro: Check detected structure and validation before inspecting scene details.
+quickTitle: Chapter Analysis Result
+quickSummary: Check detected structure and validation before inspecting scene details.
+screenshot:
+---
+
+# Chapter Analysis Result
+
+Compare the chapter summary and scene boundaries with the source manuscript. Warnings or invalid structure can explain missing scene results. Diagnostic output is evidence for review, not an automatic correction of the source.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/ChapterTest.md

@@ -0,0 +1,29 @@
+---
+title: Combined Chapter Analysis Test
+category: Story Intelligence Admin
+tags: story intelligence, admin, chapterTest
+contextKey: storyIntelligence.admin.chapterTest
+micro: Test scene detection and scene analysis together on supplied chapter text.
+quickTitle: Combined Chapter Analysis Test
+quickSummary: Test scene detection and scene analysis together on supplied chapter text.
+screenshot:
+---
+
+# Combined Chapter Analysis Test
+
+Use a chapter with representative scene boundaries. Review the chapter structure, detected scenes and individual scene analysis results. The test makes live requests. Inspect results before using any offered action to save the test as a run; saving a run is distinct from importing scenes into the book.
+
+# Understanding the Fields
+
+| Field | Suggested use |
+| --- | --- |
+| [Analysis Project Context](/Help/Article/storyIntelligence.admin.fields.project) | Use the project that owns the manuscript being tested. |
+| [Analysis Book Context](/Help/Article/storyIntelligence.admin.fields.book) | Use the book that contains the chapter under analysis. |
+| [Analysis Chapter Context](/Help/Article/storyIntelligence.admin.fields.chapter) | Use the saved chapter identity for the source text. |
+| [Analysis Chapter Number](/Help/Article/storyIntelligence.admin.fields.chapterNumber) | Give the chapter position used to describe the test source. |
+| [Analysis Source Label](/Help/Article/storyIntelligence.admin.fields.sourceLabel) | Give this test a recognisable label for later comparison. |
+| [Chapter Test Source Text](/Help/Article/storyIntelligence.admin.fields.chapterText) | Supply complete chapter prose with its paragraph and scene breaks. |
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Commit.md

@@ -0,0 +1,20 @@
+---
+title: Confirming an Admin Scene Import
+category: Story Intelligence Admin
+tags: story intelligence, admin, commit
+contextKey: storyIntelligence.admin.commit
+micro: Check the target and proposed scene changes before committing an admin run.
+quickTitle: Confirming an Admin Scene Import
+quickSummary: Check the target and proposed scene changes before committing an admin run.
+screenshot:
+---
+
+# Confirming an Admin Scene Import
+
+This administration workflow creates scenes and scene intelligence from a completed run. Confirm the project, book, chapter, scene count and metrics. Characters, locations, assets, relationships and knowledge remain preview-only in this import step.
+
+Read blockers and warnings before importing. This mode does not merge, replace or overwrite existing scene content. An already completed commit is reported here. Return to the run if the target or results are wrong.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Configuration.md

@@ -0,0 +1,18 @@
+---
+title: Analysis Configuration Status
+category: Story Intelligence Admin
+tags: story intelligence, admin, configuration
+contextKey: storyIntelligence.admin.configuration
+micro: Check configured models, credentials availability and connection status.
+quickTitle: Analysis Configuration Status
+quickSummary: Check configured models, credentials availability and connection status.
+screenshot:
+---
+
+# Analysis Configuration Status
+
+These indicators describe the analysis service configuration. A configured key does not by itself guarantee a successful live request; also inspect connection status and errors. The page reports availability, not the secret value.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Diagnostics.md

@@ -0,0 +1,14 @@
+---
+title: Story Intelligence Diagnostics
+category: Story Intelligence Admin
+tags: story intelligence, admin, diagnostics
+contextKey: storyIntelligence.admin.diagnostics
+micro: Inspect analysis configuration and use the available administration tools.
+quickTitle: Story Intelligence Diagnostics
+quickSummary: Inspect analysis configuration and use the available administration tools.
+screenshot:
+---
+
+# Story Intelligence Diagnostics
+
+This admin page reports configured models, connectivity and prompt availability. Use it when investigating why analysis cannot start or produces errors. The manual test links run diagnostics; the development reset is a separate destructive operation, not a retry button.

PlotLine/Help/Articles/StoryIntelligence/Admin/ExistingChapter.md

@@ -0,0 +1,26 @@
+---
+title: Analyse an Existing Chapter
+category: Story Intelligence Admin
+tags: story intelligence, admin, existingChapter
+contextKey: storyIntelligence.admin.existingChapter
+micro: Select a saved chapter as the source for an administration test run.
+quickTitle: Analyse an Existing Chapter
+quickSummary: Select a saved chapter as the source for an administration test run.
+screenshot:
+---
+
+# Analyse an Existing Chapter
+
+Choose Project, Book and Chapter, then Load selection to inspect the source. Confirm that manuscript text is available before queueing. Loading the selection reads the source; Queue Story Intelligence run starts a saved background analysis. Review its results separately before any import.
+
+# Understanding the Fields
+
+| Field | Suggested use |
+| --- | --- |
+| [Analysis Project Context](/Help/Article/storyIntelligence.admin.fields.project) | Use the project that owns the manuscript being tested. |
+| [Analysis Book Context](/Help/Article/storyIntelligence.admin.fields.book) | Use the book that contains the chapter under analysis. |
+| [Analysis Chapter Context](/Help/Article/storyIntelligence.admin.fields.chapter) | Use the saved chapter identity for the source text. |
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Fields/Book.md

@@ -0,0 +1,18 @@
+---
+title: Analysis Book Context
+category: Story Intelligence Admin
+tags: story intelligence, admin, fields, book
+contextKey: storyIntelligence.admin.fields.book
+micro: Use the book that contains the chapter under analysis.
+quickTitle: Analysis Book Context
+quickSummary: Use the book that contains the chapter under analysis.
+screenshot:
+---
+
+# Analysis Book Context
+
+Choose or enter the saved book identity within the selected project. This supplies book context for the test. A book ID is not a volume number or book title.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Fields/Chapter.md

@@ -0,0 +1,18 @@
+---
+title: Analysis Chapter Context
+category: Story Intelligence Admin
+tags: story intelligence, admin, fields, chapter
+contextKey: storyIntelligence.admin.fields.chapter
+micro: Use the saved chapter identity for the source text.
+quickTitle: Analysis Chapter Context
+quickSummary: Use the saved chapter identity for the source text.
+screenshot:
+---
+
+# Analysis Chapter Context
+
+Select or enter the chapter record within the chosen book. Chapter ID and chapter number are different: the ID identifies the stored record, while the number gives its position in the story.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Fields/ChapterModel.md

@@ -0,0 +1,18 @@
+---
+title: Chapter Structure Test Model
+category: Story Intelligence Admin
+tags: story intelligence, admin, fields, chapterModel
+contextKey: storyIntelligence.admin.fields.chapterModel
+micro: Choose the model used to detect chapter structure in this test.
+quickTitle: Chapter Structure Test Model
+quickSummary: Choose the model used to detect chapter structure in this test.
+screenshot:
+---
+
+# Chapter Structure Test Model
+
+Use the available model list to compare chapter and scene boundary results. This affects the test run rather than changing the application default. Review pre-flight estimates after changing models.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Fields/ChapterNumber.md

@@ -0,0 +1,18 @@
+---
+title: Analysis Chapter Number
+category: Story Intelligence Admin
+tags: story intelligence, admin, fields, chapterNumber
+contextKey: storyIntelligence.admin.fields.chapterNumber
+micro: Give the chapter position used to describe the test source.
+quickTitle: Analysis Chapter Number
+quickSummary: Give the chapter position used to describe the test source.
+screenshot:
+---
+
+# Analysis Chapter Number
+
+Use the story chapter number for the supplied text. This is contextual numbering and is distinct from the saved Chapter ID.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Fields/ChapterText.md

@@ -0,0 +1,18 @@
+---
+title: Chapter Test Source Text
+category: Story Intelligence Admin
+tags: story intelligence, admin, fields, chapterText
+contextKey: storyIntelligence.admin.fields.chapterText
+micro: Supply complete chapter prose with its paragraph and scene breaks.
+quickTitle: Chapter Test Source Text
+quickSummary: Supply complete chapter prose with its paragraph and scene breaks.
+screenshot:
+---
+
+# Chapter Test Source Text
+
+Paste the chapter you want to test rather than a summary. Preserve paragraph breaks and scene separators so the chapter structure can be evaluated. For the full chapter test, a supplied .txt upload takes precedence over pasted text.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Fields/IllustrationCategory.md

@@ -0,0 +1,18 @@
+---
+title: Illustration Category Filter
+category: Story Intelligence Admin
+tags: story intelligence, admin, fields, illustrationCategory
+contextKey: storyIntelligence.admin.fields.illustrationCategory
+micro: Limit the library to the kind of illustration you want to inspect.
+quickTitle: Illustration Category Filter
+quickSummary: Limit the library to the kind of illustration you want to inspect.
+screenshot:
+---
+
+# Illustration Category Filter
+
+Choose a category to narrow the displayed library items, or use the all-categories choice. Apply Filter after changing the selection. Filtering does not change an illustration or its approval.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Fields/IllustrationMetadata.md

@@ -0,0 +1,18 @@
+---
+title: Illustration Metadata
+category: Story Intelligence Admin
+tags: story intelligence, admin, fields, illustrationMetadata
+contextKey: storyIntelligence.admin.fields.illustrationMetadata
+micro: Inspect the saved descriptive details attached to the library item.
+quickTitle: Illustration Metadata
+quickSummary: Inspect the saved descriptive details attached to the library item.
+screenshot:
+---
+
+# Illustration Metadata
+
+Use the read-only metadata to understand how the item is described and organised. It is not a place to edit story facts or character identities.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Fields/IllustrationNotes.md

@@ -0,0 +1,18 @@
+---
+title: Illustration Admin Notes
+category: Story Intelligence Admin
+tags: story intelligence, admin, fields, illustrationNotes
+contextKey: storyIntelligence.admin.fields.illustrationNotes
+micro: Record review observations for this library item.
+quickTitle: Illustration Admin Notes
+quickSummary: Record review observations for this library item.
+screenshot:
+---
+
+# Illustration Admin Notes
+
+Note concrete issues such as an incorrect object, unsuitable style or why a regeneration is needed. Save notes to retain them. Notes do not themselves approve the image or change its generation prompt.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Fields/IllustrationPrompt.md

@@ -0,0 +1,18 @@
+---
+title: Illustration Generation Prompt
+category: Story Intelligence Admin
+tags: story intelligence, admin, fields, illustrationPrompt
+contextKey: storyIntelligence.admin.fields.illustrationPrompt
+micro: Read the instructions used to generate this library image.
+quickTitle: Illustration Generation Prompt
+quickSummary: Read the instructions used to generate this library image.
+screenshot:
+---
+
+# Illustration Generation Prompt
+
+Compare the prompt with the actual image when judging whether generation followed the intended brief. This displayed prompt is read-only and does not alter manuscript analysis.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Fields/IllustrationSearch.md

@@ -0,0 +1,18 @@
+---
+title: Illustration Library Search
+category: Story Intelligence Admin
+tags: story intelligence, admin, fields, illustrationSearch
+contextKey: storyIntelligence.admin.fields.illustrationSearch
+micro: Find library items matching your search text.
+quickTitle: Illustration Library Search
+quickSummary: Find library items matching your search text.
+screenshot:
+---
+
+# Illustration Library Search
+
+Enter a recognisable term from the item you want to find, then apply Filter. Combine search with category and status when the library is large.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Fields/IllustrationSpecification.md

@@ -0,0 +1,18 @@
+---
+title: Illustration Specification
+category: Story Intelligence Admin
+tags: story intelligence, admin, fields, illustrationSpecification
+contextKey: storyIntelligence.admin.fields.illustrationSpecification
+micro: Inspect the intended content and constraints for the library item.
+quickTitle: Illustration Specification
+quickSummary: Inspect the intended content and constraints for the library item.
+screenshot:
+---
+
+# Illustration Specification
+
+Use the specification alongside the generated image when deciding whether it fits its intended library role. This is generation guidance, not evidence about an individual manuscript.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Fields/IllustrationStatus.md

@@ -0,0 +1,18 @@
+---
+title: Illustration Status Filter
+category: Story Intelligence Admin
+tags: story intelligence, admin, fields, illustrationStatus
+contextKey: storyIntelligence.admin.fields.illustrationStatus
+micro: Find items at a particular generation or review stage.
+quickTitle: Illustration Status Filter
+quickSummary: Find items at a particular generation or review stage.
+screenshot:
+---
+
+# Illustration Status Filter
+
+Choose a status to inspect queued, failed, generated or reviewed work as offered in the list. Apply Filter to update the results. A generated image still needs an editorial check before approval.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Fields/ParsedOutput.md

@@ -0,0 +1,18 @@
+---
+title: Parsed Analysis Output
+category: Story Intelligence Admin
+tags: story intelligence, admin, fields, parsedOutput
+contextKey: storyIntelligence.admin.fields.parsedOutput
+micro: Inspect the structured result used for validation.
+quickTitle: Parsed Analysis Output
+quickSummary: Inspect the structured result used for validation.
+screenshot:
+---
+
+# Parsed Analysis Output
+
+This read-only JSON shows the parsed or normalised analysis result identified by the label. Compare missing or unexpected fields against the manuscript and validation messages. Editing story records happens elsewhere; these output boxes are diagnostic views.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Fields/Project.md

@@ -0,0 +1,18 @@
+---
+title: Analysis Project Context
+category: Story Intelligence Admin
+tags: story intelligence, admin, fields, project
+contextKey: storyIntelligence.admin.fields.project
+micro: Use the project that owns the manuscript being tested.
+quickTitle: Analysis Project Context
+quickSummary: Use the project that owns the manuscript being tested.
+screenshot:
+---
+
+# Analysis Project Context
+
+Select the project or enter its saved ID as the form requires. IDs identify saved records, not their order in a list. Keep the book and chapter context consistent with the selected project; do not invent an ID to describe a new project.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Fields/RawOutput.md

@@ -0,0 +1,18 @@
+---
+title: Raw Analysis Response
+category: Story Intelligence Admin
+tags: story intelligence, admin, fields, rawOutput
+contextKey: storyIntelligence.admin.fields.rawOutput
+micro: Inspect the original response when diagnosing extraction or validation errors.
+quickTitle: Raw Analysis Response
+quickSummary: Inspect the original response when diagnosing extraction or validation errors.
+screenshot:
+---
+
+# Raw Analysis Response
+
+The label distinguishes extracted assistant output from the full response. Use these read-only values to understand a failed or incomplete analysis; they are not editable manuscript fields or accepted story facts.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Fields/Scene.md

@@ -0,0 +1,18 @@
+---
+title: Analysis Scene Context
+category: Story Intelligence Admin
+tags: story intelligence, admin, fields, scene
+contextKey: storyIntelligence.admin.fields.scene
+micro: Use the saved scene identity when testing an existing scene.
+quickTitle: Analysis Scene Context
+quickSummary: Use the saved scene identity when testing an existing scene.
+screenshot:
+---
+
+# Analysis Scene Context
+
+Enter the record ID for the scene being analysed when applicable. Do not substitute its display number. Ensure the supplied text and chapter context describe the same scene.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Fields/SceneContext.md

@@ -0,0 +1,18 @@
+---
+title: Scene Test Context Output
+category: Story Intelligence Admin
+tags: story intelligence, admin, fields, sceneContext
+contextKey: storyIntelligence.admin.fields.sceneContext
+micro: Inspect the context supplied for the scene test.
+quickTitle: Scene Test Context Output
+quickSummary: Inspect the context supplied for the scene test.
+screenshot:
+---
+
+# Scene Test Context Output
+
+This read-only JSON shows the scene context assembled for analysis. Check its character, setting and chronology information when a result appears to rely on the wrong context.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Fields/SceneModel.md

@@ -0,0 +1,18 @@
+---
+title: Scene Intelligence Test Model
+category: Story Intelligence Admin
+tags: story intelligence, admin, fields, sceneModel
+contextKey: storyIntelligence.admin.fields.sceneModel
+micro: Choose the model used to analyse the detected scenes in this test.
+quickTitle: Scene Intelligence Test Model
+quickSummary: Choose the model used to analyse the detected scenes in this test.
+screenshot:
+---
+
+# Scene Intelligence Test Model
+
+Use the available model list to compare extraction quality on the same source. This choice is separate from the chapter structure model. Different choices can affect completion time, cost estimates and results.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Fields/SceneNumber.md

@@ -0,0 +1,18 @@
+---
+title: Analysis Scene Number
+category: Story Intelligence Admin
+tags: story intelligence, admin, fields, sceneNumber
+contextKey: storyIntelligence.admin.fields.sceneNumber
+micro: Give the scene position within the chapter.
+quickTitle: Analysis Scene Number
+quickSummary: Give the scene position within the chapter.
+screenshot:
+---
+
+# Analysis Scene Number
+
+Use the scene number that describes the supplied source within its chapter. This is contextual numbering and is distinct from the saved Scene ID.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Fields/SceneText.md

@@ -0,0 +1,18 @@
+---
+title: Scene Test Source Text
+category: Story Intelligence Admin
+tags: story intelligence, admin, fields, sceneText
+contextKey: storyIntelligence.admin.fields.sceneText
+micro: Supply the actual scene prose to analyse.
+quickTitle: Scene Test Source Text
+quickSummary: Supply the actual scene prose to analyse.
+screenshot:
+---
+
+# Scene Test Source Text
+
+Paste one complete scene, preserving dialogue and paragraph breaks. Use manuscript text rather than a synopsis when testing evidence extraction. Check that the IDs and numbering, if supplied, describe the same source.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Fields/SourceLabel.md

@@ -0,0 +1,18 @@
+---
+title: Analysis Source Label
+category: Story Intelligence Admin
+tags: story intelligence, admin, fields, sourceLabel
+contextKey: storyIntelligence.admin.fields.sourceLabel
+micro: Give this test a recognisable label for later comparison.
+quickTitle: Analysis Source Label
+quickSummary: Give this test a recognisable label for later comparison.
+screenshot:
+---
+
+# Analysis Source Label
+
+Use a short label such as Chapter 4 revision or Dialogue scene test. It helps identify the analysis attempt; it does not rename the manuscript chapter or change scene content.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Fields/Upload.md

@@ -0,0 +1,18 @@
+---
+title: Chapter Text Upload
+category: Story Intelligence Admin
+tags: story intelligence, admin, fields, upload
+contextKey: storyIntelligence.admin.fields.upload
+micro: Upload a plain-text chapter instead of pasting it.
+quickTitle: Chapter Text Upload
+quickSummary: Upload a plain-text chapter instead of pasting it.
+screenshot:
+---
+
+# Chapter Text Upload
+
+The full chapter test accepts .txt files up to 2 MB. A non-empty upload takes precedence over the chapter text box. Check the loaded filename and source counts before queueing so you analyse the intended version.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/FullChapterTest.md

@@ -0,0 +1,31 @@
+---
+title: Full Chapter Analysis Test
+category: Story Intelligence Admin
+tags: story intelligence, admin, fullChapterTest
+contextKey: storyIntelligence.admin.fullChapterTest
+micro: Check a large chapter and queue a saved background analysis run.
+quickTitle: Full Chapter Analysis Test
+quickSummary: Check a large chapter and queue a saved background analysis run.
+screenshot:
+---
+
+# Full Chapter Analysis Test
+
+Paste chapter text or upload a plain-text file, choose models, then analyse pre-flight. Inspect size estimates and warnings before queueing. A queued run saves analysis results for monitoring; it does not itself commit them as story records. Open the monitor to follow the run.
+
+# Understanding the Fields
+
+| Field | Suggested use |
+| --- | --- |
+| [Analysis Source Label](/Help/Article/storyIntelligence.admin.fields.sourceLabel) | Give this test a recognisable label for later comparison. |
+| [Analysis Project Context](/Help/Article/storyIntelligence.admin.fields.project) | Use the project that owns the manuscript being tested. |
+| [Analysis Book Context](/Help/Article/storyIntelligence.admin.fields.book) | Use the book that contains the chapter under analysis. |
+| [Analysis Chapter Context](/Help/Article/storyIntelligence.admin.fields.chapter) | Use the saved chapter identity for the source text. |
+| [Chapter Structure Test Model](/Help/Article/storyIntelligence.admin.fields.chapterModel) | Choose the model used to detect chapter structure in this test. |
+| [Scene Intelligence Test Model](/Help/Article/storyIntelligence.admin.fields.sceneModel) | Choose the model used to analyse the detected scenes in this test. |
+| [Chapter Text Upload](/Help/Article/storyIntelligence.admin.fields.upload) | Upload a plain-text chapter instead of pasting it. |
+| [Chapter Test Source Text](/Help/Article/storyIntelligence.admin.fields.chapterText) | Supply complete chapter prose with its paragraph and scene breaks. |
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/IllustrationQueue.md

@@ -0,0 +1,18 @@
+---
+title: Illustration Generation Queue
+category: Story Intelligence Admin
+tags: story intelligence, admin, illustrationQueue
+contextKey: storyIntelligence.admin.illustrationQueue
+micro: Follow library items from planning through generation and review.
+quickTitle: Illustration Generation Queue
+quickSummary: Follow library items from planning through generation and review.
+screenshot:
+---
+
+# Illustration Generation Queue
+
+Generate Starter Library prepares the starter set. Queue starts generation for an eligible item; Requeue All Failed retries failed work. Inspect generated images before approving them. Regeneration starts another generation attempt rather than editing your manuscript.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/IllustrationReview.md

@@ -0,0 +1,27 @@
+---
+title: Reviewing a Library Illustration
+category: Story Intelligence Admin
+tags: story intelligence, admin, illustrationReview
+contextKey: storyIntelligence.admin.illustrationReview
+micro: Compare the image with its brief before deciding whether to use it.
+quickTitle: Reviewing a Library Illustration
+quickSummary: Compare the image with its brief before deciding whether to use it.
+screenshot:
+---
+
+# Reviewing a Library Illustration
+
+Approve an image that fits its intended library role. Reject an unsuitable result, regenerate when another attempt is warranted, or disable an item that should no longer be available. Record specific review observations in Admin notes.
+
+# Understanding the Fields
+
+| Field | Suggested use |
+| --- | --- |
+| [Illustration Generation Prompt](/Help/Article/storyIntelligence.admin.fields.illustrationPrompt) | Read the instructions used to generate this library image. |
+| [Illustration Specification](/Help/Article/storyIntelligence.admin.fields.illustrationSpecification) | Inspect the intended content and constraints for the library item. |
+| [Illustration Metadata](/Help/Article/storyIntelligence.admin.fields.illustrationMetadata) | Inspect the saved descriptive details attached to the library item. |
+| [Illustration Admin Notes](/Help/Article/storyIntelligence.admin.fields.illustrationNotes) | Record review observations for this library item. |
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Illustrations.md

@@ -0,0 +1,26 @@
+---
+title: Story Intelligence Illustration Library
+category: Story Intelligence Admin
+tags: story intelligence, admin, illustrations
+contextKey: storyIntelligence.admin.illustrations
+micro: Review reusable generated illustrations and their generation status.
+quickTitle: Story Intelligence Illustration Library
+quickSummary: Review reusable generated illustrations and their generation status.
+screenshot:
+---
+
+# Story Intelligence Illustration Library
+
+Use category, status and search to find library items. Inspect each image and its supporting specification before approving it. Queue and regeneration actions start generation work; approval, rejection and disabling manage library availability. This library is an admin tool and is separate from approving manuscript facts.
+
+# Understanding the Fields
+
+| Field | Suggested use |
+| --- | --- |
+| [Illustration Category Filter](/Help/Article/storyIntelligence.admin.fields.illustrationCategory) | Limit the library to the kind of illustration you want to inspect. |
+| [Illustration Status Filter](/Help/Article/storyIntelligence.admin.fields.illustrationStatus) | Find items at a particular generation or review stage. |
+| [Illustration Library Search](/Help/Article/storyIntelligence.admin.fields.illustrationSearch) | Find library items matching your search text. |
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/ImportPreview.md

@@ -0,0 +1,18 @@
+---
+title: Admin Story Intelligence Import Preview
+category: Story Intelligence Admin
+tags: story intelligence, admin, importPreview
+contextKey: storyIntelligence.admin.importPreview
+micro: Inspect proposed scene records and metrics before opening confirmation.
+quickTitle: Admin Story Intelligence Import Preview
+quickSummary: Inspect proposed scene records and metrics before opening confirmation.
+screenshot:
+---
+
+# Admin Story Intelligence Import Preview
+
+Review the target chapter, scene titles and counts, metrics and any blockers. Previewing does not commit story data. Use the separate confirmation step only when the target and results are correct.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Metadata.md

@@ -0,0 +1,18 @@
+---
+title: Analysis Run Metadata
+category: Story Intelligence Admin
+tags: story intelligence, admin, metadata
+contextKey: storyIntelligence.admin.metadata
+micro: Identify this attempt and inspect status, timing and errors.
+quickTitle: Analysis Run Metadata
+quickSummary: Identify this attempt and inspect status, timing and errors.
+screenshot:
+---
+
+# Analysis Run Metadata
+
+Use source identity, model and prompt versions to distinguish runs of the same chapter. Completion, cancellation and failure messages describe processing; they do not confirm an import. Check the import status separately before trying to create story records.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Preflight.md

@@ -0,0 +1,18 @@
+---
+title: Chapter Analysis Pre-flight
+category: Story Intelligence Admin
+tags: story intelligence, admin, preflight
+contextKey: storyIntelligence.admin.preflight
+micro: Review source size, selected models and estimates before queueing.
+quickTitle: Chapter Analysis Pre-flight
+quickSummary: Review source size, selected models and estimates before queueing.
+screenshot:
+---
+
+# Chapter Analysis Pre-flight
+
+Check word, paragraph and token counts to confirm the intended source was loaded. Estimates are not final usage or cost. Read warnings before queueing and repeat pre-flight after changing the source or model choices.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Prompts.md

@@ -0,0 +1,18 @@
+---
+title: Analysis Prompt Availability
+category: Story Intelligence Admin
+tags: story intelligence, admin, prompts
+contextKey: storyIntelligence.admin.prompts
+micro: Check that the prompt repository and substitutions are available.
+quickTitle: Analysis Prompt Availability
+quickSummary: Check that the prompt repository and substitutions are available.
+screenshot:
+---
+
+# Analysis Prompt Availability
+
+The repository, prompt version and substitution indicators help diagnose missing prompts or incorrect setup. Use the version when comparing runs. These indicators do not assess whether every extracted story detail is correct.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Reset.md

@@ -0,0 +1,18 @@
+---
+title: Development Data Reset
+category: Story Intelligence Admin
+tags: story intelligence, admin, reset
+contextKey: storyIntelligence.admin.reset
+micro: This reset deletes your projects, books and Story Intelligence data.
+quickTitle: Development Data Reset
+quickSummary: This reset deletes your projects, books and Story Intelligence data.
+screenshot:
+---
+
+# Development Data Reset
+
+Use only when intentionally clearing your development data. It deletes your projects, books, imports, runs and story memory. Generated image library records and files are preserved. This is not a way to retry a failed scene or cancel an active analysis.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/RunDetails.md

@@ -0,0 +1,18 @@
+---
+title: Inspecting a Story Intelligence Run
+category: Story Intelligence Admin
+tags: story intelligence, admin, runDetails
+contextKey: storyIntelligence.admin.runDetails
+micro: Inspect one analysis attempt, its errors, results and import preview.
+quickTitle: Inspecting a Story Intelligence Run
+quickSummary: Inspect one analysis attempt, its errors, results and import preview.
+screenshot:
+---
+
+# Inspecting a Story Intelligence Run
+
+Start with status and error messages, then inspect chapter and scene validation. Parsed output and raw responses support troubleshooting. A successful analysis result is not automatically an imported scene. Where offered, review the import preview before opening confirmation. Cancel run requests a stop; rerunning the same source starts another attempt.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Runs.md

@@ -0,0 +1,18 @@
+---
+title: Saved Story Intelligence Runs
+category: Story Intelligence Admin
+tags: story intelligence, admin, runs
+contextKey: storyIntelligence.admin.runs
+micro: Find saved runs and open their status, results and import history.
+quickTitle: Saved Story Intelligence Runs
+quickSummary: Find saved runs and open their status, results and import history.
+screenshot:
+---
+
+# Saved Story Intelligence Runs
+
+Use the run list to identify the correct source and analysis attempt. Open a run to inspect errors, model choices and chapter or scene results. A completed run means analysis has finished; consult its import status to see whether results were committed to story records.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/SceneResults.md

@@ -0,0 +1,18 @@
+---
+title: Scene Analysis Results
+category: Story Intelligence Admin
+tags: story intelligence, admin, sceneResults
+contextKey: storyIntelligence.admin.sceneResults
+micro: Check each detected scene and its extraction or validation status.
+quickTitle: Scene Analysis Results
+quickSummary: Check each detected scene and its extraction or validation status.
+screenshot:
+---
+
+# Scene Analysis Results
+
+Compare the proposed scenes with the source order and boundaries. Inspect failed or incomplete scenes individually rather than assuming a chapter-level success means every result is usable.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/SceneTest.md

@@ -0,0 +1,31 @@
+---
+title: Story Intelligence Scene Dry Run
+category: Story Intelligence Admin
+tags: story intelligence, admin, sceneTest
+contextKey: storyIntelligence.admin.sceneTest
+micro: Test analysis of one supplied scene before saving any result.
+quickTitle: Story Intelligence Scene Dry Run
+quickSummary: Test analysis of one supplied scene before saving any result.
+screenshot:
+---
+
+# Story Intelligence Scene Dry Run
+
+Enter a representative scene and its context, then run the test to inspect the response and validation. This makes a live analysis request. Running the dry run does not save story data; any offered save or queue action is a separate step.
+
+# Understanding the Fields
+
+| Field | Suggested use |
+| --- | --- |
+| [Analysis Project Context](/Help/Article/storyIntelligence.admin.fields.project) | Use the project that owns the manuscript being tested. |
+| [Analysis Book Context](/Help/Article/storyIntelligence.admin.fields.book) | Use the book that contains the chapter under analysis. |
+| [Analysis Chapter Context](/Help/Article/storyIntelligence.admin.fields.chapter) | Use the saved chapter identity for the source text. |
+| [Analysis Scene Context](/Help/Article/storyIntelligence.admin.fields.scene) | Use the saved scene identity when testing an existing scene. |
+| [Analysis Chapter Number](/Help/Article/storyIntelligence.admin.fields.chapterNumber) | Give the chapter position used to describe the test source. |
+| [Analysis Scene Number](/Help/Article/storyIntelligence.admin.fields.sceneNumber) | Give the scene position within the chapter. |
+| [Analysis Source Label](/Help/Article/storyIntelligence.admin.fields.sourceLabel) | Give this test a recognisable label for later comparison. |
+| [Scene Test Source Text](/Help/Article/storyIntelligence.admin.fields.sceneText) | Supply the actual scene prose to analyse. |
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/Admin/Source.md

@@ -0,0 +1,18 @@
+---
+title: Selected Chapter Source
+category: Story Intelligence Admin
+tags: story intelligence, admin, source
+contextKey: storyIntelligence.admin.source
+micro: Confirm the saved chapter and availability of its manuscript text.
+quickTitle: Selected Chapter Source
+quickSummary: Confirm the saved chapter and availability of its manuscript text.
+screenshot:
+---
+
+# Selected Chapter Source
+
+Check the project, book and chapter labels against the source you intend to analyse. Word and character counts help detect an empty or unexpected source. Queueing is available only when stored source text is present.
+
+# Related Guides
+
+- [Story Intelligence diagnostics](/Help/Article/storyIntelligence.admin.diagnostics)

PlotLine/Help/Articles/StoryIntelligence/AnalysisStarted.md

@@ -0,0 +1,18 @@
+---
+title: Analysis Already Started
+category: Story Intelligence
+tags: story intelligence, analysisStarted
+contextKey: storyIntelligence.analysisStarted
+micro: Return to your existing analysis before considering another manuscript scan.
+quickTitle: Analysis Already Started
+quickSummary: Return to your existing analysis before considering another manuscript scan.
+screenshot:
+---
+
+# Analysis Already Started
+
+The existing analysis belongs to this imported manuscript. Return to the book to follow its progress or open review when ready. Scan manuscript again returns to the scanning workflow; it is not the same as resuming background analysis.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Assets.md

@@ -0,0 +1,24 @@
+---
+title: Reviewing Story Intelligence Assets
+category: Story Intelligence
+tags: story intelligence, assets
+contextKey: storyIntelligence.assets
+micro: Keep meaningful objects and possessions without duplicating the same item.
+quickTitle: Reviewing Story Intelligence Assets
+quickSummary: Keep meaningful objects and possessions without duplicating the same item.
+screenshot:
+---
+
+# Reviewing Story Intelligence Assets
+
+Use the scene context to decide whether an object deserves a story record. A recurring key, a distinctive vehicle or an inherited ring may matter; a passing reference to an ordinary object may not.
+
+Create a new asset for a distinct item or link another mention of the same object. Existing matched cards are already linked. Previous and Next on this form save the displayed decisions; leaving by another link does not submit the form.
+
+# Understanding the Fields
+
+See [review decisions and fields](/Help/Article/storyIntelligence.assets.decisions) for the choices on each card.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Assets/Decisions.md

@@ -0,0 +1,25 @@
+---
+title: Asset Review Decisions
+category: Story Intelligence
+tags: story intelligence, assets, decisions
+contextKey: storyIntelligence.assets.decisions
+micro: Create a distinct story object or link another mention of the same item.
+quickTitle: Asset Review Decisions
+quickSummary: Create a distinct story object or link another mention of the same item.
+screenshot:
+---
+
+# Asset Review Decisions
+
+Create new for a separate meaningful object. Same asset as links it to an existing or proposed item. Ignore skips material you do not need to track. Two objects of the same kind are not necessarily the same asset.
+
+# Understanding the Fields
+
+| Field | Suggested use |
+| --- | --- |
+| [Name to import](/Help/Article/storyIntelligence.review.importName) | Choose the main record name for a newly created character, place or object. |
+| [Same Asset As](/Help/Article/storyIntelligence.assets.sameAsset) | Combine mentions only when they identify the same individual object. |
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Assets/SameAsset.md

@@ -0,0 +1,18 @@
+---
+title: Same Asset As
+category: Story Intelligence
+tags: story intelligence, assets, sameAsset
+contextKey: storyIntelligence.assets.sameAsset
+micro: Combine mentions only when they identify the same individual object.
+quickTitle: Same Asset As
+quickSummary: Combine mentions only when they identify the same individual object.
+screenshot:
+---
+
+# Same Asset As
+
+Choose an existing asset or another proposed item from the list. The brass key and the cellar key might be the same object if the evidence supports it. Two similar keys carried by different characters should remain separate.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/AuthorPlotContext.md

@@ -0,0 +1,20 @@
+---
+title: Author Plot Context
+category: Story Intelligence
+tags: story intelligence, authorPlotContext
+contextKey: storyIntelligence.authorPlotContext
+micro: Describe the major stories you want PlotDirector to look for.
+quickTitle: Author Plot Context
+quickSummary: Describe the major stories you want PlotDirector to look for.
+screenshot:
+---
+
+# Author Plot Context
+
+Give each sustained conflict, mystery or character arc its own box. One or two sentences are enough; include hidden motives or the intended resolution if they help explain the arc. These are author guidance, not prose for readers.
+
+PlotDirector still looks for additional plot lines in the manuscript. Blank boxes can be left unused. Add another plot line when you need more space for a different arc, then choose Analyse my book.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/AuthorPlotContext/Seed.md

@@ -0,0 +1,18 @@
+---
+title: Plot Line Guidance
+category: Story Intelligence
+tags: story intelligence, authorPlotContext, seed
+contextKey: storyIntelligence.authorPlotContext.seed
+micro: Describe one sustained story arc per box.
+quickTitle: Plot Line Guidance
+quickSummary: Describe one sustained story arc per box.
+screenshot:
+---
+
+# Plot Line Guidance
+
+State the central conflict or question and how it develops across the book. For example: A missing letter draws a historian into a family dispute, and each discovery changes whom she trusts. Include intended secrets where useful. Each box allows up to 4,000 characters; a sentence or two usually works best. Leave unused boxes blank.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Characters.md

@@ -0,0 +1,24 @@
+---
+title: Reviewing Story Intelligence Characters
+category: Story Intelligence
+tags: story intelligence, characters
+contextKey: storyIntelligence.characters
+micro: Confirm which manuscript names refer to distinct characters.
+quickTitle: Reviewing Story Intelligence Characters
+quickSummary: Confirm which manuscript names refer to distinct characters.
+screenshot:
+---
+
+# Reviewing Story Intelligence Characters
+
+Read the scene context and suggested existing match before deciding. Two names may refer to the same person, but similar names alone are not enough to link them. Resolving identities first makes the later relationship and knowledge reviews more reliable.
+
+Create a character for a distinct person, use Same character as for an existing identity, or ignore unsupported suggestions. Save the displayed decisions before navigating away. Bulk choices affect the displayed cards and should be checked before saving.
+
+# Understanding the Fields
+
+See [review decisions and fields](/Help/Article/storyIntelligence.characters.decisions) for the choices on each card.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Characters/Decisions.md

@@ -0,0 +1,25 @@
+---
+title: Character Review Decisions
+category: Story Intelligence
+tags: story intelligence, characters, decisions
+contextKey: storyIntelligence.characters.decisions
+micro: Create a distinct character, link an existing identity or ignore this suggestion.
+quickTitle: Character Review Decisions
+quickSummary: Create a distinct character, link an existing identity or ignore this suggestion.
+screenshot:
+---
+
+# Character Review Decisions
+
+Create new keeps a distinct person. Same character as attaches the mention to an existing identity. Ignore skips the suggestion. An existing match is evidence to inspect, not proof. Save all displayed choices before navigating away.
+
+# Understanding the Fields
+
+| Field | Suggested use |
+| --- | --- |
+| [Name to import](/Help/Article/storyIntelligence.review.importName) | Choose the main record name for a newly created character, place or object. |
+| [Same Character As](/Help/Article/storyIntelligence.characters.sameCharacter) | Link this mention to the existing person it actually identifies. |
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Characters/SameCharacter.md

@@ -0,0 +1,18 @@
+---
+title: Same Character As
+category: Story Intelligence
+tags: story intelligence, characters, sameCharacter
+contextKey: storyIntelligence.characters.sameCharacter
+micro: Link this mention to the existing person it actually identifies.
+quickTitle: Same Character As
+quickSummary: Link this mention to the existing person it actually identifies.
+screenshot:
+---
+
+# Same Character As
+
+Choose the same person under another name, title or alias. Check context and identity evidence, especially for shared surnames or role labels such as the captain. Do not link two different people simply because they have similar roles.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Complete.md

@@ -0,0 +1,20 @@
+---
+title: Story Intelligence Completion
+category: Story Intelligence
+tags: story intelligence, complete
+contextKey: storyIntelligence.complete
+micro: Open the story records created or linked through your review.
+quickTitle: Story Intelligence Completion
+quickSummary: Open the story records created or linked through your review.
+screenshot:
+---
+
+# Story Intelligence Completion
+
+Use the totals to see what this workflow prepared, created or linked. The checklist summarises the workflow; it is not a guarantee that every suggested detail was accepted or that continuity is error-free.
+
+Open scenes to check the results in context, open the book for further planning, or return to the dashboard. You can continue refining the story records as you revise.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Complete/Records.md

@@ -0,0 +1,18 @@
+---
+title: Story Database Build Summary
+category: Story Intelligence
+tags: story intelligence, complete, records
+contextKey: storyIntelligence.complete.records
+micro: Check the records prepared through manuscript analysis and review.
+quickTitle: Story Database Build Summary
+quickSummary: Check the records prepared through manuscript analysis and review.
+screenshot:
+---
+
+# Story Database Build Summary
+
+The checklist summarises the kinds of story records involved. Use the displayed counts and links to inspect what was created or linked. An ignored proposal will not become an accepted fact just because the completion page is shown.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Context.md

@@ -0,0 +1,20 @@
+---
+title: Story and Portrait Context
+category: Story Intelligence
+tags: story intelligence, context
+contextKey: storyIntelligence.context
+micro: Set broad defaults for unresolved story and portrait details.
+quickTitle: Story and Portrait Context
+quickSummary: Set broad defaults for unresolved story and portrait details.
+screenshot:
+---
+
+# Story and Portrait Context
+
+Choose defaults that fit your manuscript. Explicit manuscript evidence takes priority over these choices: an age or appearance stated in the story should not be replaced by a cast baseline.
+
+Use No baseline where you do not want to supply a broad age, era or location default. Saving this form starts analysis.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Context/Age.md

@@ -0,0 +1,18 @@
+---
+title: Primary Character Age Group
+category: Story Intelligence
+tags: story intelligence, context, age
+contextKey: storyIntelligence.context.age
+micro: Supply an age baseline only where the manuscript leaves age unresolved.
+quickTitle: Primary Character Age Group
+quickSummary: Supply an age baseline only where the manuscript leaves age unresolved.
+screenshot:
+---
+
+# Primary Character Age Group
+
+Choose the broad age group of the main cast, not the reading audience. An adult supporting character should still remain an adult in a story with teenage leads. Choose No baseline if the cast spans ages or you want the manuscript alone to guide this.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Context/Appearance.md

@@ -0,0 +1,18 @@
+---
+title: Appearance Baseline
+category: Story Intelligence
+tags: story intelligence, context, appearance
+contextKey: storyIntelligence.context.appearance
+micro: Guide unresolved portrait appearances without overriding the manuscript.
+quickTitle: Appearance Baseline
+quickSummary: Guide unresolved portrait appearances without overriding the manuscript.
+screenshot:
+---
+
+# Appearance Baseline
+
+Choose the cast baseline you intend where appearance is unspecified. Balanced diverse cast supplies a broad mix; the light, medium and dark options supply a predominant baseline. Explicit evidence only avoids supplying a broad appearance preference. Custom mix is a listed choice, but this screen has no controls for entering proportions. This choice does not rewrite established character descriptions.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Context/Choices.md

@@ -0,0 +1,27 @@
+---
+title: Choosing Story and Portrait Defaults
+category: Story Intelligence
+tags: story intelligence, context, choices
+contextKey: storyIntelligence.context.choices
+micro: Use broad context only where the manuscript leaves details unresolved.
+quickTitle: Choosing Story and Portrait Defaults
+quickSummary: Use broad context only where the manuscript leaves details unresolved.
+screenshot:
+---
+
+# Choosing Story and Portrait Defaults
+
+Use broad context only where the manuscript leaves details unresolved.
+
+# Understanding the Fields
+
+| Field | Suggested use |
+| --- | --- |
+| Appearance Baseline | Guide unresolved portrait appearances without overriding the manuscript. |
+| Primary Character Age Group | Supply an age baseline only where the manuscript leaves age unresolved. |
+| Story Era Baseline | Guide unresolved period details using the broad era of your story. |
+| Story Location Baseline | Supply broad setting context rather than an individual scene location. |
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Context/Era.md

@@ -0,0 +1,18 @@
+---
+title: Story Era Baseline
+category: Story Intelligence
+tags: story intelligence, context, era
+contextKey: storyIntelligence.context.era
+micro: Guide unresolved period details using the broad era of your story.
+quickTitle: Story Era Baseline
+quickSummary: Guide unresolved period details using the broad era of your story.
+screenshot:
+---
+
+# Story Era Baseline
+
+Choose the setting period rather than the year you wrote the book. For a story spanning periods, use No baseline when one choice would mislead. Explicit dates and period evidence in the manuscript take priority.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Context/Location.md

@@ -0,0 +1,18 @@
+---
+title: Story Location Baseline
+category: Story Intelligence
+tags: story intelligence, context, location
+contextKey: storyIntelligence.context.location
+micro: Supply broad setting context rather than an individual scene location.
+quickTitle: Story Location Baseline
+quickSummary: Supply broad setting context rather than an individual scene location.
+screenshot:
+---
+
+# Story Location Baseline
+
+Choose the geographical or setting baseline that fits the story, or No baseline if none fits. This is not the place hierarchy: individual houses, towns and rooms are reviewed under Locations.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Knowledge.md

@@ -0,0 +1,24 @@
+---
+title: Reviewing Story Intelligence Knowledge
+category: Story Intelligence
+tags: story intelligence, knowledge
+contextKey: storyIntelligence.knowledge
+micro: Track what a character knows, believes or suspects at a scene.
+quickTitle: Reviewing Story Intelligence Knowledge
+quickSummary: Track what a character knows, believes or suspects at a scene.
+screenshot:
+---
+
+# Reviewing Story Intelligence Knowledge
+
+Read who holds the knowledge and the supporting evidence. A character can believe something false, suspect a truth without proof, or discover a fact later than the reader. Choose a state that reflects the character at this point in the story.
+
+Create a distinct record, link the proposed existing match, merge duplicate suggestions, or ignore unsupported material. Previous and Next submit the displayed decisions. Check bulk selections before saving, especially where similar facts belong to different characters.
+
+# Understanding the Fields
+
+See [review decisions and fields](/Help/Article/storyIntelligence.knowledge.decisions) for the choices on each card.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Knowledge/Decisions.md

@@ -0,0 +1,25 @@
+---
+title: Knowledge Review Decisions
+category: Story Intelligence
+tags: story intelligence, knowledge, decisions
+contextKey: storyIntelligence.knowledge.decisions
+micro: Create, link, merge or ignore a character knowledge proposal.
+quickTitle: Knowledge Review Decisions
+quickSummary: Create, link, merge or ignore a character knowledge proposal.
+screenshot:
+---
+
+# Knowledge Review Decisions
+
+Create new keeps distinct knowledge. Link existing uses the suggested saved match when available. Merge with another knowledge item combines duplicate proposals using the selected target. Ignore skips unsupported material. Do not merge different facts or different character perspectives just because their wording is similar.
+
+# Understanding the Fields
+
+| Field | Suggested use |
+| --- | --- |
+| [Character Knowledge State](/Help/Article/storyIntelligence.knowledge.state) | Choose how the character holds this information in this scene. |
+| [Knowledge Merge Target](/Help/Article/storyIntelligence.knowledge.mergeTarget) | Choose another proposal for the same knowledge record. |
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Knowledge/MergeTarget.md

@@ -0,0 +1,18 @@
+---
+title: Knowledge Merge Target
+category: Story Intelligence
+tags: story intelligence, knowledge, mergeTarget
+contextKey: storyIntelligence.knowledge.mergeTarget
+micro: Choose another proposal for the same knowledge record.
+quickTitle: Knowledge Merge Target
+quickSummary: Choose another proposal for the same knowledge record.
+screenshot:
+---
+
+# Knowledge Merge Target
+
+Use this after choosing Merge with another knowledge item. Select a retained target rather than an ignored item or the item itself. Check both the information and the character context; similar wording about different secrets is not a duplicate.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Knowledge/State.md

@@ -0,0 +1,18 @@
+---
+title: Character Knowledge State
+category: Story Intelligence
+tags: story intelligence, knowledge, state
+contextKey: storyIntelligence.knowledge.state
+micro: Choose how the character holds this information in this scene.
+quickTitle: Character Knowledge State
+quickSummary: Choose how the character holds this information in this scene.
+screenshot:
+---
+
+# Character Knowledge State
+
+Distinguish knowing from believing or suspecting using the available states. A convincing lie may be a belief rather than story truth. Use the evidence for this character at this time; do not assume they know everything the reader or author knows.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Locations.md

@@ -0,0 +1,24 @@
+---
+title: Reviewing Story Intelligence Locations
+category: Story Intelligence
+tags: story intelligence, locations
+contextKey: storyIntelligence.locations
+micro: Resolve settings and organise places within larger locations.
+quickTitle: Reviewing Story Intelligence Locations
+quickSummary: Resolve settings and organise places within larger locations.
+screenshot:
+---
+
+# Reviewing Story Intelligence Locations
+
+Start with significant settings, then inspect uncertain identities or all detected locations. Parent places may be shown to explain the hierarchy. Confidence measures identification certainty; significance measures story importance.
+
+Use Same location as only for another name for the same place. Use Parent location for containment, such as a kitchen within a house. Existing matches may need only a parent decision. Save before changing filters or following navigation links.
+
+# Understanding the Fields
+
+See [review decisions and fields](/Help/Article/storyIntelligence.locations.decisions) for the choices on each card.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Locations/Decisions.md

@@ -0,0 +1,27 @@
+---
+title: Location Review Decisions
+category: Story Intelligence
+tags: story intelligence, locations, decisions
+contextKey: storyIntelligence.locations.decisions
+micro: Distinguish a new place, an alternative name and a place within another place.
+quickTitle: Location Review Decisions
+quickSummary: Distinguish a new place, an alternative name and a place within another place.
+screenshot:
+---
+
+# Location Review Decisions
+
+Create new for a distinct setting. Same location as combines references to one physical place. Ignore skips an unsupported suggestion. Parent location organises containment independently of identity. Already matched locations keep their existing identity; review the parent if needed.
+
+# Understanding the Fields
+
+| Field | Suggested use |
+| --- | --- |
+| [Name to import](/Help/Article/storyIntelligence.review.importName) | Choose the main record name for a newly created character, place or object. |
+| [Parent Location](/Help/Article/storyIntelligence.locations.parent) | Choose the larger place that physically contains this location. |
+| [Same Location As](/Help/Article/storyIntelligence.locations.sameLocation) | Link alternative names for the same physical place. |
+| [Location Review Filters](/Help/Article/storyIntelligence.locations.filters) | Switch between story-important settings, every detected place and uncertain identities. |
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Locations/Filters.md

@@ -0,0 +1,18 @@
+---
+title: Location Review Filters
+category: Story Intelligence
+tags: story intelligence, locations, filters
+contextKey: storyIntelligence.locations.filters
+micro: Switch between story-important settings, every detected place and uncertain identities.
+quickTitle: Location Review Filters
+quickSummary: Switch between story-important settings, every detected place and uncertain identities.
+screenshot:
+---
+
+# Location Review Filters
+
+Significant locations prioritises settings important to the story. All detected locations includes minor settings. Need review focuses on unresolved identities. Parent locations can appear for context. These links change the view, so save any pending edits before switching.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Locations/Parent.md

@@ -0,0 +1,18 @@
+---
+title: Parent Location
+category: Story Intelligence
+tags: story intelligence, locations, parent
+contextKey: storyIntelligence.locations.parent
+micro: Choose the larger place that physically contains this location.
+quickTitle: Parent Location
+quickSummary: Choose the larger place that physically contains this location.
+screenshot:
+---
+
+# Parent Location
+
+For a kitchen, choose its house; for the house, choose its town if appropriate. You can use an existing place or a proposed place available in the list. Not determined leaves the parent unspecified. A parent is not an alias, and a place cannot contain itself or create a circular hierarchy.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Locations/SameLocation.md

@@ -0,0 +1,18 @@
+---
+title: Same Location As
+category: Story Intelligence
+tags: story intelligence, locations, sameLocation
+contextKey: storyIntelligence.locations.sameLocation
+micro: Link alternative names for the same physical place.
+quickTitle: Same Location As
+quickSummary: Link alternative names for the same physical place.
+screenshot:
+---
+
+# Same Location As
+
+Choose an existing location or another proposed location when both mentions mean the same setting. The old mill and Harrow Mill may be one place; the mill office is a separate child location. Do not merge a room into its building just because they occur together.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Metrics.md

@@ -0,0 +1,18 @@
+---
+title: Story Intelligence Scene Metrics
+category: Story Intelligence
+tags: story intelligence, metrics
+contextKey: storyIntelligence.metrics
+micro: Inspect automatically applied scene metrics on the Timeline.
+quickTitle: Story Intelligence Scene Metrics
+quickSummary: Inspect automatically applied scene metrics on the Timeline.
+screenshot:
+---
+
+# Story Intelligence Scene Metrics
+
+Metrics describe analysed scene qualities such as pacing or tension where those metrics are configured. View them on the Timeline and check unusual values against the actual scene. They support editorial judgement and do not require the same accept-or-ignore review as relationship proposals.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Narrative.md

@@ -0,0 +1,24 @@
+---
+title: Reviewing Plot Lines and Threads
+category: Story Intelligence
+tags: story intelligence, narrative
+contextKey: storyIntelligence.narrative
+micro: Review sustained arcs, their supporting threads and scene events.
+quickTitle: Reviewing Plot Lines and Threads
+quickSummary: Review sustained arcs, their supporting threads and scene events.
+screenshot:
+---
+
+# Reviewing Plot Lines and Threads
+
+A Plot Line is a sustained story arc; a Thread tracks a more specific strand within it. Check titles, descriptions and parent choices against the manuscript and your intended story. Author-provided context is guidance; it is not proof that every proposed event occurs.
+
+Accept distinct arcs, merge duplicate accounts of the same arc, and reject unsupported suggestions. Review the proposed timeline events as well as the overall arc. Save the displayed decisions before leaving; if more candidates remain, continue with the next batch.
+
+# Understanding the Fields
+
+See [review decisions and fields](/Help/Article/storyIntelligence.narrative.decisions) for the choices on each card.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Narrative/CandidateMerge.md

@@ -0,0 +1,18 @@
+---
+title: Candidate for Merge
+category: Story Intelligence
+tags: story intelligence, narrative, candidateMerge
+contextKey: storyIntelligence.narrative.candidateMerge
+micro: Choose another proposal describing the same arc or thread.
+quickTitle: Candidate for Merge
+quickSummary: Choose another proposal describing the same arc or thread.
+screenshot:
+---
+
+# Candidate for Merge
+
+Use with Merge with candidate. The list offers other candidates of the same kind. Keep the target accepted or linked to a retained record, and avoid circular merges. Related but distinct threads should remain separate under a shared parent.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Narrative/Decisions.md

@@ -0,0 +1,31 @@
+---
+title: Plot Line and Thread Decisions
+category: Story Intelligence
+tags: story intelligence, narrative, decisions
+contextKey: storyIntelligence.narrative.decisions
+micro: Accept a distinct arc, merge a duplicate or reject an unsupported proposal.
+quickTitle: Plot Line and Thread Decisions
+quickSummary: Accept a distinct arc, merge a duplicate or reject an unsupported proposal.
+screenshot:
+---
+
+# Plot Line and Thread Decisions
+
+Accept new keeps a distinct Plot Line or Thread. Merge with existing uses the saved target; Merge with candidate combines duplicate proposals of the same kind. Reject skips the proposal. Check parent assignments and included events as well as the overall title and description.
+
+# Understanding the Fields
+
+| Field | Suggested use |
+| --- | --- |
+| [Existing Related Plot Line](/Help/Article/storyIntelligence.narrative.relatedPlotLine) | Attach this Thread to an already saved Plot Line. |
+| [Proposed Parent Plot Line](/Help/Article/storyIntelligence.narrative.parent) | Attach this Thread to a Plot Line being reviewed. |
+| [Existing Plot Line for Merge](/Help/Article/storyIntelligence.narrative.existingMerge) | Choose the saved Plot Line that already represents this proposed arc. |
+| [Candidate for Merge](/Help/Article/storyIntelligence.narrative.candidateMerge) | Choose another proposal describing the same arc or thread. |
+| [Include a Proposed Timeline Event](/Help/Article/storyIntelligence.narrative.eventInclude) | Keep only scene events that genuinely advance or establish this arc. |
+| [Narrative Timeline Event Type](/Help/Article/storyIntelligence.narrative.eventType) | Describe the role this scene plays in the arc. |
+| [Narrative Event Title](/Help/Article/storyIntelligence.narrative.eventTitle) | Give the scene development a short, specific timeline label. |
+| [Narrative Event Description](/Help/Article/storyIntelligence.narrative.eventDescription) | Explain how this scene changes the arc or thread. |
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Narrative/EventDescription.md

@@ -0,0 +1,18 @@
+---
+title: Narrative Event Description
+category: Story Intelligence
+tags: story intelligence, narrative, eventDescription
+contextKey: storyIntelligence.narrative.eventDescription
+micro: Explain how this scene changes the arc or thread.
+quickTitle: Narrative Event Description
+quickSummary: Explain how this scene changes the arc or thread.
+screenshot:
+---
+
+# Narrative Event Description
+
+Summarise the supported development, clue, complication or payoff. Keep the scene perspective and chronology clear. Do not describe the eventual resolution as if it has already happened.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Narrative/EventInclude.md

@@ -0,0 +1,18 @@
+---
+title: Include a Proposed Timeline Event
+category: Story Intelligence
+tags: story intelligence, narrative, eventInclude
+contextKey: storyIntelligence.narrative.eventInclude
+micro: Keep only scene events that genuinely advance or establish this arc.
+quickTitle: Include a Proposed Timeline Event
+quickSummary: Keep only scene events that genuinely advance or establish this arc.
+screenshot:
+---
+
+# Include a Proposed Timeline Event
+
+Leave checked to include this scene event when saving the accepted or merged candidate. Uncheck unsupported or redundant events. This removes the proposal from this acceptance, not the manuscript scene.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Narrative/EventTitle.md

@@ -0,0 +1,18 @@
+---
+title: Narrative Event Title
+category: Story Intelligence
+tags: story intelligence, narrative, eventTitle
+contextKey: storyIntelligence.narrative.eventTitle
+micro: Give the scene development a short, specific timeline label.
+quickTitle: Narrative Event Title
+quickSummary: Give the scene development a short, specific timeline label.
+screenshot:
+---
+
+# Narrative Event Title
+
+Name what happens in this scene, such as The witness changes her story, rather than repeating the whole Plot Line title. This labels the proposed timeline event and does not rename the manuscript scene.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Narrative/EventType.md

@@ -0,0 +1,18 @@
+---
+title: Narrative Timeline Event Type
+category: Story Intelligence
+tags: story intelligence, narrative, eventType
+contextKey: storyIntelligence.narrative.eventType
+micro: Describe the role this scene plays in the arc.
+quickTitle: Narrative Timeline Event Type
+quickSummary: Describe the role this scene plays in the arc.
+screenshot:
+---
+
+# Narrative Timeline Event Type
+
+Choose Introduced for a first establishment, Developed for progress, Complicated for an obstacle, Clue Planted for evidence, and Payoff or Resolved for a meaningful outcome. Revealed concerns a disclosure; Mentioned need not imply progress. Retconned is for a later revision of established continuity, not an ordinary new discovery.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Narrative/Events.md

@@ -0,0 +1,27 @@
+---
+title: Proposed Narrative Timeline Events
+category: Story Intelligence
+tags: story intelligence, narrative, events
+contextKey: storyIntelligence.narrative.events
+micro: Review the scene developments that give an arc its chronology.
+quickTitle: Proposed Narrative Timeline Events
+quickSummary: Review the scene developments that give an arc its chronology.
+screenshot:
+---
+
+# Proposed Narrative Timeline Events
+
+Keep events that establish, advance, complicate or resolve the selected arc. Remove unsupported or redundant suggestions before saving.
+
+# Understanding the Fields
+
+| Field | Suggested use |
+| --- | --- |
+| Include a Proposed Timeline Event | Keep only scene events that genuinely advance or establish this arc. |
+| Narrative Timeline Event Type | Describe the role this scene plays in the arc. |
+| Narrative Event Title | Give the scene development a short, specific timeline label. |
+| Narrative Event Description | Explain how this scene changes the arc or thread. |
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Narrative/ExistingMerge.md

@@ -0,0 +1,18 @@
+---
+title: Existing Plot Line for Merge
+category: Story Intelligence
+tags: story intelligence, narrative, existingMerge
+contextKey: storyIntelligence.narrative.existingMerge
+micro: Choose the saved Plot Line that already represents this proposed arc.
+quickTitle: Existing Plot Line for Merge
+quickSummary: Choose the saved Plot Line that already represents this proposed arc.
+screenshot:
+---
+
+# Existing Plot Line for Merge
+
+Use with Merge with existing when the proposal duplicates a saved Plot Line. Compare the central conflict and scope, not just its title. This is a merge target, whereas Existing related Plot Line is the parent for a Thread.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Narrative/Parent.md

@@ -0,0 +1,18 @@
+---
+title: Proposed Parent Plot Line
+category: Story Intelligence
+tags: story intelligence, narrative, parent
+contextKey: storyIntelligence.narrative.parent
+micro: Attach this Thread to a Plot Line being reviewed.
+quickTitle: Proposed Parent Plot Line
+quickSummary: Attach this Thread to a Plot Line being reviewed.
+screenshot:
+---
+
+# Proposed Parent Plot Line
+
+Select the proposed parent arc when no existing Plot Line is the appropriate parent. Make sure that parent is accepted or merged into a retained Plot Line. Avoid conflicting parent choices: an existing related Plot Line takes priority.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Narrative/RelatedPlotLine.md

@@ -0,0 +1,18 @@
+---
+title: Existing Related Plot Line
+category: Story Intelligence
+tags: story intelligence, narrative, relatedPlotLine
+contextKey: storyIntelligence.narrative.relatedPlotLine
+micro: Attach this Thread to an already saved Plot Line.
+quickTitle: Existing Related Plot Line
+quickSummary: Attach this Thread to an already saved Plot Line.
+screenshot:
+---
+
+# Existing Related Plot Line
+
+Choose the sustained arc this strand advances. A search for a witness might belong under the wider murder investigation. Use an existing parent when it already exists; this choice takes precedence over a proposed parent.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Overview.md

@@ -0,0 +1,20 @@
+---
+title: Preparing Story Intelligence
+category: Story Intelligence
+tags: story intelligence, overview
+contextKey: storyIntelligence.overview
+micro: Analyse your imported manuscript to find story information for review.
+quickTitle: Preparing Story Intelligence
+quickSummary: Analyse your imported manuscript to find story information for review.
+screenshot:
+---
+
+# Preparing Story Intelligence
+
+Core import has already created the book structure. Story Intelligence reads the saved scenes and suggests characters, settings, objects, relationships, knowledge and plot developments.
+
+Continue to story and portrait context before starting. You can skip analysis for now and return from your book. If analysis has already started, return to the book to follow progress instead of starting a duplicate analysis.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Pipeline.md

@@ -0,0 +1,18 @@
+---
+title: Story Intelligence Workflow
+category: Story Intelligence
+tags: story intelligence, pipeline
+contextKey: storyIntelligence.pipeline
+micro: Follow the journey from core import through analysis to review.
+quickTitle: Story Intelligence Workflow
+quickSummary: Follow the journey from core import through analysis to review.
+screenshot:
+---
+
+# Story Intelligence Workflow
+
+Core import creates book structure from the manuscript. Analysis reads the saved scenes. Review lets you confirm suggested story records, beginning with character identities. The phase indicator describes the workflow stage rather than a precise measure of processing time.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Progress.md

@@ -0,0 +1,20 @@
+---
+title: Following Manuscript Analysis
+category: Story Intelligence
+tags: story intelligence, progress
+contextKey: storyIntelligence.progress
+micro: Follow the analysis and return later while it continues in the background.
+quickTitle: Following Manuscript Analysis
+quickSummary: Follow the analysis and return later while it continues in the background.
+screenshot:
+---
+
+# Following Manuscript Analysis
+
+Chapters and scenes read show progress through the saved manuscript. Elapsed and estimated remaining times describe analysis, not story time; remaining time is an estimate. Needs review flags analysis failures that may need attention.
+
+Current activity and the live feed show work in progress. Discoveries are suggestions until reviewed. Continue in background leaves analysis running; Cancel analysis requests that active work stop. Open the Review Centre when available.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Progress/Cancel.md

@@ -0,0 +1,18 @@
+---
+title: Cancel or Continue Analysis
+category: Story Intelligence
+tags: story intelligence, progress, cancel
+contextKey: storyIntelligence.progress.cancel
+micro: Continue in background keeps work running; Cancel analysis requests a stop.
+quickTitle: Cancel or Continue Analysis
+quickSummary: Continue in background keeps work running; Cancel analysis requests a stop.
+screenshot:
+---
+
+# Cancel or Continue Analysis
+
+Use Continue in background if you only want to leave this page. Word does not need to stay open for analysis of saved scenes. Cancel analysis requests that active work stop; it is not an undo of core import or of decisions already saved.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Progress/Current.md

@@ -0,0 +1,18 @@
+---
+title: Current Analysis Activity
+category: Story Intelligence
+tags: story intelligence, progress, current
+contextKey: storyIntelligence.progress.current
+micro: See the chapter and scene currently being analysed.
+quickTitle: Current Analysis Activity
+quickSummary: See the chapter and scene currently being analysed.
+screenshot:
+---
+
+# Current Analysis Activity
+
+The current chapter and scene change as background work advances. Waiting means there is no current item to display yet. A chapter title remaining on screen does not by itself show that analysis has failed; consult the progress and error messages.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Progress/Discoveries.md

@@ -0,0 +1,18 @@
+---
+title: Recent Story Discoveries
+category: Story Intelligence
+tags: story intelligence, progress, discoveries
+contextKey: storyIntelligence.progress.discoveries
+micro: Preview possible characters, settings and clues found during analysis.
+quickTitle: Recent Story Discoveries
+quickSummary: Preview possible characters, settings and clues found during analysis.
+screenshot:
+---
+
+# Recent Story Discoveries
+
+Discoveries are provisional signals from the manuscript. Later review may combine aliases, discard incidental objects or correct interpretations. Do not treat their appearance in the feed as confirmation that a new record has been accepted.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Progress/Latest.md

@@ -0,0 +1,18 @@
+---
+title: Latest Scene Summary
+category: Story Intelligence
+tags: story intelligence, progress, latest
+contextKey: storyIntelligence.progress.latest
+micro: Read the latest analysis summary as it becomes available.
+quickTitle: Latest Scene Summary
+quickSummary: Read the latest analysis summary as it becomes available.
+screenshot:
+---
+
+# Latest Scene Summary
+
+This feed summarises recently analysed scene content. Use it to follow which part of the manuscript is being read. It is not replacement prose or an approved story record; check discoveries in the relevant review category.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Relationships.md

@@ -0,0 +1,26 @@
+---
+title: Reviewing Story Intelligence Relationships
+category: Story Intelligence
+tags: story intelligence, relationships
+contextKey: storyIntelligence.relationships
+micro: Record relationship facts and changing states in their scenes.
+quickTitle: Reviewing Story Intelligence Relationships
+quickSummary: Record relationship facts and changing states in their scenes.
+screenshot:
+---
+
+# Reviewing Story Intelligence Relationships
+
+Each card proposes a fact or development in a particular scene. Read the scene and supporting context, then correct the track, state and direction before accepting. The confidence badge describes the suggestion, not the strength of the emotion.
+
+A relationship track is the underlying connection. Its state can change from Friendly to Tense or Reconciled as the story develops. Acceptance reuses a matching relationship where possible and adds this scene event, preserving existing history.
+
+Accept is selected initially. Review every displayed card before saving. Ignore skips this proposal without deleting existing relationship history. Save before using page links or returning to the Review Centre.
+
+# Understanding the Fields
+
+See [review decisions and fields](/Help/Article/storyIntelligence.relationships.decisions) for the choices on each card.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Relationships/Awareness.md

@@ -0,0 +1,18 @@
+---
+title: Awareness of a Relationship State
+category: Story Intelligence
+tags: story intelligence, relationships, awareness
+contextKey: storyIntelligence.relationships.awareness
+micro: Record whether the receiving character knows about the feeling or attitude.
+quickTitle: Awareness of a Relationship State
+quickSummary: Record whether the receiving character knows about the feeling or attitude.
+screenshot:
+---
+
+# Awareness of a Relationship State
+
+Choose Yes when the scene establishes that the receiving character knows. Choose No / not established for a hidden feeling or insufficient evidence. Awareness is not reciprocity and is not reader knowledge. If Reverse A and B is ticked, answer for the new receiving character even though the displayed label keeps the original name.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Relationships/Decisions.md

@@ -0,0 +1,30 @@
+---
+title: Relationship Scene Proposal Decisions
+category: Story Intelligence
+tags: story intelligence, relationships, decisions
+contextKey: storyIntelligence.relationships.decisions
+micro: Accept a supported scene development or ignore the proposal.
+quickTitle: Relationship Scene Proposal Decisions
+quickSummary: Accept a supported scene development or ignore the proposal.
+screenshot:
+---
+
+# Relationship Scene Proposal Decisions
+
+Acceptance adds this scene event and reuses a matching factual or directional relationship where possible. Existing history is preserved. Ignore skips this proposal without deleting previous events. Accept is initially selected; use the scene evidence to check every value before saving.
+
+# Understanding the Fields
+
+| Field | Suggested use |
+| --- | --- |
+| [Relationship Track](/Help/Article/storyIntelligence.relationships.track) | Choose the underlying connection that this scene develops. |
+| [Relationship State in This Scene](/Help/Article/storyIntelligence.relationships.state) | Choose the feeling or condition supported at this point in the story. |
+| [Relationship Direction](/Help/Article/storyIntelligence.relationships.direction) | Choose whose feeling or behaviour this event records. |
+| [Reverse Relationship Direction](/Help/Article/storyIntelligence.relationships.reverse) | Swap the characters when the proposal points the wrong way. |
+| [Awareness of a Relationship State](/Help/Article/storyIntelligence.relationships.awareness) | Record whether the receiving character knows about the feeling or attitude. |
+| [Relationship Emotional Intensity](/Help/Article/storyIntelligence.relationships.intensity) | Optionally rate the strength of the emotion from 1 to 10. |
+| [Relationship Development or Discovery](/Help/Article/storyIntelligence.relationships.development) | Describe what this scene establishes or changes about the connection. |
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Relationships/Development.md

@@ -0,0 +1,18 @@
+---
+title: Relationship Development or Discovery
+category: Story Intelligence
+tags: story intelligence, relationships, development
+contextKey: storyIntelligence.relationships.development
+micro: Describe what this scene establishes or changes about the connection.
+quickTitle: Relationship Development or Discovery
+quickSummary: Describe what this scene establishes or changes about the connection.
+screenshot:
+---
+
+# Relationship Development or Discovery
+
+Write a short statement grounded in the scene, such as A defends B in public, showing growing trust. For a factual discovery, describe the fact revealed. Correct unsupported wording and avoid later-story knowledge. A non-blank description is required to accept the proposal.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Relationships/Direction.md

@@ -0,0 +1,18 @@
+---
+title: Relationship Direction
+category: Story Intelligence
+tags: story intelligence, relationships, direction
+contextKey: storyIntelligence.relationships.direction
+micro: Choose whose feeling or behaviour this event records.
+quickTitle: Relationship Direction
+quickSummary: Choose whose feeling or behaviour this event records.
+screenshot:
+---
+
+# Relationship Direction
+
+A → B means A feels or acts this way towards B. Choose Mutual / reciprocal only when the evidence supports the state in both directions. Receiving a compliment or knowing someone loves you does not prove you feel the same way. Use Reverse A and B for a one-way event running from B to A.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Relationships/Intensity.md

@@ -0,0 +1,18 @@
+---
+title: Relationship Emotional Intensity
+category: Story Intelligence
+tags: story intelligence, relationships, intensity
+contextKey: storyIntelligence.relationships.intensity
+micro: Optionally rate the strength of the emotion from 1 to 10.
+quickTitle: Relationship Emotional Intensity
+quickSummary: Optionally rate the strength of the emotion from 1 to 10.
+screenshot:
+---
+
+# Relationship Emotional Intensity
+
+Use a consistent scale: 1–3 mild, 4–6 moderate, 7–9 strong and 10 extreme is a useful convention. Fear and hostility can be as intense as love. This is not analysis confidence or a positive-to-negative scale. Leave blank when the scene does not support a rating.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Relationships/Reverse.md

@@ -0,0 +1,18 @@
+---
+title: Reverse Relationship Direction
+category: Story Intelligence
+tags: story intelligence, relationships, reverse
+contextKey: storyIntelligence.relationships.reverse
+micro: Swap the characters when the proposal points the wrong way.
+quickTitle: Reverse Relationship Direction
+quickSummary: Swap the characters when the proposal points the wrong way.
+screenshot:
+---
+
+# Reverse Relationship Direction
+
+Tick this when the evidence describes B towards A rather than A towards B. The receiving character for the awareness answer is also swapped. The labels currently keep their original names after ticking: interpret the awareness question using the reversed pair. For a mutual state, reversing does not make it one-sided.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Relationships/State.md

@@ -0,0 +1,18 @@
+---
+title: Relationship State in This Scene
+category: Story Intelligence
+tags: story intelligence, relationships, state
+contextKey: storyIntelligence.relationships.state
+micro: Choose the feeling or condition supported at this point in the story.
+quickTitle: Relationship State in This Scene
+quickSummary: Choose the feeling or condition supported at this point in the story.
+screenshot:
+---
+
+# Relationship State in This Scene
+
+A friendship may be Friendly now and Tense later. Choose the closest supported state, such as Protective, Distrustful or Reconciled. Unknown means the evidence does not establish a state; Neutral means a neutral state is supported. Do not carry a later revelation back into an earlier scene.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Relationships/Track.md

@@ -0,0 +1,18 @@
+---
+title: Relationship Track
+category: Story Intelligence
+tags: story intelligence, relationships, track
+contextKey: storyIntelligence.relationships.track
+micro: Choose the underlying connection that this scene develops.
+quickTitle: Relationship Track
+quickSummary: Choose the underlying connection that this scene develops.
+screenshot:
+---
+
+# Relationship Track
+
+Use a supported connection such as Friend, Family or Professional. Other provides a general track when a more fixed category is not appropriate. Keep the same track for later developments of that connection so its history stays together. State describes the changing feeling within the track. On factual proposals the label is Factual relationship type; selecting a type does not itself change a Development proposal into a Factual proposal.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/Review/ImportName.md

@@ -0,0 +1,18 @@
+---
+title: Name to Import
+category: Story Intelligence
+tags: story intelligence, review, importName
+contextKey: storyIntelligence.review.importName
+micro: Choose the main record name for a newly created character, place or object.
+quickTitle: Name to Import
+quickSummary: Choose the main record name for a newly created character, place or object.
+screenshot:
+---
+
+# Name to Import
+
+Replace an ambiguous manuscript mention with a clear, consistent record name. Use a recognised full name or distinctive place or object name supported by the story. Changing this field names the imported record; it does not rewrite the manuscript. If the record already exists, use the matching option instead of creating another record under a different name.
+
+# Related Guides
+
+- [Story Intelligence Review Centre](/Help/Article/storyIntelligence.reviewCentre)

PlotLine/Help/Articles/StoryIntelligence/ReviewCentre.md

@@ -0,0 +1,18 @@
+---
+title: Story Intelligence Review Centre
+category: Story Intelligence
+tags: story intelligence, reviewCentre
+contextKey: storyIntelligence.reviewCentre
+micro: Resolve characters first, then choose the story categories to review.
+quickTitle: Story Intelligence Review Centre
+quickSummary: Resolve characters first, then choose the story categories to review.
+screenshot:
+---
+
+# Story Intelligence Review Centre
+
+Confirm character identities first so relationships, knowledge and plot analysis refer to the right people. Character summaries and whole-book plot discovery can continue after those decisions are saved.
+
+Preparing or Analysing means background work is still underway. Failed categories offer Retry when supported. Complete means that category has been handled; it does not mean every suggestion was accepted. Other categories can be reviewed in any order once unlocked.
+
+Locations let you explore significant settings and uncertain identities. Scene Metrics opens analysed values on the Timeline. Return to Book or the Writer Workspace whenever you want to continue writing.

PlotLine/Views/Admin/ChapterStoryIntelligenceTest.cshtml

@@ -17,7 +17,7 @@
 <div class="page-heading compact">
     <div>
         <p class="eyebrow">Admin utility</p>
-        <h1>Chapter Story Intelligence Test</h1>
+        <h1>Chapter Story Intelligence Test <help-icon key="storyIntelligence.admin.chapterTest" /></h1>
         <p class="lead-text">This dry run detects suggested scene boundaries, runs Scene Intelligence sequentially, and can save the resulting audit data only when you choose to save it.</p>
     </div>
 </div>
@@ -32,32 +32,32 @@
 </nav>
 
 <section class="edit-panel">
-    <h2>Manual combined pipeline test</h2>
+    <h2>Manual combined pipeline test <help-icon key="storyIntelligence.admin.chapterTest" /></h2>
     <p>Use fictional sample text only. This page runs Chapter Structure first, splits the submitted chapter into in-memory scene blocks, then runs Scene Intelligence for each block without creating PlotDirector scenes.</p>
     <form asp-action="ChapterStoryIntelligenceTest" method="post">
         <div class="row g-3">
             <div class="col-md-3">
-                <label class="form-label" asp-for="Form.ProjectID">ProjectID</label>
+                <label class="form-label" asp-for="Form.ProjectID">ProjectID <help-icon key="storyIntelligence.admin.fields.project" mode="inline" /></label>
                 <input class="form-control" asp-for="Form.ProjectID" />
             </div>
             <div class="col-md-3">
-                <label class="form-label" asp-for="Form.BookID">BookID</label>
+                <label class="form-label" asp-for="Form.BookID">BookID <help-icon key="storyIntelligence.admin.fields.book" mode="inline" /></label>
                 <input class="form-control" asp-for="Form.BookID" />
             </div>
             <div class="col-md-3">
-                <label class="form-label" asp-for="Form.ChapterID">ChapterID</label>
+                <label class="form-label" asp-for="Form.ChapterID">ChapterID <help-icon key="storyIntelligence.admin.fields.chapter" mode="inline" /></label>
                 <input class="form-control" asp-for="Form.ChapterID" />
             </div>
             <div class="col-md-3">
-                <label class="form-label" asp-for="Form.ChapterNumber">ChapterNumber</label>
+                <label class="form-label" asp-for="Form.ChapterNumber">ChapterNumber <help-icon key="storyIntelligence.admin.fields.chapterNumber" mode="inline" /></label>
                 <input class="form-control" asp-for="Form.ChapterNumber" />
             </div>
             <div class="col-12">
-                <label class="form-label" asp-for="Form.SourceLabel">SourceLabel</label>
+                <label class="form-label" asp-for="Form.SourceLabel">SourceLabel <help-icon key="storyIntelligence.admin.fields.sourceLabel" mode="inline" /></label>
                 <input class="form-control" asp-for="Form.SourceLabel" />
             </div>
             <div class="col-12">
-                <label class="form-label" asp-for="Form.ChapterText">Chapter text</label>
+                <label class="form-label" asp-for="Form.ChapterText">Chapter text <help-icon key="storyIntelligence.admin.fields.chapterText" mode="inline" /></label>
                 <textarea class="form-control" asp-for="Form.ChapterText" rows="14"></textarea>
             </div>
         </div>
@@ -72,7 +72,7 @@
 @if (result is not null)
 {
     <section class="edit-panel">
-        <h2>Combined pipeline result</h2>
+        <h2>Combined pipeline result <help-icon key="storyIntelligence.admin.chapterResult" /></h2>
         @if (!string.IsNullOrWhiteSpace(result.ErrorMessage))
         {
             <div class="alert alert-warning">@result.ErrorMessage</div>
@@ -138,7 +138,7 @@
     </section>
 
     <section class="edit-panel">
-        <h2>Chapter Structure</h2>
+        <h2>Chapter Structure <help-icon key="storyIntelligence.admin.chapterResult" /></h2>
         <div class="row g-3">
             <div class="col-md-4">
                 <div class="border rounded p-3 h-100">
@@ -193,14 +193,14 @@
         }
 
         <h3 class="mt-3">Raw JSON</h3>
-        <label class="form-label" for="chapterStructureJson">Extracted Chapter Structure JSON</label>
+        <label class="form-label" for="chapterStructureJson">Extracted Chapter Structure JSON <help-icon key="storyIntelligence.admin.fields.rawOutput" mode="inline" /></label>
         <textarea class="form-control font-monospace" id="chapterStructureJson" rows="12" readonly>@result.ChapterJsonText</textarea>
-        <label class="form-label mt-3" for="chapterRawResponse">Raw OpenAI chapter response</label>
+        <label class="form-label mt-3" for="chapterRawResponse">Raw OpenAI chapter response <help-icon key="storyIntelligence.admin.fields.rawOutput" mode="inline" /></label>
         <textarea class="form-control font-monospace" id="chapterRawResponse" rows="12" readonly>@result.ChapterRawResponseText</textarea>
     </section>
 
     <section class="edit-panel">
-        <h2>Detected Scene List</h2>
+        <h2>Detected Scene List <help-icon key="storyIntelligence.admin.sceneResults" /></h2>
         @if (result.SceneBlocks.Count == 0)
         {
             <p>No in-memory scene blocks were produced.</p>
@@ -222,7 +222,7 @@
     @foreach (var block in result.SceneBlocks)
     {
         <section class="edit-panel">
-            <h2>Suggested Scene @Display(block.TemporarySceneNumber)</h2>
+            <h2>Suggested Scene @Display(block.TemporarySceneNumber) <help-icon key="storyIntelligence.admin.sceneResults" /></h2>
             <dl>
                 <dt>Paragraph range</dt>
                 <dd>@Display(block.StartParagraph)-@Display(block.EndParagraph)</dd>
@@ -286,9 +286,9 @@
             }
 
             <h3>Raw Scene Intelligence Response</h3>
-            <label class="form-label" for="sceneJson-@block.TemporarySceneNumber">Extracted Scene Intelligence JSON</label>
+            <label class="form-label" for="sceneJson-@block.TemporarySceneNumber">Extracted Scene Intelligence JSON <help-icon key="storyIntelligence.admin.fields.rawOutput" mode="inline" /></label>
             <textarea class="form-control font-monospace" id="sceneJson-@block.TemporarySceneNumber" rows="12" readonly>@block.SceneJsonText</textarea>
-            <label class="form-label mt-3" for="rawScene-@block.TemporarySceneNumber">Raw OpenAI response</label>
+            <label class="form-label mt-3" for="rawScene-@block.TemporarySceneNumber">Raw OpenAI response <help-icon key="storyIntelligence.admin.fields.rawOutput" mode="inline" /></label>
             <textarea class="form-control font-monospace" id="rawScene-@block.TemporarySceneNumber" rows="12" readonly>@block.RawResponseText</textarea>
         </section>
     }