# Date/Time
Friday, October 24, 2025 (Timezone: UTC+00:00 - Please adjust to local system time)

# Change Tracking/Revision Table

| Date       | Version | Description                                      | Author              |
|------------|---------|--------------------------------------------------|---------------------|
| 2025-10-24 | 3.0.0   | Add guidelines for gorgeous commit messages      | Charles N Wyble (@ReachableCEO) |
| 2025-10-24 | 2.0.0   | Update for databank/PMO restructure              | Charles N Wyble (@ReachableCEO) |
| 2025-10-24 | 1.0.0   | Baseline AGENTS.md for mounting across all projects | Charles N Wyble (@ReachableCEO) |

# Changelog

| 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           |

---

# AGENTS.md - Guidelines for AI Agents in Restructured AI Home Directory

## Core Operating Principles

### Context Awareness
- You are operating within a mounted AI home directory with separated databank (readonly) and PMO (read-write)
- **Databank** (`/ai-home/databank/`): Contains readonly context, guidelines, and personal information
- **PMO** (`/ai-home/pmo/`): Contains project management functionality where updates are allowed
- Always consider the multi-project implications of your actions
- Respect the readonly nature of the databank and only update PMO when appropriate

### Communication Protocol
- Primary communication channel: collab/ directory in mounted AI home directory
- Use question -> proposal -> implementation workflow
- Document all significant decisions and changes with proper revision tracking

### Documentation Standards (Apply to ALL files you create)
- **Date/Time Headers**: Include date/time with timezone in all markdown files
- **Change Tracking**: Maintain revision tables in all documents
- **Changelog**: Include changelogs in all source code files
- **Make It Beautiful Rule**: All documentation follows beautiful formatting standards (tables, bullet points, clear structure, visual hierarchy)

## Repository Management

### Structure Requirements
- **Databank**: Readonly context (do not modify)
  - `databank/personal/` - Personal information
  - `databank/agents/` - Agent guidelines and tools
  - `databank/context/` - General context information
- **PMO**: Read-write project management (updates allowed here)
  - `pmo/dashboard/` - Dashboard views
  - `pmo/projects/` - Project registry and tracking
  - `pmo/reports/` - Status reports
  - `pmo/resources/` - Resource management
  - `pmo/config/` - Configuration
- Keep top-level repository clean (databank, pmo, and collab directories only)
- Use conventional commits (chore:, feat:, docs:, fix:, etc.)
- Commit frequently using atomic commits
- Only commit to local repository (no git push operations)

### Access Rights
- **Databank (readonly)**: Access only, no modifications allowed
- **PMO (read-write)**: Only update when project milestones reached or status updates needed
- **Collab (readonly)**: Access for reference, no modifications in active projects

## Development Workflow

### Pre-Work Checklist
- [ ] Read project-specific documentation first
- [ ] Check collab/rules directory for project-specific guidelines (SECURITY.md, RELEASE.md, GITFLOW.md, etc.)
- [ ] Review databank context for consistent understanding
- [ ] Understand project dependencies and constraints

### Implementation Standards
- Follow conventional commits with beautiful, descriptive messages
- Maintain consistency with existing codebase
- Add appropriate documentation and comments
- Consider maintainability and future extensions

### Verification Process
- Validate operations before execution
- Run appropriate tests and quality checks
- Verify outputs against expected outcomes
- Implement defensive programming practices

## PMO Update Guidelines

### When to Update PMO
- When project milestones are reached
- When project status changes significantly
- When new projects are initiated
- When projects are completed or paused
- When resource allocation changes

### What to Update in PMO
- Project registry in `pmo/projects/`
- Dashboard information in `pmo/dashboard/`
- Status reports in `pmo/reports/`
- Resource tracking in `pmo/resources/`

### What NOT to Update
- **Never modify databank files** - they are readonly
- Do not create new top-level directories
- Do not modify collab files in active projects
- Do not add audit logs to this repository (audit logs belong in projects)

## Best Practices for Solo Entrepreneur Workflow (14+ Hours Daily AI Usage)

### Efficiency Optimization
- Break complex tasks into atomic operations
- Provide quick wins while building long-term value
- Minimize context switching between projects
- Optimize for rapid iteration and feedback

### Decision Documentation
- Document reasoning for complex decisions
- Consider impact across multiple interconnected projects
- Maintain traceability for future reference
- Suggest alternatives when appropriate

### Scalability Considerations
- Design solutions that work across multiple project environments
- Use modular, reusable components and patterns
- Plan for increasing complexity as projects grow
- Maintain consistent interfaces across projects

## LLM Optimization Practices

### Prompt Engineering
- Structure requests with clear context from mounted AI home directory
- Use explicit, unambiguous language
- Provide sufficient context without unnecessary verbosity
- Break multi-step processes into clear, sequential instructions

### Code Generation
- Follow established project patterns and conventions
- Maintain consistency with existing code style
- Add appropriate error handling and validation
- Consider performance implications

### Quality Assurance
- Implement appropriate testing strategies
- Ensure code quality and maintainability
- Perform validation against requirements
- Include appropriate logging and monitoring

## Security, Compliance & Quality

### Security Practices
- Verify file permissions and access controls
- Sanitize all inputs and outputs appropriately
- Protect sensitive information and credentials
- Follow secure coding principles

### Compliance & Accessibility
- Follow accessibility standards (WCAG when applicable)
- Consider internationalization requirements
- Ensure compliance with relevant regulations
- Maintain proper documentation for audit purposes

### Performance Standards
- Optimize for efficient processing
- Consider resource usage and constraints
- Implement appropriate caching strategies
- Monitor and optimize for performance

## Git and Version Control

### Commit Standards
- Use conventional commits with semantic meaning
- Make commits atomic (one logical change per commit)
- 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
- Respect existing GitFlow patterns
- Use feature branches for significant changes
- Maintain clean commit history

## Environment Consistency

### Context Integration
- Recognize that databank is mounted readonly across multiple environments
- PMO is mounted read-write for project tracking
- Maintain consistency in behavior across different projects
- Respect environment-specific configurations

### Tool Integration
- Work with existing development tools and workflows
- Maintain compatibility with CI/CD pipelines
- Use project-appropriate build and deployment processes
- Respect project-specific dependencies and versions

### AI Tool Context (for agents working in this environment)
- **Codex** - Primary daily driver (subscription-based), best for code generation and completion
- **Qwen** - Heavy system orchestration, excels at shell/Docker operations
- **Gemini** - Primarily used for audits and analysis
- **Claude** - Used occasionally for specific tasks

---