waldyrious

aspe:keyoxide.org:Q24ZRMWF2VFSRKFSDLTOXCG43Q

waldyrious

Principles for good commit messages

A summary of the patterns and best practices I use in detailed git commit messages (title+body).

---

Standard practices

In general, I try to follow the established good practices for good commit messages, particularly as documented in:

waldyrious

Git alias: merge-diff

Note: This alias and the explanation below were created with Gemini 3, and manually edited for clarity and comprehensiveness.

Summary

This alias allows you to check whether a branch has been fully merged into a target branch (even if squash-merged or rebase-merged) and, if not, view the exact diff of what remains to be integrated.

Unlike a standard git diff, this approach:

1. Ignores history divergence: It bypasses any changes that may have been added to the target branch on top of the point that your branch branched off from. In other words, it compares the final state of your branch against the target, as if you had done a git rebase followed by git diff .

waldyrious

A Theoretical Framework for AI Memory Systems

Executive Summary

This report examines the theoretical foundations of AI memory systems, moving beyond implementation details to explore the cognitive models, philosophical assumptions, and design principles that underpin different approaches. We'll classify memory architectures by their theoretical commitments, evaluate the LLM + knowledge graph paradigm, and explore deep questions about compressibility, consolidation, and the nature of machine learning itself.

---

Part 1: Taxonomy and Comparison of AI Memory Systems