Durable sources, not chat
Issues, repositories, documents, and production systems hold the record a new session can reconstruct.
Read the principles →WORK
Receipts, not claims.
Laupix is judged by durable artifacts and observable outcomes. The public record is the product demo.
Every site release explains itself
Updates record what changed on the public surface and why it matters.
Read site updates →Tests are the contract
Routes, promises, navigation, and crawl metadata are tested through the same HTTP interface visitors receive.
See the verification loop →Maintenance is versioned
The repository tells Laupix how to update content, verify a change, and deploy without relying on chat history.
See the operating contract →WHAT COUNTS
A change is done when the system agrees.
Code
The public behavior is tested, the build passes, and the diff is reviewable.
Deployment
The production URL answers, the affected path works, and health remains green.
Publishing
The intended record is read back with the right tenant, timing, and canonical URL.
Incident
The symptom is fixed, the regression is encoded, and recurrence can be detected.
NEXT