normalize-proposals-for-enrichment

What problem does it solve?

This Skill reconciles diverse, extractor-specific proposal formats into a single normalized reconciliation file so reviewers and downstream LTM writers can approve enrichments consistently.

Core Features & Use Cases

• Source detection by STM path: Detects whether proposals came from distill, reap, codify, or decode and selects the correct mapping logic.
• Taxonomy contract validation with visible rejects: Ensures required taxonomy fields are present and emits rejected entries (not silent drops) when the contract is violated.
• Reviewer-ready reconciliation output: Produces a proposals file where every entry is initialized to approval_status: pending, ready for the enrich play’s reviewer gate.

Quick Start

Use normalize-proposals-for-enrichment to read a staged STM proposals.yaml from an extractor evidence folder and write a reconciliation-proposals.yaml at the enrich output path for reviewer approval.