Methodology

Measure a claim. Keep its boundary.

VeriEnvelope is an evidence-based evaluation system for reproducible AI Tool and Model Context Protocol testing. It separates specification, implementation, observation, interpretation, and admission.

01

Claim

The narrow behavior stated before execution.

02

Method

The frozen rule that says what counts.

03

Evidence

The observation preserved without a rewrite.

04

Envelope

The conditions and limits attached to the result.

Before execution

The component identity, testable statement, expected observation, decision rules, execution boundary, and revalidation triggers are written down before a measurement is authorized.

After execution

Raw observation remains distinct from interpretation and diagnosis. A result can be demonstrated, not_demonstrated, insufficient, unknown, or out_of_envelope.

What admission means

admitted means the record may enter the current registry within its stated envelope. It does not certify the component, establish production readiness, or decide fitness for use.

History is part of the evidence

When a Method or Runner defect is found, the old package stays. A repaired Method requires a new authorization and a new measurement. The Filesystem case preserves exactly that sequence.

Read the full Methodology ↗