kal — bloghttps://kal0.dev/blog/AI-native version controlUndo is a design decision, not a featurehttps://kal0.dev/blog/undo-in-version-control/https://kal0.dev/blog/undo-in-version-control/Compare undo models: git reflog, jj op log, kal ops. What makes a safety net complete vs partial. Why operation logs beat ref2026-07-26How to tell which code an AI wrote — and prove it laterhttps://kal0.dev/blog/who-wrote-this-code/https://kal0.dev/blog/who-wrote-this-code/Git records one author string, so an agent looks exactly like a colleague. The approaches teams use to track AI-generated code, and where each breaks.2026-07-26You ran git reset --hard. Here's how to get your work backhttps://kal0.dev/blog/recover-from-git-reset-hard/https://kal0.dev/blog/recover-from-git-reset-hard/A practical recovery guide for the commands that eat your work — reset --hard, a bad rebase, a dropped stash, a deleted branch.2026-07-25Your git history records what changed, never whyhttps://kal0.dev/blog/why-your-git-history-is-useless/https://kal0.dev/blog/why-your-git-history-is-useless/Commit messages describe the diff you can already read. Why the reasoning behind a change keeps getting lost, and what to do about it.2026-07-24Four questions about AI-generated code your team can't answer yethttps://kal0.dev/blog/ai-code-audit-questions/https://kal0.dev/blog/ai-code-audit-questions/Auditors, acquirers and insurers have started asking what share of your codebase a model wrote. What to have ready before you're asked.2026-07-23