6.2. What is assumed
Assumption | Checked by |
|---|---|
the server clock is roughly right (only the order of | operations (NTP) |
Postgres runs each batch as one serializable transaction, and the engine locks exactly the footprint | Postgres docs, concurrent stress tests |
the engine implements the Lean model | differential tests |
the shell hands request bodies and file texts to the model unchanged, and the clock gives whole microseconds | differential tests |
positions only increase (gaps allowed) | an increasing sequence |
only trusted backends reach the engine; they authenticate end users and set fields such as an actor id, which rules may then rely on | deployment (network access, credentials) |
Left out of the model on purpose: reading views through the API, authentication, the table layout, HTTP beyond method, path, status and body.