> ## Documentation Index > Fetch the complete documentation index at: https://docs.wirevow.dev/llms.txt > Use this file to discover all available pages before exploring further. # Why does this file look the way it does? > The output lists the file's commits newest first Run: ```sh theme={"dark"} gitvow why ``` Agent commits show the session, the step within that session, the agent's stated plan before committing, and the attribution: `agent share` is the fraction of added lines that match what the agent wrote; `lines changed by a person afterwards` means a human reworked it before committing. Commits marked `(person)` were made by a human with no session. How to use the answer: * If a person changed lines after the agent, treat that region as deliberate; do not "fix" it back. * If a plan names a constraint (an ordering, a compatibility reason, a boundary), keep it unless the user asks otherwise, and cite the session in your explanation. * If it says a session note is not available, the author has not pushed notes; say so rather than guessing. * For a specific region, follow with `gitvow trace :-`. Never read transcripts or ledger files directly; the command already returns the redacted record.