diff --git a/databank/agents/AGENTS.md b/databank/agents/AGENTS.md
index d82c9e0..fe1cc5c 100644
--- a/databank/agents/AGENTS.md
+++ b/databank/agents/AGENTS.md
@@ -5,6 +5,7 @@ Friday, October 24, 2025 (Timezone: UTC+00:00 - Please adjust to local system ti
 
 | Date       | Version | Description                                      | Author              |
 |------------|---------|--------------------------------------------------|---------------------|
+| 2025-10-24 | 3.0.0   | Add guidelines for gorgeous commit messages      | AIOS-Public System  |
 | 2025-10-24 | 2.0.0   | Update for databank/PMO restructure              | AIOS-Public System  |
 | 2025-10-24 | 1.0.0   | Baseline AGENTS.md for mounting across all projects | AIOS-Public System  |
 
@@ -12,6 +13,7 @@ Friday, October 24, 2025 (Timezone: UTC+00:00 - Please adjust to local system ti
 
 | Date       | Version | Description                                      |
 |------------|---------|--------------------------------------------------|
+| 2025-10-24 | 3.0.0   | Added guidelines for gorgeous commit messages    |
 | 2025-10-24 | 2.0.0   | Updated for databank/PMO restructure             |
 | 2025-10-24 | 1.0.0   | Initial creation of baseline AGENTS.md           |
 
@@ -168,8 +170,20 @@ Friday, October 24, 2025 (Timezone: UTC+00:00 - Please adjust to local system ti
 ### Commit Standards
 - Use conventional commits with semantic meaning
 - Make commits atomic (one logical change per commit)
-- Write descriptive commit messages
-- Include relevant context in commit descriptions
+- Write gorgeous, verbose commit messages when needed
+- Include comprehensive context and detailed descriptions
+- Follow the aesthetic principles of beautiful commits
+
+### Guidelines for Gorgeous Commit Messages
+- Be verbose and comprehensive when it adds value
+- Include context about why the change was made
+- Explain the impact of the changes when relevant
+- Use clear, descriptive language that future-you will understand
+- Follow the format: "type(scope): short description" for the first line
+- Add a blank line followed by detailed explanation when needed
+- Include any relevant references (issues, discussions, etc.)
+- Aim for beauty in both form and function
+- Think of commit messages as documentation for the changes
 
 ### Branching and Merging
 - Follow project-specific branching strategies