validating-solutions

Stress-test competitive programming solutions by executing a matrix of deliberately-wrong code against a test suite to identify logic holes, performance mismatches, and edge-case failures. The skill manages a zoo of failure modes to ensure test suite robustness.

Yes, algorithm-validation requires the ioi isolate sandbox environment and testlib to ensure accurate verdict reporting and resource constraint enforcement. These dependencies guarantee that execution matches competitive programming judging conditions.

Yes, validating-solutions operates within a problem directory context to compare model solutions against alternative algorithms and brute-force oracles. It uses arbiter logic to resolve disagreements through exhaustive brute-force verification.

An invocation matrix is a testing mechanism that runs multiple solution variants against a test suite to identify mismatches and holes. It detects logic errors, performance bottlenecks, and edge-case failures across the zoo of deliberately-wrong code.

Resolve disagreements between multiple accepted solutions using arbiter logic, which performs exhaustive brute-force verification. This compares model solutions against alternative algorithms within the problem directory to pinpoint exact failure modes.