elixir-verification-gate

Verification in Elixir projects requires running Mix commands like `mix test`, `mix compile`, and `mix format --check-formatted`, then capturing exact terminal outputs as evidence. This proves tests pass, code compiles, and formatting standards are met before claiming success.

Evidence means the exact command output from Mix tasks—test results, compilation logs, static analysis reports, and migration execution output. Pasting the terminal output directly proves the claim is backed by actual execution, not assumption.

Yes. Verification applies across the full Elixir pipeline: `mix test` for tests, `mix compile` for builds, `mix format` for formatting, `mix credo` for static analysis, and `mix ecto.migrate` for migrations. Each command's output serves as structured proof.

Command outputs provide concrete, reproducible proof that code actually meets the claimed standards. Requiring evidence prevents false claims and creates an auditable record of project health across testing, compilation, and code quality checks.

Run `mix test` for test results, `mix compile` for build status, `mix format --check-formatted` for code style, `mix credo` for static analysis, and `mix ecto.migrate --log-migrations` for migration verification. Capture all outputs as end-to-end proof.

Yes. Evidence-driven verification scales from small projects to large codebases. The method remains the same: execute prescribed Mix commands and capture outputs as proof, regardless of project complexity or team size.