Skip to main content
⚠️ Draft — Non-authoritative content (noindex)
INFORMATIVEDRAFTnone
Truth Source: Repository schemas and tests are authoritative.

Evidence Pack Contract

[!IMPORTANT] Non-Normative Document

This document is informative only.

SSOT: Validation_Lab/governance/contracts/
This page is a Reference projection. Authority resides in the Validation Lab repository.

What is an Evidence Pack?​

An Evidence Pack is the input to the Validation Lab's adjudication engine. It contains all artifacts, timeline events, and metadata required for the Lab to evaluate your implementation against Lifecycle Guarantees.

No Execution Hosting

The Lab does not run your code or accept uploads for execution. You generate evidence packs locally in your own environment, then the Lab evaluates the pack against versioned rulesets.

Pack Structure​

A valid evidence pack typically includes:

ComponentPurpose
manifest.jsonPack metadata, version, and integrity checksums
artifacts/Context, Plan, Trace, and other module outputs
timeline/Event logs (e.g., events.ndjson)
snapshots/State snapshots for diff-based evaluation
integrity/Checksums and hash files
Non-Normative Note

The exact structure and required fields depend on the pack format version (e.g., pack-v0.2, pack-v0.4). See the SSOT contract documents for authoritative field definitions.

Pack Versioning​

Evidence packs use the pack-v* prefix for format versioning:

VersionDescription
pack-v0.2~v0.4Current active formats

Each ruleset declares which pack versions it is compatible with.

Portability & Recheck​

Evidence packs are designed to be:

  • Portable — Can be exported and reviewed outside the Lab
  • Recheckable — Same pack re-evaluated yields same verdict
  • Auditable — All evidence pointers are resolvable

Export Contract​

The Lab provides an export contract for curated runs:

ExportFormatPurpose
curated-runs.jsonJSONConsumer export for downstream systems

See SSOT: export/curated-runs.json for the authoritative schema.