LiveFreev1.3.2MIT

Evidence & review infrastructure / 01

Evidence Preflight

Turn a persuasive claim into an inspectable record before review, publication, or operational use.

01Seven bounded records

Claim, scope, provenance, comparison, failure criteria, limitations, and decision use.

02Portable contract

Draft 2020-12 JSON Schema, neutral example, library, and command-line validator.

03Private by design

The worksheet does not upload or persist entries; the validator makes no network requests.

Use it when

The claim sounds ready, but its evidence contract is still implicit.

Evidence Preflight makes a reviewer’s first questions explicit before the work moves downstream. It is useful for research findings, evaluation summaries, technical recommendations, model claims, and internal decisions whose reasoning should survive beyond the meeting or author who produced them.

Workflow

Draft, exchange, enforce.

01 / Draft

Structure the claim

Use the browser-local worksheet to write each required record and see missing-field guidance before export.

Launch worksheet
02 / Exchange

Export a stable record

Download readable Markdown or schema-identified JSON that can travel with a report, review, or repository.

Open neutral example
03 / Enforce

Validate locally

Use the dependency-free Node.js library or CLI to reject incomplete, malformed, oversized, or contract-divergent cards.

Inspect schema

Quick start

Install the exact first-party release.

The direct package is the canonical v1.3.2 distribution. npm-registry availability is not claimed.

npm install https://kaldenframelabs.com/downloads/kaldenframe-labs-evidence-preflight-1.3.2.tgz
node bin/validate-evidence-card.mjs card.json

Included

Everything needed to inspect the contract.

  • Interactive worksheetLocal drafting, completion guidance, import, and Markdown or JSON export.
  • JSON SchemaStrict, machine-readable v1 contract with exact required fields and bounded text.
  • Validator and CLIDependency-free local checks with content-safe error reporting and a 64 KB input limit.
  • Neutral exampleA complete non-domain-specific card for integration tests and orientation.

Next decision

Need to gate the artifact after the claim is documented?