normalize-proposals-for-enrichment

Normalizing multiple YAML proposal formats applies deterministic per-source transformations to reconcile diverse extractor outputs into a single file. It maps fields based on STM path detection, ensuring consistent reviewer approval and downstream LTM enrichment.

When taxonomy contract validation fails during proposal normalization, the process emits rejected entries rather than silently dropping them. This visible reject mechanism ensures missing or undetectable sources are explicitly reported in the output reconciliation file.

Missing or undetectable data sources are handled through explicit rejected-entry reporting during YAML reconciliation. The process performs taxonomy contract validation and outputs rejected entries to ensure no source data is silently dropped before LTM enrichment.

Preparing reconciliation proposals for LTM enrichment involves initializing every normalized entry with a pending approval status. This creates a reviewer-ready output file where target-path scope checks and taxonomy validation have already been applied.

Yes, deterministic mapping logic can be applied for different extractor types by detecting the STM path source, such as distill, reap, codify, or decode. The process selects the correct mapping transformation for each specific extractor evidence folder.