Control
A bounded room the AI works in — and you can rewind
When an assistant actually does work — drafting, editing, organizing — it does it in a sandbox inside your project, not on your real data. Every change is a separate, reversible layer you can roll back, and it never sees your real file paths.
Available
A bounded room — and you can rewind
Project workspaceQ3 Launch · sandbox
3 uncommitted changes- +draft-summary.mdadded
- ~outline.mdedited
- →notes/moved
A derived layer — never touches your canonical data · real paths redacted.
REWIND
OPEN
Workspace opened
EDIT
Edited outline.md
MOVE
Moved notes/
NOW
You are here
fold back inroll back
Each step is recorded in the append-only event store — so the room stays reversible.
01
Why it matters
An assistant that edits your real files is a disaster waiting to happen. But an assistant that can't do anything is just a chatbot. The answer is a room with walls and an undo button.
02
What Nolocron provides
- A governed, app-owned workspace where an assistant can create, edit, move, and delete — without touching canonical data.
- Full history and rewind: fold the good work back in, or roll any of it back.
- Work is a derived projection — it can never corrupt your real archive.
- Real file paths are redacted; the assistant never learns where your data lives on disk.
03
How it works
- Open a project and give its assistant a task.
- It works in the sandbox, not on your real files.
- Review what it changed.
- Fold the good parts in, or rewind the whole thing.
04
Proof
- Its work can never corrupt or overwrite your canonical data.
- Anything it did is reversible.
- It never sees your real file paths.
Related