icfpc-module-synthesizer

Create a JSON spec with a behavior table of input/output cases, then run synthesize-module.mjs with --verify-official and --json. The tool searches with exact BFS or CEGIS and writes a verified .man module only if official verification passes.

Use examples when matching only a few listed cases, with no guarantee for unlisted inputs. Use complete-table only when the enumerated cases are the entire target domain, which strengthens the minimality claim.

With caseStrategy auto, full-case BFS runs for fewer than 16 cases and exact CEGIS for 16 or more. CEGIS starts from up to 4 representative cases and adds counterexamples until the candidate passes the full table.

Unknown means the maxStates budget was reached, not that no solution exists; increase the budget or narrow opcodes with justification. Bounded-unsat means no candidate exists within maxInstructions, so raise the instruction limit and recheck the spec.

No, it only synthesizes new straight-line one-shot modules from behavior tables. For shrinking an existing .man room or pipe layout, use the icfpc-layout-optimizer skill instead.

No, the supported ABI is one ordinary room, one worker, one input and one output pipe, and a branch-free straight-line instruction sequence ending in H. Contracts involving branches, loops, or multiple ports are out of scope.