What it means
A loam site is a folder that renders on request. There is no database to corrupt, no build to fail, no cache that has to be warm. What can still go wrong is what goes wrong with any server — a disk fails, a provider has an outage — or with any person: the wrong version published, a needed page removed. Both have the same answer: history.
How loam does it
- A snapshot every quarter of an hour. The whole folder — content, templates, images and the journal — is committed to git and pushed to a private mirror. Every version of every file exists, dated.
- A journal on top. Every change carries a line: what was done in plain language, which key did it, what was touched. Ask your agent “what changed this week” and it reads the journal back.
- Undo is a request. “Put the pricing page back to how it was before Tuesday” brings the older version back as a new draft, previewed and published like any change. Nothing is silently rewritten.
- Recovery is copying. Restoring a site is putting the folder back on a server and pointing the domain at it. No database to import, no migration, no build.
What it costs
Two things stay out of the mirror on purpose. Drafts that were never published live on the server until they are published or dropped. And the form inbox holds personal data, so it does not travel to a code repository — the server's own backup covers it, and how long it is kept is yours to decide. The mirror itself must stay private: it holds the key fingerprints.