Limen
Governed multi-agent production with evidence at every boundary
Limen Concept Sketch
Problem
Complex software delivery becomes expensive when authority, ownership, work routing, verification, and handoff live only in conversation. Adding agents increases throughput, but it also multiplies ambiguous claims, duplicated work, hidden capacity use, and unsafe state transitions.
Approach
Limen treats production work as a bounded conduct graph. A deterministic record keeper owns lifecycle transitions and leases; native agent lanes keep their identities; work packets can only narrow authority, scope, budget, deadlines, depth, and fanout. Human sessions remain protected while routine reversible engineering continues.
Outcome
The system turns coordination into inspectable evidence: exact heads, changed paths, predicates, review state, cost, child receipts, rollback information, and a named handoff. The value is not agent volume. It is the ability to make complicated delivery governable without taking ownership away from the people responsible for it.
Limitations
Repository activity and orchestration receipts do not establish product adoption or business impact. Limen governs the delivery process; each deployed product still requires its own operational, user, and commercial evidence.