Engineering leadership
How do I catch contradictions between tickets and strategy?
First make the chain explicit. Then compare the meaning of each execution item with the parent it is supposed to serve. A contradiction is not weak similarity; it is an intent that actively opposes its ancestor.
Separate missing links from opposing intent
A ticket with no strategy path has a traceability gap. A ticket linked to a strategy that it opposes has a contradiction. Those failures need different evidence and different repairs.
Use structural checks to prove that the relationships exist. Use a bounded semantic review to judge whether the connected statements can both be true.
Candidate pair
Compare artifacts only when they share a direct ancestor-descendant line.
Cited rationale
Require the judge to name the conflicting intents and preserve its confidence.
Human decision
Let the accountable owner revise the child, revise the parent, or dismiss the finding with a reason.
How Helen checks the chain
Helen narrows candidate pairs through graph lineage and semantic similarity. Its judge emits a Chain Contradiction finding only when the child opposes its ancestor above the configured confidence floor.
Near-duplicate parent and child text follows a different detector because repetition is not contradiction. That distinction keeps the finding actionable.
Review the nearest decision boundary
Resolve the lowest conflicting link first. That usually reveals whether the ticket drifted, the parent changed, or the decomposition was wrong.