Product-intent checks
Helen’s detectors
Each detector looks for one defined failure mode in product intent or implementation evidence. Review what the detector checks, when it runs, the evidence it reports, and where its authority stops.
Detector explainers
6 detectors
- 01 Stale Premise detector Helen’s Stale Premise detector finds live work that still inherits from an abandoned, obsolete, or duplicate ancestor. Deterministic graph traversal Blocking
- 02 Chain Contradiction detector Helen’s Chain Contradiction detector finds a child whose intent opposes an ancestor it is supposed to serve. Bounded semantic judgment over graph lineage Blocking
- 03 Execution Context Gap detector Helen’s Execution Context Gap detector finds user-facing stories that cannot trace to an active persona and problem. Deterministic demand-link traversal Blocking
- 04 Specification Clause Violation detector Helen’s Specification Clause Violation detector fails a pull request only when a reviewed exact checker has complete evidence of a blocking contract violation. Reviewed deterministic code-contract verification Blocking
- 05 Stale Implementation detector Helen’s Stale Implementation detector finds product intent that changed after the code most strongly associated with it. Code-symbol alignment with versioned recency evidence Advisory
- 06 Duplicate Implementation detector Helen’s Duplicate Implementation detector finds near-identical public code symbols in different files. Bounded code-signature similarity Advisory
Start with the engineering questions.
Read practical answers about governing AI-assisted delivery.