Perse — work management without an agent hierarchy
the line itself: an ask becomes a Form, scheduled lanes build and check it, and the outcome is recorded before the next pass.
The problem
Architecture
One decision
Memory lives in Postgres as insert-only records, not in the model’s context window. Every observation is written before the next step is taken.
Long-lived sessions carrying the state in context. Rejected because the state died with the session and could not be audited afterwards — the one property the whole system exists to provide.
See it
Measured: pull requests merged through the loop, counted from GitHub and refreshed on a schedule. Every change must pass its tests and an automated review; changes to deployment, to what the loop may do, or to its written rules wait for the operator to read them before they merge, and everything else merges once its checks pass and is read afterwards, with a revert path. The ledger records the merge, not the reading.