James WamplerandClaude Opus 5
7678cc7275
The self-nesting outline tree was more structure than chapter outlining needs.
A chapter outline is now a paragraph plus a flat, ordered table of beats, and
tags do the cross-referencing that nesting was doing badly.
A beat is one row: a three-to-five word title, an optional character, what
happened, and what's next. Ordering is a SortOrder column within the chapter —
no parent pointers, no cycle guards, no recursive tree building. Reordering is
one call taking beat ids in the order wanted; ids left out keep their relative
position at the end rather than jumping to the front.
Beats plan, scenes carry prose. The two layers stay separate and a beat's
SceneId is the optional link between them, nullable in both directions —
deleting a scene ungroups its beats rather than deleting the plan, since that
is a decision about prose and not about the outline.
Tags are project-scoped, unique by name case-insensitively, and attach to
characters, chapters and beats through three join tables so cascade deletes are
the database's job rather than ours. Applying an unknown tag by name creates it,
which keeps tagging a single action; GET /api/tags/{id}/references returns
everything carrying a tag across all three kinds at once.
Removed: OutlineNode, OutlineService, its endpoints, agent and MCP tools, and
the Outline tab. Added: Beat and Tag with their services, endpoints, 5 agent
tools and 10 MCP tools, a beat table on the chapter page, a tag editor used in
three places, and a Tags tab for cross-referencing.
Migration drops OutlineNodes — the scaffolder's data-loss warning is the
intended removal, not an accident.
44 tests, up from 31.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S56bfZMGe1hnhpWP4CjjNw
41 lines
1.4 KiB
C#
41 lines
1.4 KiB
C#
namespace NovelSoftware.Domain.Entities;
|
|
|
|
/// <summary>A chapter: an ordered container of scenes plus its own planning fields.</summary>
|
|
public class Chapter
|
|
{
|
|
public Guid Id { get; set; } = Guid.NewGuid();
|
|
public Guid ProjectId { get; set; }
|
|
public Project? Project { get; set; }
|
|
|
|
/// <summary>Position in the manuscript, 1-based.</summary>
|
|
public int Number { get; set; }
|
|
|
|
public string Title { get; set; } = string.Empty;
|
|
|
|
/// <summary>
|
|
/// The paragraph that opens the chapter's outline, above the beat table.
|
|
/// </summary>
|
|
public string? Summary { get; set; }
|
|
|
|
/// <summary>Whose head we are in for this chapter.</summary>
|
|
public Guid? PovCharacterId { get; set; }
|
|
public Character? PovCharacter { get; set; }
|
|
|
|
public string? Setting { get; set; }
|
|
public string? Notes { get; set; }
|
|
|
|
public DraftStatus Status { get; set; } = DraftStatus.Planned;
|
|
public int? TargetWordCount { get; set; }
|
|
|
|
public DateTimeOffset CreatedAt { get; set; } = DateTimeOffset.UtcNow;
|
|
public DateTimeOffset UpdatedAt { get; set; } = DateTimeOffset.UtcNow;
|
|
|
|
/// <summary>The chapter's outline: an ordered, flat list of beats.</summary>
|
|
public List<Beat> Beats { get; set; } = [];
|
|
|
|
/// <summary>The prose layer. Beats may optionally be grouped under these.</summary>
|
|
public List<Scene> Scenes { get; set; } = [];
|
|
|
|
public List<Tag> Tags { get; set; } = [];
|
|
}
|