Veqtor

Documentation

A technical map of Veqtor 0.1.2.

Start here for the public tool surface and operating model. Use the versioned GitHub documents when you need the exact request, response and error contract.

Public technical Alpha · Current site docs: v0.1.2

Operating model

Veqtor is a local MCP server using the stdio transport. Claude remains the model and reasoning layer. Veqtor exposes deterministic document operations for a narrow Word redline workflow.

The server has no embedded model calls. Tool results enter the MCP client conversation and may be sent to the user’s model provider.

Public tools

list_rounds

Discover negotiation drafts

Scans one local folder, ignores Word lock files and reports readable rounds in deterministic filename order.

extract_redlines

Read supported tracked changes

Returns change units, document hashes, structural references and bounded paragraph context.

verify_quote

Check one quote at its source

Compares supplied wording with one anchored change and returns exact, normalized or not_found.

preflight_edits

Test the complete edit batch

Runs the full document-processing pipeline in memory and never creates an output document.

apply_edits

Create a new tracked-change output

Writes supported replace, delete, counter and reinstate edits atomically to a create-if-absent file.

export_decision_record

Export compact local provenance

Returns a privacy-aware summary of the best-effort local activity journal for later review.

Expected trust sequence

  1. List the available rounds.
  2. Extract the current redlines.
  3. Verify every quotation used as evidence.
  4. Preflight the complete proposed edit batch.
  5. Apply only when the batch is reported as applicable.
  6. Re-extract the output and export the decision record.

Veqtor never overwrites the source or an existing output file. A successful write creates a new Word document and normally appends to a private local journal.

Local decision records

Unless disabled, tool calls append JSON Lines records to <matter>/.veqtor/decision-records.jsonl. The raw journal may contain verbatim matter text and should not be committed or shared.

These records are best-effort local provenance. They are not authenticated, signed, hash-chained or tamper-evident. Always check record_status before treating an operation as durably recorded.

Versioned primary documentation

Why link to the tagged version?

The site explains the product. The tagged files define the exact behavior of the release you install.

Start with sample documents

New to Veqtor? Start with the visual workflow.

Watch the demoConnect Veqtor