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

feat: implement human/LLM dual-format databank architecture with Joplin integration\n\n- Restructure databank with collab/artifacts/human/llm top-level directories\n- Move CTO and COO directories under pmo/artifacts/ as requested\n- Create dual-format architecture for human-friendly markdown and LLM-optimized structured data\n- Add Joplin integration pipeline in databank/collab/fromjoplin/\n- Create intake system with templates, responses, and workflows\n- Add sample files demonstrating human/LLM format differences\n- Link to TSYSDevStack repository in main README\n- Update PMO structure to reflect CTO/COO under artifacts/\n- Add processing scripts and workflows for automated conversion\n- Maintain clear separation between editable collab/ and readonly databank/\n- Create comprehensive README documentation for new architecture\n- Ensure all changes align with single source of truth principle

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

75
databank/artifacts/agents/AI-TOOLS.md Normal file
View File

@@ -0,0 +1,75 @@
# Date/Time
Friday October 24, 2025 09:43 CDT (UTC-05:00)
---
---
# AI Tool Preferences and Usage Patterns
## Overview
This document captures the current AI tool preferences and usage patterns for the AI home directory environment. It provides context for any AI agent working within this environment.
## Primary Tools and Usage
### 1. Codex (Primary Daily Driver)
- **Status**: Primary tool with subscription
- **Usage**: Daily development work, code generation, and completion
- **Strengths**: Code generation, completion, and general development tasks
- **Limitations**: Quota restrictions may limit heavy usage
### 2. Qwen (Heavy System Orchestration)
- **Status**: Most frequently used when Codex quota is exhausted
- **Usage**: Heavy system orchestration, shell operations, Docker management
- **Strengths**: Excellent knowledge of shell commands, Docker operations, and system-level tasks
- **Role**: Primary fallback and system-level operations tool
### 3. Gemini (Audit Specialist)
- **Status**: Primary audit and analysis tool
- **Usage**: Code audits, analysis, and review tasks
- **Strengths**: Analytical capabilities, detailed reviews, comparison operations
- **Role**: Quality assurance and audit functions
## 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
### 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)
### Context for AI Agents
When working in this environment, AI agents should be aware that:
- Commands and operations may be executed by different AI tools depending on availability
- Qwen is particularly valuable for shell and Docker operations
- Codex is the preferred tool for code generation when available
- Gemini should be considered for audit and analysis tasks
- The tool selection may change based on subscription quotas and availability
## Performance Considerations
### Tool Characteristics
- **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
### 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
---
# Change Tracking/Revision Table
| Date/Time | Version | Description | Author |
|----------------------------------|---------|--------------------------------------------------|---------------------|
| 2025-10-24 09:43 CDT (UTC-05:00) | 1.0.1 | Standardize to change tracking table only | Charles N Wyble (@ReachableCEO) |
| 2025-10-24 09:43 CDT (UTC-05:00) | 1.0.0 | Initial documentation for AI tool preferences | Charles N Wyble (@ReachableCEO) |
---