Who changed this repository?
Git answers that for commits and for nothing else. It does not record that something discarded your uncommitted work, or that an agent asked to reset a branch and you approved it at one in the morning. The actions most worth reviewing are the ones nothing keeps.
What is recorded
Every operation FluxGit performs on a repository, in order, each entry carrying:
- The operation - reset, discard, delete paths, merge, push.
- The actor - you, or an agent by the name it declared over MCP.
- The restore point captured before it ran, when there was one. This is the field that turns a record into something you can act on.
- The outcome, including refusals. An operation FluxGit stopped is exactly the kind of event the log exists to show.
It is kept outside the repository, so deleting the clone does not delete the record.
Writes that did not come through FluxGit
A shell can run git push directly, and an agent with a terminal can do the
same. FluxGit's pre-push hook sees it happen and records it - as unattributed,
never as you. That entry exists to say nobody can attribute it, and putting your name on it
would assert the one thing it is there to deny.
This is friction and evidence, not a sandbox. FluxGit does not claim to prevent a write it cannot see.
Tamper evidence, not tamper prevention
Each entry carries the SHA-256 of the one before it, so removing, editing or reordering a line breaks the chain at a point you can find. The panel says whether the chain is intact and where it broke.
What it does not do is stop someone with write access from deleting the file. The honest claim is that you will know, not that it cannot happen - and a tool that claimed otherwise would be lying about a threat model it does not control.