dbm-concordance-verify

Semantic concordance verification compares synthesized section outputs against the frozen concordance register and deterministic findings to surface mismatches before publication. It enforces alignment among section bodies, assertion rows, and findings, ensuring package readiness.

Post-synthesis semantic verification is needed after deterministic concordance checks and source-supersession findings are complete. It serves as a final readiness gate to ensure all section bodies, assertion rows, and deterministic findings align before publishing the package.

Semantic concordance verification produces a markdown verification report and a package-local findings CSV. These outputs document any semantic disparities between synthesized DBM section outputs and the frozen concordance register for review.

Semantic verification can be used to check alignment between section bodies, assertion rows, and deterministic findings. It identifies and reports semantic disparities across these elements against the frozen concordance register to enforce overall package consistency.

The best way to identify semantic disparities is to execute verification against the active package snapshot. This compares synthesized section outputs directly with the frozen concordance register and deterministic findings to surface any misalignments.

Semantic concordance verification runs after deterministic checks because it validates alignment among section bodies, assertion rows, and deterministic findings. It acts as a final validation layer to catch semantic mismatches that deterministic checks may not surface before publication.