Layer output
A full history
Every change is kept, in order, in a history that is never rewritten, so the current state can always be rebuilt from it.
- Nothing is overwritten
- Any past state can be recovered
Resulta history you can review
PLATFORM / PRINCIPLES
Four rules every tool follows.
No tool suggests or changes anything in client work until it meets them. They keep the work reviewable and leave a person in charge.
THE FOUR RULES
What each rule means in practice.
Layer output
A record with the reason
Every applied change is recorded with its reason, the value before, who approved it and the version of the rule behind it.
- Nothing happens silently
- Reviewed before the next change
Resulta change log you can explain
Layer output
No duplicated actions
Running the same step twice never repeats a change, whether the cause is a retry, a network error or a double click.
- Each change carries its own identity
- Repeats are recognised and discarded
Resultsafe to repeat
Layer output
Changes a person can undo
The state before each change is saved, and the way to undo it is designed before the change runs. What cannot be reversed, such as a sent email, is approved before it happens.
- Changes can be reversed
- A person's decision always wins
Resultreversible work
OUTSIDE SYSTEMS
Nothing changes in an outside system without a person's approval.
A tool can prepare, draft and check a change. Anything that touches an outside system, such as Amazon, DNS, an email to a customer or a public release, waits for a person's explicit approval.
web-builder / production route
Page/platform/principles/
Surface stateapproval first
EvidenceThe data and the reason are shown before anything changes.
first
DraftThe change is prepared without applying it, so the result can be seen in advance.
first
ApprovalA person approves it explicitly. Silence is not approval.
explicit
ChangeOnly after approval, and the record is written as it happens.
after approval
CheckThe result is confirmed where it happened, not only on our side.
after
Who decidesa person
No tool changes an outside system without a person. Speed never skips this step.
NEXT
If your work needs automation you can check and undo, tell us about it.
Many tools automate. Ours let a person see, approve and undo what they do.
Talk to us