Project history
In short
Every project keeps a record of the agent sessions, releases and review runs behind it, so what changed, when, and at what cost is answerable after the fact rather than reconstructed.
A Sapilon project records what happened to it. Three kinds of event make up that record:
| Record | What it captures |
|---|---|
| Agent sessions | One conversation with the agent: what was asked, what changed, what it cost. |
| Releases | A version deployed to a server, and when. |
| Review runs | An automated review over the project, and how it finished. |
Why it is kept
- Cause. “It worked last Tuesday” becomes a question with an answer: which release, which session, which change.
- Cost. Sessions carry their points, so an expensive week can be traced to the requests that made it expensive.
- Rollback. A release is a point you can return to. Going back creates a new version rather than erasing the old one.
What is not recorded
Reading your own project is not an event. Browsing files, opening artifacts, and moving around the app leave no trace and cost nothing — only work does.
Reading it well
The most useful habit is to look at the record when something is surprising, not on a schedule. A cost spike, a behaviour change, a failed gate — each of those has a session or a release behind it, and finding it is usually faster than reasoning about the code.