Stamp output with a data-version identifier #54

New issue

Closed

opened 2026-07-01 00:52:19 +00:00 by manlycucumber · 0 comments

manlycucumber commented

2026-07-01 00:52:19 +00:00

(Migrated from github.com)

Problem

Consumers must know which corpus and engine version produced a result so caches and clients can invalidate correctly. A data-version stamp must travel with every output.

Acceptance criteria

Output includes a data-version stamp tied to the corpus build
The stamp changes when the corpus changes
The stamp is documented in the contract
A test asserts the stamp is present and well-formed

Notes

Versioning enables the v1.0.0 contract freeze.

## Problem Consumers must know which corpus and engine version produced a result so caches and clients can invalidate correctly. A data-version stamp must travel with every output. ## Acceptance criteria - [ ] Output includes a data-version stamp tied to the corpus build - [ ] The stamp changes when the corpus changes - [ ] The stamp is documented in the contract - [ ] A test asserts the stamp is present and well-formed ## Notes Versioning enables the v1.0.0 contract freeze.