What it does
Not reachable in this release. Two pieces exist as libraries: a readiness worksheet built from live data, and a signed pack format with an offline verifier command. No server route or command produces either.
How it works
The worksheet builder gathers audit-trail volume, role and session counts, retention, hold and erasure counts, and key-management state into one report whose certification field always reads not_a_certification_or_attestation. Its notes state that retention rules are declarative and that legal holds do not cover every deletion path.
The pack format bundles controls, configuration, audit proofs, restore drills, incidents and operator actions into one JSON file with a manifest, section digests and an Ed25519 signature. The kynetra-evidence-verify command takes --pack and --trust files, checks the schema version, signer trust, signature, section digests, audit proof and record digests without the database, and exits non-zero on any failure. The verifier cannot recompute the keyed audit chain, because it does not hold the key. The pack carries its own SHA-256 chain over the exported records, which shows they were not altered after export and does not show they match the live log.
Where you reach it
- CLI
kynetra-evidence-verify --pack <pack.json> --trust <trust.json> [--json] (verifies a pack; nothing in the server produces one)
Limits
- Nothing in the server or the kynetra command builds a pack or a worksheet, so a user cannot produce one in this release.
- Neither the worksheet nor a pack is a certification or an attestation.
Evidence
- On this siteAvailable now: the audit log
- Tests96 pack and verifier tests and 14 worksheet tests exist (tampering, redaction, signer trust, digests); none run through the server
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.