Docs · How PXNT works
The rules PXNT keeps
The few rules everything else follows: code shared and data never, a record of who did what, the clock of the place, and a person deciding.
The rules
1. Code is shared, data never is
Each product keeps its own database, accounts and users. Nothing in pxnt-kernel holds a customer's data.
2. People never see PXNT
Each product has its own sign-in page, brand and accounts, all running PXNT's sign-in.
3. Every change says who made it
The record of who did what is written in the same step as the change. If the record cannot be written, the change does not happen.
4. A "no" is an answer
"This task is already done" is told to the person, plainly. A tap pressed twice changes nothing and is not an error.
5. The place's clock
Which day it is and what the wall clock says always come from the site's own time zone, never from a server.
6. AI proposes, a person decides
An AI may draft a change; a person confirms it and answers for it. An AI never signs and never completes a step.
7. Differences become settings
Never a second copy of the same screen or rule for another product.
8. Products choose when to update
Each product pins a version and takes the next one on purpose, one product first.
Why
The products were built by copying each other, and copies drift: a sign-in fix made in one never reached the next. Every rule above exists so a fix is made once and reaches everyone, and so nobody has to trust a change that left no trace. How PXNT is built tells it with drawings.