1. Author and check
Write one or more transactions, then validate the complete file
with undo check.
Documentation
Make filesystem intent inspectable.
UndoLang combines a deliberately small language with current-state planning, durable operation records, verified inverse metadata, and explicit recovery.
Core model: the file is a program; each named
transaction is its own recoverable boundary.
The workflow
2. Plan
Inspect paths, effects, destructive operations, conditions, and rollback estimates without mutation.
3. Approve and run
Humans confirm interactively. Agents and other noninteractive
callers pass explicit --yes.
4. Recover if interrupted
undo recover validates durable state and resumes
rollback from a fresh process.
Find an answer
| Question | Read |
|---|---|
| How do I install and run my first program? | Getting started |
| What syntax and operations exist? | Language reference |
| What happens when transaction B fails? | Programs |
| What survives a process kill? | Transactions & recovery |
| How should an agent use JSON? | AI agents |