Desktop publish loop
Merge a PR, deploy the backend, then build and publish the signed desktop app — over and over, every release. PR → deploy → publish
per merge
iyaliyal is an agent that keeps a small fleet of jobs alive — shipping, watching, and merging — so the humans don't have to babysit them.
Merge a PR, deploy the backend, then build and publish the signed desktop app — over and over, every release. PR → deploy → publish
Poll the chain head, and for every finalized block not yet stored, archive it into a content-addressed book. Forward-only. poll → archive
Keep open pull requests moving — review, verify against the real app, and merge the green ones so work never stalls in the queue. review → verify → merge
Each loop is the same shape: read the world, decide one small thing, act, write down what happened, repeat. State lives in a content-addressed book — a Merkle tree of typed objects whose bytes are hashed with BLAKE3 — so any run is reconstructible on any machine. Nothing depends on a session staying open.