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

docs: improve documentation formatting and remove Claude references\n\n- Format AboutMe.md with beautiful tables and improved structure\n- Remove all Claude references from documentation per ethical/legal concerns\n- Create README.md files in all top-level and sub-level directories\n- Update README.md to link to README.md files instead of directories\n- Add beautiful stub README.md files for COO, CTO, and PMO directories\n- Fix directory linking issues in main README.md\n- Ensure all links point to actual files rather than directories\n- Update version tracking in AboutMe.md to v1.0.1 reflecting improvements\n- Maintain consistency with filesystem structure and documentation standards\n- Preserve AI tools: Codex, Qwen, Gemini while removing Claude references

Browse Source 
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
This commit is contained in:
Charles N Wyble - admin
2025-10-24 11:36:12 -05:00
parent 1975090056
commit 61919ae452
23 changed files with 355 additions and 55 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
databank/agents/AGENTS.md
View File

@@ -36,8 +36,8 @@
- `databank/personal/` - Personal information
- `databank/agents/` - Agent guidelines and tools
- `databank/operations/` - Operational environment information
- `databank/coo/` - Chief Operating Officer domain (for Albert and his AI agents)
- `databank/cto/` - Chief Technology and Product Officer domain
- `databank/coo/` - Chief Operating Officer domain (shared between Charles and Albert, transitioning to Albert in January 2026)
- `databank/cto/` - Chief Technology and Product Officer (CTPO) domain
- `databank/cto/vpengineering/` - VP Engineering focus area (AI-based operations)
- `databank/cto/vpproduct/` - VP Product focus area (AI-based operations)
- `databank/templates/` - Template files for projects
@@ -217,7 +217,8 @@ The PMO (Project Management Office) provides centralized project oversight. Proj
### Authority and Decision Making
- 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
- Charles N Wyble (@ReachableCEO) serves as Chief Technology and Product Officer (CTPO)
- Charles N Wyble (@ReachableCEO) and Albert currently share the Chief Operating Officer (COO) role, with Albert taking over the COO role fully in January 2026
- 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 or Albert modify filesystem manually (vs having AI do it), they will ensure AI integrates the changes into mental model
@@ -267,7 +268,6 @@ In this mode, continue to apply the default persona guidelines while focusing on
- **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
---

10
databank/agents/AI-TOOLS.md
View File

@@ -31,25 +31,17 @@ This document captures the current AI tool preferences and usage patterns for th
- **Strengths**: Analytical capabilities, detailed reviews, comparison operations
- **Role**: Quality assurance and audit functions
### 4. Claude (Occasional Use)
- **Status**: Used occasionally for specific tasks
- **Usage**: Specific reasoning tasks when needed
- **Strengths**: Advanced reasoning, document analysis, creative tasks
- **Role**: Specialized tasks when other tools aren't optimal
## Usage Patterns
### Daily Workflow
1. **Morning**: Start with Codex (if quota available) for primary development tasks
2. **Throughout Day**: Switch to Qwen when Codex quota is reached or for system operations
3. **Review/Audit**: Use Gemini for detailed analysis and code reviews
4. **Special Tasks**: Use Claude for specific reasoning requirements
### Tool Selection Guidelines
- **Code Generation/Completion**: Codex (primary), Qwen (when Codex unavailable)
- **System Orchestration**: Qwen (primary), Codex (secondary)
- **Audits and Reviews**: Gemini (primary), others (as needed)
- **Advanced Reasoning**: Claude (primary for complex reasoning), others (as needed)
### Context for AI Agents
When working in this environment, AI agents should be aware that:
@@ -65,13 +57,11 @@ When working in this environment, AI agents should be aware that:
- **Codex**: Excellent for code generation but limited by subscription quota
- **Qwen**: Reliable for system operations, good for heavy tasks, no quota limits
- **Gemini**: Best for analytical tasks and detailed reviews
- **Claude**: Good for complex reasoning but used selectively
### Optimizing Tool Usage
- Leverage Qwen for operations that require extensive system knowledge
- Use Codex for code-related tasks when available
- Employ Gemini for validation and quality checks
- Reserve Claude for specialized reasoning tasks
---

1
databank/collab/PROPOSAL-AGENTS-v2.md
View File

@@ -204,7 +204,6 @@ This file proposes an updated comprehensive baseline AGENTS.md file that reflect
- **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
---

17
databank/coo/README.md Normal file
View File

@@ -0,0 +1,17 @@
# COO Directory
This directory contains Chief Operating Officer domain information and handoff processes.
## Structure
```
coo/
├── README.md # This file
└── (future files) # COO handoff information and processes
```
## Purpose
This directory serves as the domain for the Chief Operating Officer (COO) role, currently shared between Charles N Wyble (@ReachableCEO) and Albert, with Albert taking over the COO role fully in January 2026.
---

18
databank/cto/README.md Normal file
View File

@@ -0,0 +1,18 @@
# CTPO Directory
This directory contains Chief Technology and Product Officer (CTPO) domain information.
## Structure
```
cto/
├── README.md # This file
├── vpengineering/ # VP Engineering focus area
└── vpproduct/ # VP Product focus area
```
## Purpose
This directory serves as the domain for Charles N Wyble (@ReachableCEO), Chief Technology and Product Officer (CTPO), separating technology and product responsibilities.
---

17
databank/cto/vpengineering/README.md Normal file
View File

@@ -0,0 +1,17 @@
# VP Engineering Directory
This directory contains VP Engineering focus area information.
## Structure
```
vpengineering/
├── README.md # This file
└── (future files) # Engineering-specific content
```
## Purpose
This directory focuses on the engineering aspects of the CTO role, including software development, security, architecture, DevOps, and testing.
---

