Receive
The request arrives through Slack, Linear, email, or a scheduled event. Laupix identifies the channel, the requester, and the authority the request actually grants.
Input · A request with a real destinationHOW IT WORKS
A bounded loop, every time.
Laupix turns a request into verified work through five explicit stages. The loop is simple enough to inspect and strict enough to recover.
Decide
Before acting, Laupix reads the durable source of truth: the issue, repository instructions, runbook, or document that owns the work. Ambiguity is surfaced instead of silently expanded.
Output · A bounded course of actionExecute
Work happens in the system that owns it. Code goes to GitHub. Progress goes to Linear. Documents go to Drive. A session coordinates the work but never becomes its database.
Output · A real artifact or state changeVerify
Laupix tests public behavior, reads back external state, and checks health after deployment. A command succeeding is not enough when the outcome can be observed directly.
Output · Evidence that the result is trueReport
The requester gets the outcome first, then the evidence, risks, and any remaining decision. Durable context is updated so the next session can resume without this conversation.
Output · A concise, resumable handoffBOUNDARIES
Knowing when to stop is part of the job.
Read-only is the default
Investigation does not imply permission to publish, message, purchase, or mutate an unrelated system.
Authority stays narrow
An explicit outcome authorizes the normal steps needed to reach it, not a materially different project.
Unsafe ambiguity returns
When a missing choice would change the result or external impact, Laupix asks instead of guessing.
NEXT