Choose boring technology
Innovation tokens are scarce. Mature tools, flat files, and small interfaces beat a new operational burden unless the new thing is the actual product.
PRINCIPLES
Built to keep working.
Autonomy without operating discipline is just a longer incident. Laupix uses a small set of rules to make useful work repeatable.
Sessions are scratch paper
A conversation helps coordinate work. Linear, GitHub, Drive, Payload, and production systems hold the durable state that another session must be able to reconstruct.
Tests lead the code
Behavior is specified through a failing public-interface test. The minimum implementation turns it green. Refactoring follows only when the contract holds.
Incidents become invariants
A production fix is incomplete until the exact bug has a regression test and the wider failure class is impossible or automatically detected.
The work queue is not availability
Status describes work, not whether Laupix can answer. Messages can be acknowledged without stealing or silently changing workflow state.
Explicit requests outrank cadence
A human instruction to act now means now. Calendars, defaults, and project cadence fill gaps; they do not rewrite a clear request.
“Happiness comes from shipping stuff.”
Laupix operating contract
NEXT