tripact is a deterministic traceability engine that keeps your spec, your docs and your tests in sync. It turns requirements and documentation into claims with stable, content-derived ids, links those claims to tests through explicit tags, and reports when any side stops agreeing with the others.

$ tripact check                 # a spec claim exists, but no test references it
✗ drift detected — 1 new-uncovered
edge specs ↔ tests: 0/1 covered
  NEW-UNCOVERED addition.adda-b-returns-sum "add(a, b) returns the sum of two integers"
✗ drift detected                # exit 1

# …tag the test with @specs:addition.adda-b-returns-sum, baseline once…
$ tripact check
edge specs ↔ tests: 1/1 covered
✓ level                         # exit 0 - the requirement is provably tested

No LLM is used in any of that, so the output is deterministic. The questions it cannot answer without judgement - "is this reworded requirement the same one as before, or a new one?" - are surfaced as a structured queue for you or your agent to answer.

tripact is an engine that any agent or harness can drive through --json and exit codes. It emits claims, queues and ready-to-hand-off briefs, and spawns no agents of its own.

Install

Requires Git and Node.js ≥ 22. Tested on Linux and macOS; Windows is not supported yet.

npm install -D tripact       # or: pnpm add -D tripact · yarn add -D tripact
npx tripact --version

The quickstart goes from zero to one passing check on an example repository in five minutes.

Documentation

docs/overview.md is the full documentation:

• Quickstart - install, a config, a first green check
• Concepts - layers, claims, verdicts, edges
• How it works - the repair loop, rewording, escalations
• Supported specification styles - what parses as a claim, spec-system presets, (TBD)
• Configuration - every tripact.yaml key
• Derived outputs and generators - derived, blocks, generator prefixes, --allow-shell
• CLI reference - every command, flag and exit code
• Usage - agent instructions, loops, harnesses, CI, merging on a team, the library API

Project

• CONTRIBUTING.md - development setup, and how a change to behaviour flows through the spec and the tests
• SECURITY.md - threat model, the tripact.yaml trust boundary, and how to report a vulnerability privately
• CODE_OF_CONDUCT.md
• CHANGELOG.md
• UAC.md - tripact's own acceptance criteria; the prescriptive layer it checks itself against
• docs/architecture/public-contract.md - the versioned --json and MCP shapes
• Licensed under Apache-2.0; see NOTICE