{"data":{"kind":"file","path":"README.md","version_id":"dph8gr95tedmd6y35430kwyo","entry":{"name":"README.md","path":"README.md","is_directory":false,"size":1255,"modified_at":"2026-11-18T05:16:03.424000","content_hash":"8beeaf701cf331389e82764e8b65b19d22c83f257a3bd6607079f8c68d879422"},"entries":[],"content":"# ocio_config_repair\n\nRepair an OpenColorIO config that loads, renders, and is wrong.\n\nFour of its five faults raise no error at all. The fifth passes every structural check and is caught only numerically, by encoding a value into a colourspace and decoding it back to somewhere else.\n\nEvery fault here is in one class: the artifact runs, raises nothing, delivers,\nand is wrong. Faults that throw are already caught by the software and are not\nworth grading.\n\n## Reward\n\nBinary, 1.0 or 0.0, with a specific reason either way. No partial credit: a\nhandoff is either correct for the department downstream or it is not, and\nrewarding \"nearly right\" teaches the wrong thing efficiently.\n\nShape checks alone are gameable, so every channel or field the repair was not\nmeant to touch is compared against a known-good reference and must match, and\neverything it was allowed to touch must still correlate with the original.\nSatisfying the rules while destroying the data is graded as a failure. On the\nfirst adversarial pass across these environments, seven of twelve attacks\nscored full reward without fixing anything; those holes are closed and the\nattacks are kept in `tools/reward_hack.py` upstream.\n\n## Source\n\nhttps://github.com/AlaboMPJ/alabo-creative-envs\n","encoding":"utf-8","truncated":false,"total_bytes":1255},"status":null}