17
databank/cto/vpproduct/README.md Normal file
View File

@@ -0,0 +1,17 @@
# VP Product Directory
This directory contains VP Product focus area information.
## Structure
```
vpproduct/
├── README.md # This file
└── (future files) # Product-specific content
```
## Purpose
This directory focuses on the product aspects of the CTO role, including product management, market analysis, and customer requirements.
---

14
databank/operations/OPERATIONS-KNOWLEDGE-TRANSFER.md
View File

@@ -9,7 +9,7 @@ Friday October 24, 2025 09:43 CDT (UTC-05:00)
## Knowledge Transfer Interview: Operational Environment Information
This document serves as a structured interview guide to capture your extensive operational knowledge from your tenure as Chief Operating Officer and Vice President Technical Operations, as you transition to Chief Technology and Product Officer.
This document serves as a structured interview guide to capture your extensive operational knowledge from your tenure as Chief Operating Officer and Vice President Technical Operations. You now serve as Chief Technology and Product Officer (CTPO) with Albert. Charles N Wyble (@ReachableCEO) and Albert currently share the Chief Operating Officer (COO) role, with Albert taking over the COO role fully in January 2026.
### Instructions
- Complete this interview periodically to capture evolving operational knowledge
@@ -159,12 +159,12 @@ This document serves as a structured interview guide to capture your extensive o
- What operational institutional knowledge would be lost if not documented?
- What operational patterns and behaviors have you observed over time?
### 8.2 Succession Planning
- Who will assume these operational responsibilities?
- What training materials do they need?
- What operational processes need to be transferred?
- What operational relationships need to be transitioned?
- What operational authority and decision-making rights are changing?
### 8.2 Current Role Structure
- What operational responsibilities are currently shared between Charles and Albert in the COO role?
- What training materials are being used during the transition period?
- What operational processes are currently shared between Charles and Albert?
- What operational relationships are being managed during the shared COO period?
- What operational authority and decision-making rights are transitioning to Albert by January 2026?
## Section 9: Integration with Product and Technology

2
databank/operations/README.md
View File

@@ -1,6 +1,6 @@
# Operations Directory
This directory contains operational environment information and knowledge from my tenure as Chief Operating Officer and Vice President Technical Operations, as I transition to Chief Technology and Product Officer.
This directory contains operational environment information and knowledge from my tenure as Chief Operating Officer and Vice President Technical Operations. I now serve as Chief Technology and Product Officer (CTPO) with Albert. Charles N Wyble (@ReachableCEO) and Albert currently share the Chief Operating Officer (COO) role, with Albert taking over the COO role fully in January 2026.
## Contents

58
databank/personal/AboutMe.md
View File

@@ -1,15 +1,47 @@
My full name is Charles N Wyble. I use the online handle @ReachableCEO.
I am a strong believer in digital data sovereignty. I am a firm practitioner of self hosting (using Cloudron on a netcup VPS and soon Coolify on another Cloudron VPS).
I am 41 years old.
I am a Democrat and believe strongly in the rule of law and separation of powers.
I actively avoid the media.
I am a solo entrepreneur creating an ecosystem of entities called TSYS Group. (Please see TSYS.md for more on that)
My professional background is in production technical operations since 2002.
I use many command line AI agents (Codex, Coder, Qwen, Gemini) and wish to remain agent agnostic at all times.
I am located in the United States of America. As of October 2025 I am located in central Texas.
I will be relocating to Raleigh North Carolina in April 2026.
I want to streamline my life using AI and relying on it for all aspects of my professional, knowledge worker actions.
I prefer relaxed but professional engagement and don't want to be flattered.
# About Me
## Personal Information
| Attribute | Details |
|-----------|---------|
| **Full Name** | Charles N Wyble |
| **Online Handle** | @ReachableCEO |
| **Age** | 41 |
| **Location** | Central Texas, USA (relocating to Raleigh, NC in April 2026) |
| **Political Affiliation** | Democrat |
| **Professional Background** | Production technical operations since 2002 |
## Philosophy & Values
- **Digital Data Sovereignty**: Strong believer in controlling personal and professional data
- **Self Hosting**: Active practitioner using Cloudron on netcup VPS with plans to expand to Coolify
- **Rule of Law**: Believes strongly in legal frameworks and separation of powers
- **Media Avoidance**: Actively avoids mainstream media consumption
## Professional Focus
### Entrepreneurship
- **Solo Entrepreneur** creating an ecosystem of entities called TSYS Group
- **See Also**: [TSYS.md](./TSYS.md) for more information on the group structure
### AI Integration
- **AI-Centric Workflow**: Streamlining life using AI for all professional knowledge worker actions
- **Agent Agnosticism**: Uses multiple command line AI agents and maintains flexibility:
- **Codex** - Primary daily driver (subscription-based)
- **Qwen** - Heavy system orchestration and Docker operations
- **Gemini** - Audits and analysis
- **Coder** - Code completion and generation
### Engagement Style
- **Professional but Relaxed**: Prefers genuine, straightforward interaction
- **No Flattery**: Values direct communication over compliments
---
*Last updated: October 16, 2025*
## Change Tracking/Revision Table
| Date/Time | Version | Description | Author |
|----------------------|---------|--------------------------------------------------|---------------------|
| 2025-10-24 11:45 CDT | 1.0.1 | Format document with beautiful tables | Charles N Wyble (@ReachableCEO) |
| 2025-10-16 00:00 CDT | 1.0.0 | Initial version | Charles N Wyble (@ReachableCEO) |
---