001 — Principles
Five rules, kept.
Every Strlng tool follows the same five rules. They are the product as much as any command is.
-
01
Preview before write.
Every command that changes a store shows the exact change first. A dry run is the default path, not a flag you have to remember.
-
02
Every write is reversible.
Before a tool writes, you already have a way back: a snapshot you took, or a backup it takes for you. Undo is a command, not a support ticket.
-
03
Recovery is a procedure, not a memory.
What to do when something goes wrong is written down, in the README and the runbook. Nobody has to remember what they did last Tuesday.
-
04
Local-first, no phone-home.
Snapshots, backups and plans live on your disk. The only network traffic is to your own store's Admin API and, if you run the Fallback monitor, to your own GitHub repo. There is no Strlng server.
-
05
The same result every time.
Given the same store and the same input, the tools do the same thing. No model in the loop and no guessing.
002 — The studio
Small on purpose, with a long view.
Strlng is a small studio. The tools are maintained on the schedule of one person with a demanding day job. Requests and reports are read and answered, not on a contractual timeline.
The tools are designed to compose. If you build something on top of them, the studio would like to hear about it.