Living system specifications

Keep your system’s truth intact.

Structure complex specifications, connect every claim to evidence, and give people and AI agents one dependable description of how your system is meant to work.

Get started Built for AI agents
Git-friendly filesEvidence-backed claimsAgent-ready Markdown
Payment platform✓
⌄Platform24
⌄Checkout9
·Validation4
·Payments5
›Ledger8
›Notifications7

Payment platform

Status: attention required

Claims

8f2a · verified
Every accepted payment has a durable ledger entry.
4c91 · failed
Duplicate requests never create a second charge.

Content

The platform coordinates checkout, authorization, settlement and customer notification.

specification.md# Payment platform
**verified** — Every accepted payment…
**failed** — Duplicate requests…
One source of truth

A specification that earns trust.

Turn system knowledge into a navigable hierarchy of verifiable claims—not another document that drifts away from reality.

Verify every claim

Match claims to test results and see verified, failed, unverified and ignored states throughout the hierarchy.

See integrity at a glance

Recursive status indicators expose exactly where confidence ends and investigation should begin.

Keep knowledge reviewable

Small, text-based files fit naturally into Git, making specification changes visible, attributable and reversible.

Specification integrity

Know what is true—and what still needs proof.

A healthy specification is explicit about uncertainty. Verification results roll up from individual claims to every subsystem, without hiding failures in a long document.

01

Failures stay visible

Failed evidence appears in red on the claim and every affected parent node.

02

Unknowns stay honest

Unverified claims remain distinct from claims that have passed their supporting tests.

03

Exceptions stay intentional

Ignored claims are recorded and excluded without being silently erased from the specification.

specification.md
Generated: 2026-09-01 16:16:15 +10:00

# Payment platform

**Verification status:** verified

**Claims:**

- **verified** — Every accepted payment
  has a durable ledger entry.

## Checkout

**Verification status:** failed

- **failed** — Duplicate requests never
  create a second charge.
Excellent AI context

Give agents the whole system, not a handful of guesses.

Every verification run produces a complete, depth-first specification.md. It is portable, readable and designed to become high-quality context for coding agents.

  • Structured context. Heading levels preserve subsystem relationships and boundaries.
  • Evidence-aware instructions. Claim statuses tell agents which facts are proven, failing or unresolved.
  • Repository-native. Keep the generated specification beside the code so agents can find and use it.
  • Fresh on demand. Verification regenerates the file before it is rendered or printed.
A durable workflow

From intent to evidence to shared context.

Describe the system

Break the architecture into subsystems. Add concise claims and supporting Markdown content at the right level.

Verify against reality

Read test results in place, match evidence to claims, and surface unresolved integrity gaps immediately.

Share one clear artifact

Generate specification.md for reviewers, automation and AI agents working inside the repository.

Quick start

From install to living specification in two commands.

Install the CLI globally, navigate to the directory that will contain your specification, and point the tool at your test output. The application starts and opens in your browser.

npm install -g system-specification-tool
system-specification-tool --test-results=<directory containing test output files>
The current directory becomes the specification project. Test results stay in place and may be JSON, JUnit/XUnit XML, MSTest TRX, TAP, Cargo output, or Go test -json.

Make your specification part of the system.

Replace stale documents and fragmented context with a living, verifiable description that humans and AI agents can trust.

Get started