# Changelog

All notable public-safe changes to the Open Accounting–Labor Data Linkage Hub release package are documented here.

## 0.1.0 — 2026-08-21

### Added

- Prototype methodology for the planned Lightcast↔CCM and Lightcast↔Revelio linkage objects.
- Explicit source decisions, candidate-audit rows, accepted-release rows, target identities, target levels, validity intervals, and cardinality policies.
- A Lightcast↔CCM contract that treats GVKEY as the accepted firm identity and retains any time-valid GVKEY–PERMNO history in a separate downstream bridge.
- Public-safe JSON schema with separate source, target, candidate, and final-decision objects.
- Tri-state geography and temporal evidence: `match`, `conflict`, or `missing`; missing evidence receives no positive score credit.
- Generic TypeScript reference implementation for normalization, candidate generation, illustrative scoring, ranking, diagnostics, and explicit decision-record validation.
- A self-contained `.tgz` package with compiled JavaScript, declarations, source, tests, package metadata, license, and synthetic inputs; its bundled tests run without dependency installation.
- Synthetic example records using `SYN-` identifiers, reserved `.example` domains, and explicit target levels.
- Shared error taxonomy covering names, corporate structure, time, collisions, and source coverage.
- Benchmark protocol separating the development/adjudication set, frozen holdout, and validated release.
- Evidence-gated definitions for Prototype, Public beta, and Validated release, including predeclared intended-use performance criteria before a validated claim.
- Citation metadata, third-party data exclusion, file-level checksums, and a deterministic release manifest.

### Evidence ceiling

Version 0.1.0 does not include:

- a production Lightcast↔CCM or Lightcast↔Revelio mapping;
- licensed row-level records or proprietary identifiers;
- a publicly established canonical private source chain;
- a production exact-identifier rule or acceptance threshold;
- an adjudicated production development set;
- a frozen production holdout;
- a predeclared or passed production acceptance criterion;
- benchmark-supported precision, recall, coverage, unresolved-rate, collision, or temporal-consistency estimates;
- a Validated release claim.

### Release boundary

Only files on the build script's explicit public allowlist are copied into the website. The release builder clean-compiles the reference package, rejects unexpected archive members, and records the package archive in the manifest. The independent verifier checks checksums, exact archive contents, synthetic identifiers, reserved domains, target levels, candidate/decision schema separation, bundled test execution, and prohibited private-path, credential, and signed-URL patterns before the site is considered verified.