Skip to main content

​
Synopsis

​
Description

pome compile-seeds turns a task file’s prose ## Seed State section into a compiled <task>.seed.json sidecar next to the markdown. Write the starting world in English; let the compiler produce the JSON the twin loads. The compiler checks its own work: it loads the sidecar into the twin before writing it, so a seed that the twin would reject never reaches disk.
Compiling calls a model, and you pay for it. The CLI calls Anthropic directly and needs ANTHROPIC_API_KEY in the environment. With no [target] it walks ./tasks and makes one call per file, so point it at a single file while you are still iterating.

​
What it compiles, and what it skips

The compiler emits a GitHub seed today, so it works on tasks that declare github and nothing else. It prints one line per file on stdout, and any failure on stderr, saying which of these happened: A hand-authored sidecar outranks --force. Those seeds encode adversarial setups — a backdoored pull request, a fabricated green CI status, an exfiltration lure — and a recompile would quietly rewrite what the task tests while the run still reported normally. To recompile one deliberately, delete the sidecar first.

​
Arguments

​
Options

​
Examples

Compile one task:
Compile every task under ./tasks/ — one model call per file:
Recompile after editing the seed prose:

​
Exit status

​
See also

  • pome tasks — the bundled tasks, whose seeds are worked examples.
  • pome twin — boot a twin from a seed file by hand.
  • Write a task — where the seed section sits in the task format.