Document Editing
16 requirements
·
48 scenarios
Outgoing Attachment Traceability
JR-document-editing-001
The system SHALL associate outgoing document attachments with both the originating source attachment and the parent conversation. This ensures full traceability from any delivered document back to its source.
3 test scenarios
- Revised clean document links to source attachment JR-document-editing-001.1
- Tracked changes and redline attachments link to source JR-document-editing-001.2
- Sent attachments maintain proper source linkage JR-document-editing-001.3
Previous Draft Retrieval
JR-document-editing-002
The system SHALL retrieve the most recent previously-sent clean draft by tracing the linkage back to the original source attachment. This enables iterative editing workflows where each revision builds on the last.
3 test scenarios
- Retrieve previous draft by source attachment JR-document-editing-002.1
- No previous draft exists on first edit JR-document-editing-002.2
- Multiple previous drafts select most recent JR-document-editing-002.3
Incremental Redline Generation
JR-document-editing-003
The system SHALL generate incremental redlines showing only changes made since the previous AI-generated draft. Users can review the latest round of edits in isolation.
2 test scenarios
- Incremental redline generated from prior draft JR-document-editing-003.1
- Incremental redline reflects only new changes JR-document-editing-003.2
Cumulative Redline Generation
JR-document-editing-004
The system SHALL generate cumulative redlines showing all changes from the original document through the current draft. The cumulative view preserves full change history against the original.
1 test scenario
- Cumulative redline generated from original document JR-document-editing-004.1
Dual Redline Output
JR-document-editing-005
The system SHALL generate both cumulative and incremental redline PDFs when a previous draft exists. On first edit, only a single cumulative redline is produced.
2 test scenarios
- Follow-up edit produces both redline PDFs JR-document-editing-005.1
- First edit produces single redline PDF JR-document-editing-005.2
Incremental Change Summaries
JR-document-editing-006
The system SHALL generate edit summaries in the cover note based on incremental changes since the last sent draft, not cumulative changes. On first edit, all changes are shown.
3 test scenarios
- Follow-up summaries show only incremental changes JR-document-editing-006.1
- First edit summaries show all changes JR-document-editing-006.2
- No incremental changes produces empty summary JR-document-editing-006.3
Definition Term Auto-Formatting
JR-document-editing-007
The system SHALL automatically apply bold formatting to defined terms when inserting new definitions, matching the document's existing definition style conventions. Terms already formatted are not reformatted.
9 test scenarios
- Definition term bolded when neighbors are bold JR-document-editing-007.1
- Multiple definitions inserted together JR-document-editing-007.2
- Definition using shall-mean variant JR-document-editing-007.3
- Definition using has-the-meaning variant JR-document-editing-007.4
- Multi-word definition term formatted JR-document-editing-007.5
- Bracket-prefixed definition formatted JR-document-editing-007.6
- Already-formatted definition not double-tagged JR-document-editing-007.7
- Non-definition quoted text not tagged JR-document-editing-007.8
- No style model available triggers fallback JR-document-editing-007.9
Visual Change Snippet Generation
JR-document-editing-008
When document edits are finalized, the system SHALL generate visual snippets showing changes. Deleted text is displayed with red strikethrough and inserted text with blue underline.
3 test scenarios
- Single edit change rendered JR-document-editing-008.1
- Multiple edit changes rendered JR-document-editing-008.2
- No changes yields empty snippet JR-document-editing-008.3
Cover Note Change Snippets
JR-document-editing-009
The document editing workflow SHALL include a change summary section in the cover email, showing a visual representation of text changes made to the document.
2 test scenarios
- Cover note includes change snippets JR-document-editing-009.1
- Snippet styling matches redline output JR-document-editing-009.2
Edit Source Citation Tracking
JR-document-editing-012
The system SHALL support an optional citation on document editing operations to track the source of each edit for traceability. Omitting the citation SHALL remain backward-compatible.
3 test scenarios
- Text replacement called with citation JR-document-editing-012.1
- Paragraph insertion called with citation JR-document-editing-012.2
- Citation omitted preserves backward compatibility JR-document-editing-012.3
Edit Provenance Model
JR-document-editing-013
The system SHALL define a structured model to capture edit provenance, including source type, reference identifier, and contextual details. This enables auditing of why each edit was made.
2 test scenarios
- Playbook-sourced edit captured JR-document-editing-013.1
- Email-sourced edit captured JR-document-editing-013.2
Edit Rationale as Document Comment
JR-document-editing-017
The text replacement operation SHALL accept an optional rationale parameter that, when provided, inserts a Word comment on the edited paragraph explaining the change to opposing counsel.
3 test scenarios
- Edit with rationale creates document comment JR-document-editing-017.1
- Edit without rationale has no comment JR-document-editing-017.2
- Failed edit does not create comment JR-document-editing-017.3
Insertion Rationale as Document Comment
JR-document-editing-018
The paragraph insertion operation SHALL accept an optional rationale parameter that, when provided, inserts a Word comment on the newly inserted paragraph explaining the addition to opposing counsel.
2 test scenarios
- Insert with rationale creates comment on new paragraph JR-document-editing-018.1
- Insert without rationale has no comment JR-document-editing-018.2
Multi-Paragraph Insertion
JR-document-editing-020
The system MUST provide a multi-paragraph insertion capability that inserts multiple paragraphs in a single operation, automatically chaining each new paragraph after the previously inserted one.
2 test scenarios
- Section with subsections inserted JR-document-editing-020.1
- Partial failure handled gracefully JR-document-editing-020.2
List Numbering Preservation
JR-document-editing-024
When the AI deletes an entire list item's content and that item is not the last in its list, the system SHALL replace the deletion with a placeholder instead of removing the content. This preserves list numbering and prevents downstream section references from becoming stale.
4 test scenarios
- Middle list item deletion intercepted with placeholder JR-document-editing-024.1
- Last list item deletion allowed JR-document-editing-024.2
- Non-list paragraph deletion allowed JR-document-editing-024.3
- Partial text deletion within list item allowed JR-document-editing-024.4
Structural Paragraph Deletion
JR-document-editing-027
The system SHALL provide a paragraph deletion capability that removes a paragraph by its structural identifier without requiring text-based matching. When a rationale is provided, the system SHALL insert a Word comment on the adjacent paragraph.
4 test scenarios
- Paragraph deleted by identifier JR-document-editing-027.1
- Deletion with rationale creates adjacent comment JR-document-editing-027.2
- Invalid identifier returns error JR-document-editing-027.3
- Malformed identifier returns error JR-document-editing-027.4