dbm-concordance-seed

Concordance seeding transforms raw evidence atoms and risk inventory rows into typed publication concordance candidates. It assigns authority sections conservatively and tags rows as Ready-for-Freeze or Needs-Review according to documented rules.

Generating a typed candidate CSV requires mapping planning inputs and evidence artifacts for a defined scope. The process enforces required input and output paths, applies the normalization contract, and produces scope-local typed candidates.

Scope-bounded concordance processing reads only mapped planning inputs and evidence artifacts for the assigned scope. It preserves boundary and provenance by operating on a defined scope with two scope-local outputs: a typed candidates CSV and a seed QA markdown.

Yes, you can seed publication concordance candidates for a single approved section, bounded group, or consolidation pass. The process converts risk inventory rows and evidence atoms while enforcing required inputs and applying authority section assignments conservatively.

Rows are tagged Needs-Review when the normalization contract detects ambiguities during authority and section ownership assignment. Conservative tagging ensures safe freeze decisions by flagging any uncertain concordance evidence for manual review.

Concordance seeding requires mapped planning inputs and evidence artifacts for the assigned scope. It enforces required input and output paths to ensure traceable provenance and produces a typed candidates CSV and a seed QA markdown.