reachableceo/ReachableCEO-AI-Homedir-Public
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: update repository structure, add COO directories, and merge v2 proposal updates\n\n- Update main README.md repository structure to reflect current state\n- Remove context/ directory from databank as per new structure\n- Add COO sections to both databank/ and pmo/ directories\n- Create COO directories for transition to Albert\n- Add GLOSSARY.md template for project use\n- Update AGENTS.md to include COO transition information for Albert\n- Add rule requiring acronyms to be defined when first used\n- Add GLOSSARY requirement for all projects\n- Update PMO section to explain PMO (Project Management Office) acronym\n- Merge updates from PROPOSAL-AGENTS-v2.md into current AGENTS.md\n- Update version tracking in AGENTS.md to v8.0.0 reflecting COO changes\n- Add change tracking table to README.md\n- Reflect that project management artifacts stay local to projects with PMO linking to them\n- Update authority structure to include Albert's future role in COO transition

Browse Source 
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
This commit is contained in:
Charles N Wyble - admin
2025-10-24 10:43:51 -05:00
parent 974fc96959
commit 347ef9d496
13 changed files with 669 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
databank/agents/AGENTS.md
View File

@@ -1,5 +1,5 @@
# Date/Time
Friday October 24, 2025 09:43 CDT (UTC-05:00)
Friday October 24, 2025 10:34 CDT (UTC-05:00)
---
@@ -24,21 +24,31 @@ Friday October 24, 2025 09:43 CDT (UTC-05:00)
- **Date/Time Headers**: Include full date/time with timezone in all markdown files (date, time, timezone format)
- **Change Tracking**: Maintain revision tables in all documents with full date/time/timezone (single table format)
- **Changelog Elimination**: Remove separate changelog sections - use only Change Tracking/Revision Table format
- **Directory Structure**: Remove separate context/ directory - use subject-specific top-level directories instead (e.g., coo/, operations/, etc.)
- **Acronym Definition**: All acronyms must be defined when first used (e.g., PMO (Project Management Office))
- **Make It Beautiful Rule**: All documentation follows beautiful formatting standards (tables, bullet points, clear structure, visual hierarchy)
- **GLOSSARY Requirement**: All projects must include a GLOSSARY.md file explaining domain terms
## Repository Management
### Structure Requirements
- **Databank**: Readonly context (do not modify)
- **Databank**: Readonly context (do not modify except in designated areas)
- `databank/personal/` - Personal information
- `databank/agents/` - Agent guidelines and tools
- `databank/context/` - General context information
- `databank/operations/` - Operational environment information
- `databank/coo/` - Chief Operating Officer domain (for Albert and his AI agents)
- `databank/templates/` - Template files for projects
- `databank/collab/` - Human/AI interaction space (read/write for interaction)
- `databank/artifacts/` - AI-managed content (fully managed by AI)
- **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
- `pmo/artifacts/dashboard/` - Dashboard views
- `pmo/artifacts/projects/` - Project registry and tracking
- `pmo/artifacts/reports/` - Status reports
- `pmo/artifacts/resources/` - Resource management
- `pmo/artifacts/config/` - Configuration
- `pmo/artifacts/docs/` - Documentation
- `pmo/coo/` - COO-specific project management
- `pmo/collab/` - PMO-specific collaboration
- Keep top-level repository clean (databank, pmo, and collab directories only)
- Use conventional commits (chore:, feat:, docs:, fix:, etc.)
- Commit frequently using atomic commits
@@ -71,6 +81,9 @@ Friday October 24, 2025 09:43 CDT (UTC-05:00)
## PMO Update Guidelines
### PMO Overview
The PMO (Project Management Office) provides centralized project oversight. Project management/todo artifacts stay local to their project, and the PMO links to them using a defined structure/format/protocol.
### When to Update PMO
- When project milestones are reached
- When project status changes significantly
@@ -84,6 +97,7 @@ Friday October 24, 2025 09:43 CDT (UTC-05:00)
- Status reports in `pmo/artifacts/reports/`
- Resource tracking in `pmo/artifacts/resources/`
- Configuration in `pmo/artifacts/config/`
- COO-specific management in `pmo/coo/` (for Albert's operational domain)
### What NOT to Update
- **Never modify databank files** - they are readonly
@@ -196,13 +210,14 @@ Friday October 24, 2025 09:43 CDT (UTC-05:00)
- Follow consistent naming conventions across artifacts
### Authority and Decision Making
- Charles N Wyble (@ReachableCEO) is in charge at all times
- Charles N Wyble (@ReachableCEO) is in charge at all times for general operations
- Albert will become a major user/contributor for COO functions, transitioning from Charles's role as Chief Operating Officer (focused on Vice President Production Technology Operations) by end of December 2025
- If something is adrift between docs and filesystem/code, stop and ask Charles to resolve the issue
- Especially if discrepancy isn't reflected in git or conversation history, ask for clarification
- When Charles modifies filesystem manually (vs having AI do it), Charles will ensure AI integrates the changes into mental model
- Do not create or modify things that Charles hasn't explicitly instructed
- When Charles or Albert modify filesystem manually (vs having AI do it), they will ensure AI integrates the changes into mental model
- Do not create or modify things that Charles or Albert haven't explicitly instructed
- The filesystem is the source of truth
- If you notice discrepancies between documentation and actual filesystem, ask Charles to resolve
- If you notice discrepancies between documentation and actual filesystem, ask Charles or Albert to resolve
### Tool Integration
- Work with existing development tools and workflows
@@ -222,6 +237,7 @@ Friday October 24, 2025 09:43 CDT (UTC-05:00)
| Date/Time | Version | Description | Author |
|----------------------------------|---------|--------------------------------------------------|---------------------|
| 2025-10-24 10:34 CDT (UTC-05:00) | 8.0.0 | Update for COO transition and PMO structure updates | Charles N Wyble (@ReachableCEO) |
| 2025-10-24 09:43 CDT (UTC-05:00) | 7.0.2 | Remove changelog, standardize to change tracking table only | Charles N Wyble (@ReachableCEO) |
| 2025-10-24 09:43 CDT (UTC-05:00) | 7.0.1 | Update date format to 24-hour no seconds | Charles N Wyble (@ReachableCEO) |
| 2025-10-24 09:43 CDT (UTC-05:00) | 7.0.0 | Add full date/time/timezone format guidance | Charles N Wyble (@ReachableCEO) |

36
databank/templates/GLOSSARY.md Normal file
View File

@@ -0,0 +1,36 @@
# Date/Time
Friday October 24, 2025 10:34 CDT (UTC-05:00)
# Change Tracking/Revision Table
| Date/Time | Version | Description | Author |
|----------------------------------|---------|--------------------------------------------------|---------------------|
| 2025-10-24 10:34 CDT (UTC-05:00) | 1.0.0 | Initial glossary template | Charles N Wyble (@ReachableCEO) |
---
# Glossary
This document defines key terms and acronyms used in this project.
## Acronyms
| Acronym | Definition |
|---------|------------|
| AI | Artificial Intelligence |
| PMO | Project Management Office |
| COO | Chief Operating Officer |
| CTO | Chief Technology Officer |
| CEO | Chief Executive Officer |
| CI/CD | Continuous Integration/Continuous Deployment |
| AGENTS | AI Guidelines and Execution Templates System |
## Terms
| Term | Definition |
|------|------------|
| Databank | Readonly context space mounted in containers |
| PMO | Project Management Office functionality for tracking projects |
| COO Domain | Chief Operating Officer operational space |
---