{"category_id":"repository","default_severity":"warning","description":"Executable script test/spec artifacts are prohibited in operational trees. Repository Standards owns this path boundary; semantic workflow analysis belongs in Code Standards.","examples":[{"after":"Terraform validation, precondition, or shared policy","before":"iac/bell/preview-contract.test.ts","expected_severity":"warning","id":"sarj-artifact-no-operational-script-tests","language":"text","title":"Operational source-coupled test"}],"fix":"Delete the operational test and every invocation. Moving or renaming it is not remediation; express the invariant in Terraform, shared policy, provider state, or runtime behavior.","kind":"rule","references":[],"rule_id":"repository/artifacts/operational-script-tests","rule_version":2,"slug":"operational-script-tests","source":{"path":"src/repo_standards/policy_sarj/policy.py","symbol":"repository/artifacts/operational-script-tests"},"title":"Keep script tests out of operational trees","topic_id":"artifacts","why":"Bespoke deployment tests create parallel contracts that drift from Terraform, providers, shared policy, and runtime behavior. Workflow contents are outside this exact-tree rule's evidence boundary."}