Requirements Verification

Verify requirements audits the latest complete generated Pine source against the behaviour explicitly requested in the project. It is useful after a new build, a staged Build Plan or several rounds of modification. The audit does not rewrite the code. It separates implemented, partially implemented and missing requirements and identifies behaviour that still needs manual TradingView testing.

Before the audit is sent, Xen displays the collected requirements for review. Remove obsolete instructions or clarify the wording when the project changed direction. Requirements Verification uses the selected supported model and consumes credit.

Reading the report

The report presents an overall match and explains the evidence for each explicit requirement. Implemented items cite relevant source. Partial and missing sections describe the gap, while manual-test items identify behaviour that static source inspection cannot prove. Risks can identify order, calculation, repainting or lookahead concerns without treating every concern as a missing feature.

Repairing a gap

When an explicit requirement is missing or partial, Repair missing requirements prepares a focused request using the audit and original requirements. The repair should address only confirmed gaps and preserve unrelated working behaviour.

Run verification again after a complete revised script is returned, but do not repeat repair indefinitely when a result remains unchanged. The requirement may need clarification or may only be provable through Pine Editor, chart behaviour or Strategy Tester.

Requirements Verification is static analysis. It does not compile Pine Script and does not replace TradingView testing.