reviewing-problems

To audit a competitive programming problem package, you can use an automated tool that evaluates problem directories for constraint drift, checker-validator alignment, and statement ambiguities. It coordinates automated mechanical checks with human-in-the-loop judgement reviews.

Checker-validator alignment in competitive programming quality assurance ensures that the checker and validator logic match the problem constraints and intended behavior. The audit evaluates this alignment through a fresh-context review process to catch inconsistencies.

Yes, you can automatically detect orphan files and incomplete phases in a testlib problem directory. The mechanical audit phase identifies these structural issues, along with matrix holes and constraint drift, using specialized automated tools.

Yes, the competitive programming problem audit supports testlib package structures by evaluating problem directories for constraint drift, orphan files, and matrix holes. It verifies package structure alignment with the intended difficulty and constraints.

The best way to review problem statements for assumed definitions and unproven invariants is through a judgement audit. This process evaluates statement clarity using a fresh-context review to identify ambiguous definitions and hidden invariants.

Constraint drift in a problem package occurs when the stated constraints do not match the actual test data or validator limits. Running a mechanical audit detects this drift automatically, ensuring the test suite is robust and aligned before deployment.