fused-verifylisted

# Security, testing, and validation in fused > **Part of the Fused skill set — don't work from it alone.** Fused is `workspace ⊃ > project ⊃ UDF`. If you're validating code that belongs to a project, load > **`fused-projects`** for the end-to-end flow (specs, run, deploy) and > **`fused-execute`** for how code runs. See **`fused-guide`** for the full set. ## Overview fused has several complementary quality layers that can be applied to code before or after execution: | Layer | Tool | What it checks | |---|---|---| | Security scan | `verify_code` / `fused code verify` | Code patterns, input file safety | | Spec conformance | `verify_code(spec=...)` | LLM check: does code match intent? | | Correctness | `execute_code(expectations=...)` | Output schema, null rates, row counts | | Test suite | `test_code` / `fused code test` | Pytest + line/branch coverage in Lambda | | Audit | `get_audit_log` / `fused audit log` | What ran, what was blocked | These layers are complementary. Use them in combination for critical or production code paths. --- ## Security scanning (`verify_code`) `verify_code` scans code and input files **without executing** anything. Use it before `execute_code` when you want to catch problems early, or as a gate in CI. The scanners run in the same single canonical pre-execution order as the `execute_code` pipeline (spec required → input firewall → code → type check → spec → dependencies → input PII); it streams a best-effort progress message that never aff