Review work with comments

Anchor discussion to supported dimensions while keeping review data separate from the creative document.

Comments are a review layer

Comments are stored separately from the screenplay CRDT. They use a project dimension and anchor to point at script text, outline content, or supported canvas entities. This keeps discussion from becoming screenplay text and lets the team resolve review without rewriting the artifact.

Current comment support covers the script, outline, and relevant canvas-style dimensions. Beats do not currently expose the same comment anchoring, so place beat-level discussion on the outline or in the related script context instead of expecting a hidden beat comment thread.

Viewers can participate in review

Viewer access is read-only for creative data but can still support comments. This distinction is useful for producers, clients, or reviewers who should discuss work without changing it. Project access and membership still determine whether the person can open the project.

Write actionable comments

Anchor the smallest useful target and state the decision needed. “This is confusing” is weak. “At this line, do we want Mara to recognize the signal, or should the reveal remain in scene 12?” gives location, problem, and choice.

Use replies to keep one decision together. Resolve or close threads when the underlying change is accepted, rejected, or superseded. If the anchored content is moved or deleted, confirm that the comment still points to meaningful context.

Comments are not version history. Preserve a version before large changes and use comments to explain decisions around that checkpoint.