reqvire

What is Reqvire?

A semantic engineering framework for building verifiable and traceable software.

Reqvire is a Git-native semantic engineering model for ontologies, capabilities, requirements, contracts, verification plans, evidence, and implementation links. It keeps engineering intent close to the codebase, computes typed change impact across the model, and gives engineers and AI assistants scoped implementation context constrained by requirements, contracts, and verification evidence.

Use the CLI, Explorer UI, and MCP tools to navigate from intent to code, understand what changes affect, and keep implementation work aligned with the verified system model.

Use Reqvire to:

• define shared ontology vocabulary and semantic contracts
• connect capabilities to implementable requirements
• attach requirement-owned contracts for behavior, state, I/O, sources, and constraints
• plan verification and link concrete evidence
• inspect traceability, coverage, and change impact
• expose structured engineering context to AI workflows without exporting a separate model

Latest Changes

Reqvire 1.0.0 is the first stable release. It formalizes the current model around ontologies, capabilities, requirements, semantic contracts, verification objectives, and concrete verification evidence.

For older workspaces, preview supported breaking model updates with:

reqvire migrate
reqvire migrate --fix

reqvire migrate is dry-run by default; --fix applies deterministic migrations such as legacy document header cleanup, verification-objective holder creation, contract relation cleanup, and legacy Contract Bindings heading migration to Contract Bindings.

---

Quick Start

Install Reqvire CLI

curl -fsSL https://raw.githubusercontent.com/reqvire-org/reqvire/main/scripts/install.sh | bash

Validate a Reqvire workspace:

reqvire validate

Open the Explorer UI from an installed Reqvire binary:

reqvire serve

Then open the printed local URL, usually:

http://localhost:8080/

No-install npm form:

npx -y @reqvire-org/reqvire@latest --workspace /absolute/path/to/workspace serve

The effective workspace root is the path used for Reqvire identifiers and relative paths. It must contain at least one eligible Git worktree; files under the workspace but outside Git worktrees are ignored by model processing.

The Explorer UI is embedded in release/npm binaries. Source builds are for development and must build the Explorer bundle before compiling Rust.

---

Skills and MCP

Reqvire exposes model context through an MCP server and ships setup assets for Claude Code and Codex. Full setup details live in the documentation: https://www.reqvire.org/coding_assistants.html

MCP Server

Start the MCP server with the Reqvire CLI:

reqvire --workspace /absolute/path/to/workspace mcp

Convenience no-install form using the npm package:

npx -y @reqvire-org/reqvire@latest --workspace /absolute/path/to/workspace mcp

This exposes Reqvire engineering context to AI assistants through the Model Context Protocol (MCP).

Reqvire MCP uses Streamable HTTP. Start the server with the command above, then point MCP clients at:

http://127.0.0.1:8081/mcp

Example MCP client configuration:

{
  "mcpServers": {
    "reqvire-myrepository": {
      "type": "http",
      "url": "http://127.0.0.1:8081/mcp"
    }
  }
}

The MCP server exposes tools, resources, and prompts. Prompt templates include regular Reqvire workflows such as model exploration, change planning, and verification coverage review, plus semantic workflows for vocabulary-driven SPARQL query construction and verification search.

Enable mutation tools:

reqvire --workspace /absolute/path/to/workspace mcp --enable-mutations

---

Claude Code

The Reqvire Claude Code plugin is distributed through the reqvire-org plugin marketplace. Marketplace installation is the default Claude Code path:

/plugin marketplace add https://github.com/reqvire-org/reqvire
/plugin install reqvire@reqvire-org

For environments that use the local Claude skills folder directly: