What problem does it solve? Developers working on Divalto Harmony ERP code need a consolidated, traceable analysis report before modifying code, but manually merging request parsing, candidate search, and evidence verification results into a coherent markdown document is slow and error-prone. ## Core Features & Use Cases - Catalog-driven report assembly: Evaluates 9 content types by deterministic relevance scoring and includes only pertinent sections (examples, impact study, action sites, business constants, dossier settings). - Dual deliverables: Produces a human-readable markdown report plus a JSON metrics file with confidence level, Neo4j coverage, and X.12/X.13 traceability counts. - Quality enforcement: Applies hard bounds, absolute-path validation, anti-stub rules, and golden tests for Jinja2 fragments before any report ships. - Use Case: After running the three analysis phases on a bug ticket, feed request.json, candidates_x12.json, and evidence_x13.json to the script to get a final markdown report with confirmed code examples, impact callers, and action proposals for the developer. ## Quick Start Run the build_report.py script with the paths to your request, candidates, and evidence JSON files to generate the final pre-action markdown report and metrics JSON in the output directory.
