/**
 * pipeline/attribution-versions.ts
 *
 * Version constants for the live attribution ensemble (the score-change
 * attribution that ships in reports, computed by `computeJudgmentAttribution`
 * in `compute-attribution.ts` and wired by `compute-attribution-step.ts`).
 *
 * These are the cache-invalidation axes recorded in the attribution-meta
 * artifact and read by the diagnosis runner. They are versioned independently
 * of any one algorithm file; `scripts/check-version-bumps.ts` guards them so a
 * change here forces a deliberate `ensembleVersion` bump.
 *
 * History: these constants previously lived in `pipeline/attribution.ts`
 * alongside `attributeChanges` — a dormant, correlation-based Phase-1
 * attribution path with no production call site, superseded by
 * `computeJudgmentAttribution`. That dead code (and its tests) was removed in
 * W-doctype-retrieval-attribution; the still-live version constants moved here,
 * to a module that names their real owner (the ensemble), not the dead code.
 */
/** v0 sentinel — no embedding call in v0; v1.2's flip to a real
 *  model name (e.g., "text-embedding-3-small") mechanically forces
 *  ensembleVersion's right segment to change, invalidating cached
 *  weights downstream. */
export declare const embeddingModel = "none";
/** VER-01 D-02 — co-located ensemble version. Compound semver-ish
 *  shape: "{algorithmVersion}+{embeddingModel}" (per D-02 of Phase
 *  4 CONTEXT.md). Phase 1 landed the constant; Phase 4 wires the
 *  compound shape and the bump-by-calibration discipline
 *  (calibrate-attribution.ts is the ONLY allowed bumper). */
export declare const ensembleVersion: "0.1.0+none";
/** Version tag for the calibration set fixture co-located in the repo.
 *  Bump when the fixture structure changes (e.g. when v1 moves the
 *  calibration set to Content Lake or expands to ~30 stratified rows). */
export declare const calibrationSetVersion = "v0-fixture";
