About Weavatrix Quality
Weavatrix Quality (WVQ) helps development teams plan and verify software changes by connecting OpenSpec obligations and Git diffs to existing test runners. It provides a CLI, MCP server, and JavaScript interface for producing revision-bound evidence and verdicts.
Key features
- 01Plan and select tests for changes
- 02Run protection tests for impacted code
- 03Bind obligations to test evidence
- 04Verify and explain composite verdicts
- 05Record browser flows with Playwright
Use cases
- 01Assess which tests a Git change affects
- 02Check obligations against existing proofs
- 03Run impacted tests and verify them in CI
- 04Draft, preview, and promote test programs
MCP support
Its MCP server exposes tools for coding agents to inspect quality context, plan and run checks, view status, verify results, and inspect evidence. An authoring profile adds test-program drafting, validation, preview, and promotion tools.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
7Saved tool list · updated 3w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| change | string | No | Change id, or `current` when exactly one OpenSpec change exists. |
| purpose | string | No | Why context is requested: spec, implementation, or review. |
| token_budget | integer | No | Maximum approximate tokens in the QualityContextPacket. |
Details
From the project READMEWeavatrix Quality (wvq)
Know what your change can break — and whether it is still protected.
Weavatrix Quality (WVQ) turns OpenSpec intent + a Git change into revision-bound proof using your existing runners. The ordinary green path spends 0 runtime LLM tokens. Rust owns policy, selection, evidence, and proof; npm/JS is a typed boundary around the same binaries.
OpenSpec → what must remain true
Weavatrix → what changed and what it can affect
Runners → smallest safe protection set
WVQ → same-revision Proof + composite verdict
| Surface | Package |
|---|---|
| npm (primary) | @weavatrix/wvq |
| MCP Registry | io.github.Weavatrix/weavatrix-quality |
| crates.io | wvq-cli · wvq-mcp · wvq-bench |
| Release | v0.1.0-alpha.5 |
Alpha 0.1.0-alpha.5. Useful first product loop (one plan → one execution →
one report). Not the full v1 DoD — see CHANGELOG and
ADR 0003.
Install
# primary distribution (ships wvq + wvq-mcp + wvq-bench for 6 platforms)
npm install --save-dev @weavatrix/[email protected]
# one-shot without adding a dependency
npx @weavatrix/[email protected] --help
# Rust binaries (alpha crates; API unstable)
cargo install wvq-cli --version 0.1.0-alpha.5
cargo install wvq-mcp --version 0.1.0-alpha.5
cargo install wvq-bench --version 0.1.0-alpha.5
Unscoped wvq is blocked by npm name-similarity rules — always use @weavatrix/wvq.
5-minute quickstart
cd your-repo
# 1) read-only discovery (never writes, never seals)
npx @weavatrix/[email protected] doctor
# 2) write fail-closed policy (first time only)
npx @weavatrix/[email protected] init
# 3) compile OpenSpec obligations for a change folder
npx @weavatrix/[email protected] spec validate --change current
# 4) run the smallest safe protection set (also builds measured coverage)
npx @weavatrix/[email protected] run \
--change current \
--base origin/main \
--head HEAD \
--scope impacted \
--evidence-policy minimal
# After a successful native coverage runner, Weavatrix `coverage_map` reads:
# .weavatrix/coverage/lcov.info
# Quality does not invent a second stack. Playwright is last-resort JS only.
# 5) read-only composite verdict from stored evidence
npx @weavatrix/[email protected] verify --change current
Need bindings before proofs can seal? Start from .weavatrix-quality/config.yaml and the examples.
CLI cookbook
All commands take --repo <path> (default: .). Prefer absolute paths in CI.
Day-to-day cycle
alias wvq='npx @weavatrix/[email protected]'
wvq doctor
wvq plan --change checkout-fix
wvq select --change checkout-fix --base origin/main --head WORKTREE
wvq run --change checkout-fix --base origin/main --head WORKTREE --scope impacted
wvq status
wvq verify --change checkout-fix
wvq explain <proof-or-finding-id>
Spec / seal / debt
wvq spec validate --change checkout-fix
wvq spec seal --change checkout-fix # fail-closed; needs valid obligations
wvq debt --change checkout-fix --base origin/main --head HEAD
wvq baseline --change checkout-fix --decision observed_only # CLI-only, not MCP
Observe-only CI (Stage A)
# facts stay honest (UNPROVEN / NOT_ENOUGH_EVIDENCE), process exit stays 0
wvq verify --change checkout-fix --observe-only true
Browser record → promote later via MCP/Studio
wvq record --change checkout-fix --route /checkout
wvq ingest-journal --file .weavatrix-quality/journals/session.json
wvq ingest-cassette --file captures/checkout.har --origin https://app.example.test
Shadow selected-vs-full (bench)
wvq bench --repo . --change checkout-fix --base origin/main --head WORKTREE
# or: npx @weavatrix/[email protected] bench --repo . ...
Exit codes
| Code | Meaning |
|---|---|
0 | success / observe-only (even when verdict is unresolved) |
1 | unresolved evidence / ordinary failure |
2 | blocking CONTRADICTED verify |
Full CLI surface: wvq --help. Deep product rules live in
docs/STATUS.md.
MCP cookbook
WVQ ships as an mcport MCP host. Default profile = 7 tools, no shell, large artifacts as handles only.
Cursor (mcp.json)
{
"mcpServers": {
"weavatrix-quality": {
"command": "npx",
"args": [
"-y",
"@weavatrix/[email protected]",
"mcp",
"--repo",
"C:/path/to/your-repo"
]
}
}
}
Claude Desktop
{
"mcpServers": {
"weavatrix-quality": {
"command": "npx",
"args": ["-y", "@weavatrix/[email protected]", "mcp", "--repo", "/Users/you/src/app"]
}
}
}
Default tools (coding agents)
quality_context quality_plan quality_run quality_status
quality_verify quality_explain quality_evidence
Example agent workflow:
quality_context— what obligations exist for this changequality_plan— gaps vs existing proofs (no execution)quality_run— execute impacted protection and publish.weavatrix/coverage/lcov.infofor Weavatrixcoverage_mapquality_verify— composite verdictquality_explain/quality_evidence— drill into a handle or id
Authoring profile (TestProgram draft → preview → promote)
npx @weavatrix/[email protected] mcp --repo . \
--profile authoring \
--change checkout-fix \
--base origin/main \
--head WORKTREE
quality_test_draft quality_test_validate quality_test_preview
quality_test_promote quality_test_record quality_test_heal
doctor / init / baseline stay CLI-only so agents cannot treat discovery
or an observed baseline as authority.
More configs and JSON-RPC samples: examples/mcp/.
JavaScript library cookbook
npm install --save-dev @weavatrix/[email protected]
Plan → run → verify
import { WvqClient } from '@weavatrix/wvq'
const wvq = new WvqClient({ repo: process.cwd() })
const plan = await wvq.plan({ change: 'checkout-fix' })
console.log(plan.obligations, plan.gaps)
const run = await wvq.run({
change: 'checkout-fix',
base: 'origin/main',
head: 'WORKTREE',
scope: 'impacted',
evidencePolicy: 'minimal',
})
console.log(run.run_id, run.outcome, run.scope_reason)
const verify = await wvq.verify({ change: 'checkout-fix' })
console.log(verify.state, verify.quality.proof, verify.base, verify.head)
if (verify.blocking) {
for (const reason of verify.quality.blocking_reasons) {
console.error(reason.code, reason.detail)
}
process.exit(2)
}
Spec / select / debt / explain
await wvq.specValidate({ change: 'checkout-fix' })
const selected = await wvq.select({
change: 'checkout-fix',
base: 'origin/main',
head: 'HEAD',
})
console.log(selected.selected, selected.uncovered_mandatory)
const debt = await wvq.debt({
change: 'checkout-fix',
base: 'origin/main',
head: 'HEAD',
})
console.log({ new: debt.new, fixed: debt.fixed, returned: debt.returned })
const detail = await wvq.explain(verify.proofs[0]?.id)
console.log(detail.summary, detail.provenance)
MCP client from Node (default + authoring)
import { WvqMcpClient } from '@weavatrix/wvq/mcp'
const mcp = new WvqMcpClient({
repo: process.cwd(),
profile: 'default',
change: 'checkout-fix',
})
const status = await mcp.call('quality_status', { change: 'checkout-fix' })
const verdict = await mcp.call('quality_verify', { change: 'checkout-fix' })
const authoring = new WvqMcpClient({
repo: process.cwd(),
profile: 'authoring',
change: 'checkout-fix',
base: 'origin/main',
head: 'WORKTREE',
})
const draft = await authoring.draft()
const validated = await authoring.validate(candidateProgram)
const preview = await authoring.preview(validated.program, {
screenshot: true,
trace: true,
})
if (preview.passed) {
await authoring.promote(preview.preview_id, validated.program)
}
CI snippet (GitHub Actions)
- uses: actions/setup-node@v4
with:
node-version: 24
- run: npx @weavatrix/[email protected] doctor
- run: >
npx @weavatrix/[email protected] run
--change current --base origin/${{ github.base_ref }} --head HEAD
--scope impacted --evidence-policy minimal
- run: npx @weavatrix/[email protected] verify --change current --observe-only true
Runnable copies: examples/js/ · examples/cli/.
Repository policy
.weavatrix-quality/config.yaml binds concrete tests to obligation IDs.
A green suite without this mapping stays UNPROVEN.
quality_policy_v: 1
test_bindings:
- path: tests/permissions.spec.ts
runner: playwright
case: viewer cannot delete a widget
obligations: [permissions-delete]
cost: 10
flake_penalty: 0
browser:
base_url: http://127.0.0.1:3000
engine: chromium
headless: true
module_root: .
wvq init writes a fail-closed starter. This repo dogfoods change
wvq-invariants — see examples/cli/dogfood.sh.
Browser preview needs Playwright in the target repo:
npm install --save-dev playwright
npx playwright install chromium
What WVQ is / is not
| Is | Is not |
|---|---|
| Spec-to-Proof over existing runners | A second test framework |
| Weavatrix-backed impact + selection | A browser engine (Playwright stays) |
| CLI + MCP + typed JS boundary | An OpenSpec fork |
| 0 LLM tokens on the green path | Automatic silent oracle healing |
| Fail-closed on unknown schemas | A single global “quality %†|
Place in the ecosystem:
Weavatrix UNDERSTAND what exists in source
Weavatrix Quality PROVE what must still be true after this change
Weavatrix Loom COMPOSE capabilities into ordinary Rust
Build from source
Requires Rust 1.89+.
cargo test --workspace --locked
cargo clippy --workspace --all-targets --locked -- -D warnings
Docs map
| Doc | Use when |
|---|---|
| examples/ | Copy-paste CLI / MCP / JS |
| CHANGELOG | What alpha ships |
| docs/STATUS.md | Maturity matrix + next task |
| docs/adr/0003-… | Alpha vs deferred v1 |
| docs/CANONICAL-MASTER-SPEC.md | Normative product design |
License
MIT. See LICENSE.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.