# Public Test and Evaluation Index — Verification Record

**Verification date:** August 25, 2026  
**Index version:** `public-test-index-v1`  
**Disposition:** VERIFIED PUBLIC CANDIDATE / NOT PUBLISHED

## Validation result

The local validator completed with zero errors across nine records:

- verified: 4;
- partial: 2;
- blocked: 1;
- open: 2.

Validation confirmed:

- all stable public identifiers are unique;
- every required metadata field is present;
- each status belongs to the frozen public status set;
- every record has at least one public-safe evidence link;
- all evidence links are relative rather than machine-local or remote;
- every linked evidence target exists; and
- every included integrity value is either a valid lowercase SHA-256 or explicitly absent.

## Inclusion review

The first version includes the three completed reproducible packages, the router direct/CLI split, the language-provenance result, one cross-trial failure-preservation record, and two explicitly open observations.

Records were separated when combining them would hide an important boundary. In particular, the router direct contract and actual CLI promotion gate are distinct entries: the former passed within scope, while the latter remains blocked.

No aggregate pass percentage is computed because the records represent different contracts, fixture classes, engines, and evidence maturity.

## Privacy review

The public index files were scanned for absolute local paths, private URLs, email-like contact data, network addresses, authorization headers, and common credential markers. The machine-readable index contains public-relative evidence links only.

## Current hashes

- `records.v1.json`: `2e06360d2ba81ad28c61aa7dc59b4c4c958ddbc94c0d25385c091cc8719a84ff`
- `validate_index.py`: `4186628ce98c6bf79d2d9ca1257b64b4af3791563c0dea485e06ad979efb0981`

The package checksum file covers the public index, records, validator, verification record, and specification; it excludes itself.

## Claim boundary

This package verifies index structure, evidence-link presence, and faithful status separation. It does not independently rerun every linked test, certify the linked systems, resolve open records, or authorize publication.