Mac and Linux only
Windows and hosted use are outside the current release.
Known limitations
Know what Veqtor does not support yet.
The public Alpha is intentionally narrow. It refuses unsupported documents and edits rather than trying to change them approximately.
Applies to Veqtor 0.1.2Read this first
The practical limits in plain language.
These are the limits most likely to change whether Veqtor is suitable for a real negotiation.
Main document text only
Comments, headers, footers, footnotes and endnotes are not analyzed or edited.
Not every Word revision
Formatting changes, moved text and some complex layouts may be counted but cannot always be edited.
No accept or reject button
Veqtor can create supported new tracked changes. It does not accept or reject existing ones.
File names establish order
Veqtor does not prove chronology or automatically match the same clause across every draft.
Claude and the user supply judgment
Veqtor does not establish that an interpretation or proposed clause is legally correct.
Helpful local history, not independent proof
The local record can be incomplete or changed by someone who has access to the computer.
Community-supported Alpha
There is no guaranteed response, fix, compatibility or uptime.
Technical boundary
Documents and package limits
One input DOCX is limited to 50 MiB compressed, 2,000 ZIP members and 100 MiB total expanded content. XML parts are limited to 25 MiB and 100,000 structural items; one extraction is limited to 10,000 change units. A folder scan accepts at most 500 candidate documents and has 500 MiB aggregate input and expanded-output budgets.
The supported container is an unencrypted, non-ZIP64 ZIP package using STORED or DEFLATED members. Ambiguous, malformed or unsupported package structures are refused.
Tracked changes and structure
Extraction and writing cover word/document.xml. The writer supports a narrow set of tracked text replace, delete, counter and reinstate operations. Deeply nested revisions, unsupported element shapes and complex adjacent structures may be refused.
Numbering and clause labels are navigation aids, not evidence. Durable references combine the document hash, change-unit identity, structural location and checked wording.
Round interpretation
Round order is deterministic filename order, not lineage proof. There is no semantic cross-round clause matcher or authorship forensics in v0.1.
Preflight and apply
One atomic batch accepts up to 100 edits, 20,000 new characters per edit and 200,000 across the batch. Preflight runs the same document pipeline in memory, but apply can still fail if the source changes, the destination already exists or the filesystem refuses publication.
Provenance and threat model
Decision records are best-effort local provenance. They are not authenticated, signed, hash-chained or tamper-evident. The supported threat model is a non-hostile, single-user Mac or Linux workspace. A malicious process running as the same user is outside scope.
Canonical release document
This page is an accessible summary. The exact versioned contract is the KNOWN_LIMITATIONS.md file for v0.1.2. If the summary and the tagged file differ, rely on the tagged file.