Skip to content

CMS130/CMS165: second-engine sweep needs the VSAC-completed sidecars (MM-1c) #532

Description

@Taleef7

State

cms130 and cms165 pass their MADiE decks against our runtime (64/64, 68/68, ADR-072) but have never been executed by the second engine. Their vendored terminology sidecars are VSAC-completed (ADR-041): the capped expansions in the upstream bundle were completed at vendor time from a pinned VSAC release, which needs the credential. An uncredentialed machine cannot reproduce the sidecar, and the 2026-08-04 run showed that a sweep on the upstream bundle's capped expansions is not a comparison of engines.

Why

ROADMAP_2026-08-30.md MM-1c: CMS130/CMS165 are swept before their flips. STANDARDS_CONFORMANCE.md limit (4) records them as unmeasured cross-engine.

How

Run backend-ts/scripts/cross-engine-check.ts --measure cms130 --load-terminology (and cms165) in a context that resolves the sidecar: the credentialed official-cases CI job's environment, or a machine with the VSAC key. Docker HAPI 8.10.0, fresh container per input, expansions pushed before the first evaluation. Write the dated evidence document and update the conformance row and running total.

cms165 additionally carries the routing blocker tracked separately (profile-only retrieve under trustMetaProfile: false); a clean sweep does not clear that.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    backendcql-engineCQL / measure-evaluation engineowner-opsOwner-run operational step, not agent code

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions