Stamp, never erase, side by side

One project, two ways of keeping it. Make the same changes to both and see what each one remembers.

On the benchNovember 2026From ZilaOS, ActiveLoop
Ledgers and paper stacks in a purple wash

Every system we build keeps its history the same way. We stamp. We never erase. It is easy to say and easy to nod at, so this note lets you try both and watch what each one remembers.

Below is one project, the way ZilaOS holds it. On the left it is stored the usual way: one row, and each change writes over the last. On the right every change is a named action that adds a line to the history. Do the same things to both.

Acting as

Overwritten

Project
Bakaara warehouse fit-out
Status
Open
Owner
Amina
Updated
09:00 by Amina

Remembers 1 of 1 event.

Stamped

Status
Open
Owner
Amina
  1. project.opened by Amina · Bakaara warehouse fit-out

Remembers 1 of 1 event.

The same actions, applied to both. One keeps the last word. The other keeps every word.

What to look for

Close the project, reopen it, hand it to someone else. Then ask the left side what happened. It knows the last thing, and who touched it last. The right side knows the whole morning.

Closing and reopening ask for a reason. That is on purpose. A serious change with no reason is a question someone will have to ask later, usually at the worst time. Handing over does not ask, because the line already says who gave it to whom.

Still on the bench

The actions here are the real ones, with the words people use: close project, reopen project, hand over. What we are still working out is how the history reads when there are a thousand lines of it. One line per event is right. A screen of a thousand lines is not. The next note on this will be about folding them.

If you build, dream, or make, you belong here.

Find your way in