Runs

A run is an ordinary turn on the company’s Profile and the agent’s model, started from a short brief: the seat, why it woke, its open issues and the company goal. Runs happen only while Synoec is open. Up to four of a company’s agents run at once, never two runs of one agent; Merge waits until no agent is running, since agents edit the company’s checkout while they work. The brief names the seat’s Specialist and the agent loads it with SpecialistRead, as a chat applies one, so its methods shape the work while the Ergon issue tools stay available.

A linked Git project gets one worktree inside the company folder, on the company’s own branch ergon/<company>. Agents change its files only there and leave the changes uncommitted; the project’s own checkout is never written by an agent. A linked folder that is not a Git repository stays read-only.

When a run’s tool needs approval, the turn waits and the request shows in the Inbox as needing an answer: Deny or Allow on its line, and, where the tool offers it, Allow for this run in its detail.

If the agent’s model or the company’s Profile is missing, the run fails with that reason. Ergon never moves an agent to another Profile or model.