Skip to main content
gitvow report describes a pull request. gitvow digest describes a stretch of time: what the agents did in this repository over the last week, how much of it a person changed, and what the gate stopped. It is the page an engineering lead reads on Monday, and it comes entirely from the record.

What it shows

Agent share and human-edit counts are the same numbers the session notes carry; the digest only adds them up. Gate counts come from the repository’s own hook log, so they cover sessions run on this machine.

What it is for

  • A weekly read of how much of the repository’s change is agent-made and how much of that people reworked, which is the closest thing to a trust curve the record offers.
  • Spotting sessions with a low agent share or many human edits afterwards: the agent’s work needed correction, and the plan says what it was attempting.
  • Seeing which gate rules fire in practice, before tightening or relaxing the policy.

Limits

It reads the current branch’s history. Sessions whose notes were never pushed appear with commits but without plans. It does not read transcripts.