# Results and findings The CLI builds plans from your local repository, and Radforge runs the mutations on hosted infrastructure. After submission, the command prints the run ID and attempt ID. Use `rad remote status` to follow the run. A **killed** mutation caused a selected test to fail. A **survivor** left every selected test passing. Radforge reports each survivor with its source path, line, mutation type, attempt, and JSON data. For each survivor: 1. Read the original behavior and the mutation described by the finding. 2. Check whether it is an equivalent mutant, where the source changed but the program behaves the same way. 3. If the changed behavior matters, add or strengthen a test for it. 4. Rerun the affected file or Git diff. Use `--json` when a script or another tool reads the results. Treat JSON field names and state values as the stable interface. Human-readable terminal output may change between releases. Mutation testing complements code review, static analysis, and security testing. It does not prove that the code has no defects.