diff-artifacts

To check semantic coverage and drift, supply input and output artifact paths along with a check type. The process extracts discrete input elements, classifies each as covered, partial, or dropped using model reasoning, and generates a structured coverage-check.yaml report.

Requirements traceability validation ensures output deliverables fully cover input specifications without unanchored drift. Semantic comparison uses model reasoning to evaluate element coverage rather than literal text matching, accurately identifying partial or dropped requirements across artifacts.

Generate a coverage analysis report by providing input and output artifact paths. The system computes a coverage summary containing element counts, drift items, and a coverage score, then writes the results directly to a structured coverage-check.yaml file.

Yes, you can detect dropped requirements and scope creep by comparing design and build artifacts. The drift detection mechanism flags output content that is not traceable back to any input element, revealing unanchored changes or scope additions.

Artifact diff does not use literal text matching to validate requirements coverage. It applies model reasoning to perform semantic comparison, ensuring that paraphrased or structurally altered elements are correctly classified as covered, partial, or dropped.

A limitation of semantic comparison for SDLC traceability is its reliance on model reasoning, which may require clear input and output artifact paths. It produces a structured coverage-check.yaml report but depends on the specified check type to extract relevant elements.