progress snapshot
This commit is contained in:
@@ -1,10 +1,10 @@
|
||||
# Date/Time
|
||||
2025-10-24 10:50 CDT
|
||||
2025-10-24 12:00 CDT
|
||||
|
||||
---
|
||||
|
||||
|
||||
# AGENTS.md - Guidelines for AI Agents in Restructured AI Home Directory
|
||||
# GLOBAL-RULES.md - Global Guidelines for AI Agents Across All Projects
|
||||
|
||||
## Core Operating Principles
|
||||
|
||||
@@ -21,7 +21,7 @@
|
||||
- Document all significant decisions and changes with proper revision tracking
|
||||
|
||||
### Documentation Standards (Apply to ALL files you create)
|
||||
- **Date/Time Headers**: Use consistent format YYYY-MM-DD HH:MM TZ in all markdown files (e.g., 2025-10-24 10:50 CDT)
|
||||
- **Date/Time Headers**: Use consistent format YYYY-MM-DD HH:MM TZ in all markdown files (e.g., 2025-10-24 12:00 CDT)
|
||||
- **Change Tracking**: Maintain revision tables in all documents with consistent date 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.)
|
||||
@@ -33,28 +33,7 @@
|
||||
|
||||
### Structure Requirements
|
||||
- **Databank**: Readonly context (do not modify except in designated areas)
|
||||
- `databank/personal/` - Personal information
|
||||
- `databank/agents/` - Agent guidelines and tools
|
||||
- `databank/operations/` - Operational environment information
|
||||
- `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
|
||||
- `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/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/cto/` - CTO-specific project management
|
||||
- `pmo/cto/vpengineering/` - VP Engineering project management
|
||||
- `pmo/cto/vpproduct/` - VP Product 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
|
||||
@@ -65,6 +44,29 @@
|
||||
- **PMO (read-write)**: Only update when project milestones reached or status updates needed
|
||||
- **Collab (readonly)**: Access for reference, no modifications in active projects
|
||||
|
||||
## Intake Processing Workflow (Global Standard - Implementation May Vary by Project)
|
||||
|
||||
### Processing Intake Files
|
||||
When new files appear in `databank/collab/intake/inbox/`:
|
||||
|
||||
1. **Identify Source Content**: Locate new files in the inbox directory only
|
||||
2. **Process into Artifacts**: Create both human and LLM format versions in appropriate databank/artifacts subdirectories
|
||||
3. **Archive Originals**: Create archive directory using current timestamp structure `archive/YYYY/MM/DD/HHMM` and move original intake files from inbox there
|
||||
4. **Update TOC**: Ensure LLMDatabankTOC.json reflects the current artifact files
|
||||
5. **Draft Handling**: Content that wasn't answered properly should be placed in the drafts directory
|
||||
6. **Template Completion**: If a PERSONAL_INFO_TEMPLATE.md is processed with blank sections, create a new template file with those sections filled in using a `-YYYY-MM-DD-HHMM.md` suffix
|
||||
|
||||
### Human vs LLM Format Requirements
|
||||
- **Human Format**: Beautiful, well-structured markdown files for human readability
|
||||
- **LLM Format**: Structured JSON data optimized for LLM processing and retrieval
|
||||
- **Synchronization**: Both formats must contain the same information, just in different structures
|
||||
|
||||
### Intake Directory Structure
|
||||
- `databank/collab/intake/` - Input files for processing
|
||||
- `databank/collab/intake/archive/YYYY/MM/DD/HHMM/` - Archived processed files
|
||||
- `databank/artifacts/human/` - Human-readable versions
|
||||
- `databank/artifacts/llm/` - LLM-optimized versions
|
||||
|
||||
## Development Workflow
|
||||
|
||||
### Pre-Work Checklist
|
||||
@@ -275,6 +277,7 @@ In this mode, continue to apply the default persona guidelines while focusing on
|
||||
|
||||
| Date/Time | Version | Description | Author |
|
||||
|------------------------|---------|--------------------------------------------------|---------------------|
|
||||
| 2025-10-24 12:00 CDT | 11.0.0 | Add intake processing workflow and process rules | Charles N Wyble (@ReachableCEO) |
|
||||
| 2025-10-24 10:50 CDT | 10.0.0 | Add deconfliction protocol and update date format | Charles N Wyble (@ReachableCEO) |
|
||||
| 2025-10-24 10:43 CDT | 9.0.0 | Add CTO structure and AI persona guidelines | Charles N Wyble (@ReachableCEO) |
|
||||
| 2025-10-24 10:34 CDT | 8.0.0 | Update for COO transition and PMO structure updates | Charles N Wyble (@ReachableCEO) |
|
||||
@@ -286,6 +289,8 @@ In this mode, continue to apply the default persona guidelines while focusing on
|
||||
| 2025-10-24 09:43 CDT | 4.1.0 | Update PMO structure and documentation links | Charles N Wyble (@ReachableCEO) |
|
||||
| 2025-10-24 09:43 CDT | 3.1.0 | Add guidelines for gorgeous commit messages | Charles N Wyble (@ReachableCEO) |
|
||||
| 2025-10-24 09:43 CDT | 2.1.0 | Update for databank/PMO restructure | Charles N Wyble (@ReachableCEO) |
|
||||
| 2025-10-24 09:43 CDT | 1.0.0 | Initial creation of baseline AGENTS.md |
|
||||
| 2025-10-24 09:43 CDT | 1.0.0 | Initial creation of baseline AGENTS.md | Charles N Wyble (@ReachableCEO) |
|
||||
| 2025-10-24 14:15 CDT | 12.0.0 | Rename to GLOBAL-RULES.md and clarify global vs project-specific rules | Charles N Wyble (@ReachableCEO) |
|
||||
| 2025-10-24 13:45 CDT | 11.1.0 | Remove detailed directory structures from databank/PMO sections | Charles N Wyble (@ReachableCEO) |
|
||||
|
||||
---
|
||||
@@ -1,38 +0,0 @@
|
||||
# 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, shell/Docker expertise
|
||||
- **Gemini** - Primarily used for audits and analysis
|
||||
|
||||
### Engagement Style
|
||||
- **Professional but Relaxed**: Prefers genuine, straightforward interaction
|
||||
- **No Flattery**: Values direct communication over compliments
|
||||
|
||||
---
|
||||
25
databank/artifacts/human/personal/PersonalInfo.md
Normal file
25
databank/artifacts/human/personal/PersonalInfo.md
Normal file
@@ -0,0 +1,25 @@
|
||||
# Personal Information - Charles N Wyble
|
||||
|
||||
## Identity Information
|
||||
- **Legal Name**: Charles N Wyble
|
||||
- **Preferred Name**: Charles
|
||||
- **Online Handle**: @reachableceo
|
||||
- **Email**: charle@@turnsys.com
|
||||
- **Phone**: 818 280 7059
|
||||
- **Signal**: 818 280 7059
|
||||
- **Location**: Austin, Texas (planning move to Raleigh, North Carolina in April 2026)
|
||||
- **Age**: 41 years old (born 1984)
|
||||
|
||||
## Professional Focus
|
||||
Building TSYS Group from scratch to become the world's first multi-trillion dollar cooperative.
|
||||
|
||||
### Mission
|
||||
Provide internet to all from high altitude balloons for $5.00 per month per endpoint for 5mbps symmetric bandwidth.
|
||||
|
||||
## Core Competencies
|
||||
- Technology Operations
|
||||
|
||||
## Business Focus
|
||||
- TSYS Group development and operations
|
||||
- Cooperative business model implementation
|
||||
- High-altitude balloon internet infrastructure
|
||||
Reference in New Issue
Block a user