← Plugin catalog
Business & Operations

Syntheia

SYNTHEIA PTY LTD v1.0.0

Compare and query contracts

Create a free account to save this plugin.

From the developer

Not specified in the available declarations: capabilities, limitations, pricing & account requirements.

Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 21, 2026. Package observed Nov 21, 2026.

View package source →

Description

From the marketplace listing

Syntheia brings two things lawyers do every day into ChatGPT. Compare: upload a counterparty's draft and your last version, and Syntheia returns a clause-by-clause list of insertions, deletions, and moved text, with a redlined document to download. Query: ask a question about one agreement, a group of agreements, or your whole workspace. Syntheia navigates each document's structure, follows cross-references, and returns the exact provision text with a link to the source clause, so every answer is grounded in the document rather than in a summary. Documents stay in your private Syntheia workspace, and results are scoped to your account.

Language: English · Automatically detected from descriptions.

What changed

Similar plugins

Finding similar plugins… Results will appear here automatically.

Browse plugins →

Files & skills

File archives

Plugin package4 files · 21 KBBrowse files →
Skill instructions
redline-issues-list16.8 KB

View saved version →

---
name: redline-issues-list
description: "Turn a Word document's tracked changes (redline, markup, blackline) into a structured issues list for lawyers. Use this whenever someone uploads or refers to a redlined .docx and wants the changes reviewed, summarised, risk-assessed, or turned into an issues list or change log -- including casual phrasings like 'review this redline', 'what did they change', 'go through the counterparty's markup', 'summarise the blackline', or 'is there anything nasty in here'. Reads w:ins/w:del revisions straight from the OOXML in document order with real clause numbers, separates out formatting-only edits, picks up Word comments and counter-edits, and builds a change / comments / impact table -- then asks which side of the deal the user is on and re-weights the impact ratings from that position."
---

# Redline Issues List

Produces a lawyer-facing issues list from a redlined `.docx`: every substantive
tracked change, in document order, with a plain description, an analysis of
what it does in practice, and a 1-10 impact score -- then revised once you know
which side of the deal the user is on.

The value here is not in listing the edits (the script does that). It's in the
comments column: what the change actually does given *this document's*
definitions and cross-references. A reviewer who could only get a list of
diffs would open Word and read the redline themselves.

Background you need: a `.docx` is a zip; the body is `word/document.xml`;
tracked insertions are `w:ins` elements, deletions are `w:del` elements whose
text sits in `w:delText`; comments live in `word/comments.xml` and list
numbering in `word/numbering.xml`. The script below handles all of that.

## Extraction

`scripts/extract_changes.py` walks the document once and classifies every
revision. Use it rather than reading `document.xml` yourself: Word tags
formatting-only edits with `*Change` elements that read like content edits;
revisions nest (an `<w:ins>` wrapping a `<w:del>` is a counter-edit across
markup rounds, not a plain deletion); a substitution is routinely split by a
stray space into what looks like two unrelated edits; clause numbers usually
live in `numbering.xml` rather than in the paragraph text; and changes hide in
table cells, footnotes, and deleted paragraph marks.

```bash
python scripts/extract_changes.py redline.docx > changes.json      # full detail
python scripts/extract_changes.py redline.docx --markdown          # starter table
python scripts/extract_changes.py redline.docx --all-parts         # + headers/footers
python scripts/extract_changes.py redline.docx --seq 20-40         # one batch, full context
python scripts/extract_changes.py redline.docx --brief             # compact index
python scripts/extract_changes.py redline.docx --text              # greppable plain text
```

Accepts a `.docx`, an unzipped folder, or a bare `document.xml` (clause numbers
and comments need the full package). Body, footnotes, and endnotes are scanned
by default. Read the script's docstring for its limitations before trusting a
clause number in an unusually numbered document.

**What comes back:** `content_changes` (the table's raw material),
`formatting_changes` (excluded, but see below), `comments`, and
`unanchored_comments`. Each content change carries `sequence` (document order),
`type`, `old_text` / `new_text`, `inserted_then_deleted` for counter-edits,
`location` (heading path plus clause number), `paragraph_context` with the edit
marked inline as `⟦DELETED: …⟧` / `⟦INSERTED: …⟧`, plus author and date.

## Workflow

### 1-2. Extract, with formatting changes set aside

Running the script covers both steps: every revision is picked up, and
formatting-only ones are already separated. Two things to do before moving on:

**Check `summary.formatting_changes_needing_review`.** A `pPrChange` that also
shifted numbering or list level is flagged there. Promoting or demoting a
clause changes what it is subordinate to, and renumberi

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
SYNTHEIA PTY LTD

Package observed Nov 21, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 21, 2026 · 18:00 UTC
Collection status
Collected

plugin_asdk_app_6a98163f30548191864ee5e6188b09f6

Download plugin data (JSON)

Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.