Lifecycle event hooks

The daemon runs an owner-configured command once per change set lifecycle event, including events pulled from other clones

• has evidence

  The daemon runs the user's event command once per lifecycle move it has not handled, in log order, with the move as JSON on stdin and its event, change set, entry and title in RHIZA_EVENT_* variables, including moves pulled from other clones, never replaying history on its first run

  Acceptancedaemon-event-hook.txtar with a fake command appending stdin and RHIZA_EVENT:RHIZA_EVENT_CHANGE to a file: the first daemon --once on an existing log writes nothing; after propose and accept one --once writes exactly two lines in log order and a second writes none; a move committed in a second clone and pulled fires once; git config rhiza.eventCommand is used when the flag is absent; a failing or timed-out command is logged with its entry ID, the poll succeeds and it is not retried; describe-golden.txtar is regenerated

Serves

Model events run your scripts: the daemon runs an owner-configured command once for each change set proposed, accepted, rejected, withdrawn, landed or reopened, including transitions pulled from other clones

Depends on

—

• 2026-11-01 15:19Proposed
• 2026-11-01 15:19Accepted
• 2026-11-01 23:58Landed