Version Story

View saved version →

---
name: combine
description: Combine two or more independently written documents into one Word draft with attributed tracked changes. Use when the documents have no shared original.
---

# Combine independent drafts

1. Confirm that the documents were written independently. If they are edits of one
   original, use merge. Ask when that distinction is unclear.
2. Confirm the author label for each document. Do not guess authors or ask the user
   to order independent documents.
3. Call `get_instructions`, then `create_combine` with the attached files in
   `document_files` (or accessible file paths), original names, and the confirmed
   `document_authors`.
4. Follow the upload instructions if the result asks for uploads, then call
   `get_combined_document` until generation finishes.
5. Download and present the Word document in the conversation with its interactive
   link. Use `read_text` only when the user requests analysis.

Excel is unsupported for this workflow. Explain that limitation before starting.

Selected documents are uploaded to Version Story and stored in the user’s account.
Follow the user’s explicit instructions. Use only files they selected and that this
session can access. Complete OAuth through the host’s sign-in flow; never request
passwords or tokens in chat. If files are unavailable, ask the user to attach them.

When a transfer or tool call fails, report it with `report_issue`, omitting document
contents and credentials, then explain the failure and stop. If the account limit is
reached, tell the user, give them the upgrade link from the message, and stop.

View saved version →

---
name: compare
description: Compare document versions and create a PDF redline or Word tracked-changes file. Use when the user requests a comparison, redline, blackline, or explanation of changes.
---

# Compare documents

1. Identify the original and revised documents. Ask which is the original if unclear.
2. Call `get_instructions` for the current connector workflow.
3. Use `create_comparison` for files: pass attached files in `base_file` and
   `comparison_files`, or accessible file paths. Use `create_comparison_from_links`
   for HTTPS document links. Follow the upload instructions only when the result
   asks for uploads.
4. Use `get_redlines` to obtain the finished documents. Leave `download_options` unset
   for the normal viewable redline. Request `word_redline` when the user asks for Word
   or tracked changes.
5. Download and present the actual result file in the conversation, with the interactive
   redline link. Use the file presentation supported by this OpenAI environment.
6. If the user requests an explanation of the changes, use `read_text` as the source
   for that analysis. A request for a redline alone does not request a summary.

Selected documents are uploaded to Version Story and stored in the user’s account.
Follow the user’s explicit instructions. Use only files they selected and that this
session can access. Complete OAuth through the host’s sign-in flow; never request
passwords or tokens in chat. If files are unavailable, ask the user to attach them.

When a transfer or tool call fails, report it with `report_issue`, omitting document
contents and credentials, then explain the failure and stop. If the account limit is
reached, tell the user, give them the upgrade link from the message, and stop.

View saved version →

---
name: merge
description: Merge two or more parallel revisions of the same original into one Word document with attributed tracked changes. Use when reviewers edited separate copies of a shared base.
---

# Merge parallel revisions

1. Identify one original and at least two revisions of it. Ask which draft everyone
   started from when the shared base is unclear. If the drafts were written
   independently, use the combine workflow. If they form a chronological chain,
   use version history.
2. Confirm the author labels for the revisions. Do not guess authors. Revision order
   does not change the result, so do not ask the user to order parallel edits.
3. Call `get_instructions`, then `create_merge`, passing attached files in `base_file`
   and `next_version_files` (or accessible file paths), original file names, and the
   confirmed `next_version_authors`.
4. Follow the upload instructions if the result asks for uploads, then call
   `get_merged_document` until generation finishes.
5. Download and present the Word document in the conversation with its interactive
   link. The user resolves competing tracked changes in Word. Use `read_text` only
   when the user requests analysis.

Excel is unsupported for this workflow. Explain that limitation before starting.

Selected documents are uploaded to Version Story and stored in the user’s account.
Follow the user’s explicit instructions. Use only files they selected and that this
session can access. Complete OAuth through the host’s sign-in flow; never request
passwords or tokens in chat. If files are unavailable, ask the user to attach them.

When a transfer or tool call fails, report it with `report_issue`, omitting document
contents and credentials, then explain the failure and stop. If the account limit is
reached, tell the user, give them the upgrade link from the message, and stop.

View saved version →

---
name: version-history
description: Trace changes through successive versions of a document and create one Word document attributing surviving changes to their source versions. Use for requests about how a document evolved or who introduced a change.
---

# Trace a document’s history

1. Establish the versions in chronological order, oldest first. If the user has not
   specified the order, propose it from the names or dates and obtain confirmation.
   Incorrect ordering changes attribution.
2. Confirm each version’s author label with the user. Use supplied names and do not
   invent authors.
3. Call `get_instructions`, then `create_version_history` with the attached files in
   `version_files` (or accessible paths) in the confirmed order, original file names,
   and the confirmed `version_authors`.
4. Follow the upload instructions if the result asks for uploads, then call
   `get_version_history_document` until ready.
5. Download and present the Word document in the conversation. Use `read_text` when
   the user requests an explanation or asks about a particular change.

Excel is unsupported for this workflow. Explain that limitation before starting.

Selected documents are uploaded to Version Story and stored in the user’s account.
Follow the user’s explicit instructions. Use only files they selected and that this
session can access. Complete OAuth through the host’s sign-in flow; never request
passwords or tokens in chat. If files are unavailable, ask the user to attach them.

When a transfer or tool call fails, report it with `report_issue`, omitting document
contents and credentials, then explain the failure and stop. If the account limit is
reached, tell the user, give them the upgrade link from the message, and stop.