Governance & compliance

Capability ledger validator

Keeps the engineering team's own capability claims tied to files that exist in the repository.

ResearchEngine edition 5f8ea3af

What it does

An offline command-line tool in the engine repository that validates a ledger of capability claims. Each claim names a status, a commit and the files that back it. It runs during development. It is not part of the database server and it is not a feature of a deployment.

How it works

The capledger command has five subcommands: validate checks a ledger file against its schema and evidence rules, summary prints status totals, migrate-v2 upgrades a ledger file, check-artifact validates a benchmark artifact file, and foundry-portfolio validates an internal research portfolio. It reads the git index and parses URLs and fetches nothing. A clean run means the claimed evidence files exist and the document is consistent. It does not mean the claims are true.

Where you reach it

  • CLIcapledger validate <ledger.json> | summary | migrate-v2 | check-artifact | foundry-portfolio

Limits

  • Internal tooling. It is not reachable from a running server and is not scheduled as a product feature.
  • A clean validation shows that files exist. It says nothing about whether a claim is true.

Evidence

  • On this siteCapability catalogue
  • Tests93 tests exist in the tool (schema rules, evidence paths, migration, artifact checks)

Test coverage is listed as present in the engine repository at this edition. This page does not report test results.

KynetraDB is in private preview

This is not available in the preview. Request a preview to discuss the current scope.