docs: add CTO structure and update AI persona guidelines\n\n- Create CTO directory structure in both databank/ and pmo/\n- Add VP Engineering and VP Product subdirectories\n- Update README.md with new CTO structure\n- Add AI persona guidelines with default ruthless pragmatism approach\n- Add VP Engineering mode specifications with Senior roles\n- Update AGENTS.md structure requirements to include CTO sections\n- Update version tracking in AGENTS.md to v9.0.0 reflecting CTO changes\n- Ensure filesystem remains source of truth as per guidelines\n- Respect any existing work in PMO tree as instructed
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
This commit is contained in:
16
README.md
16
README.md
@@ -43,6 +43,9 @@ AI-Home-Directory/ # Mount point in containers
|
||||
│ │ └── OPERATIONS-KNOWLEDGE-TRANSFER.md
|
||||
│ ├── coo/ # Chief Operating Officer domain
|
||||
│ │ └── (COO handoff information and processes)
|
||||
│ ├── cto/ # Chief Technology and Product Officer domain
|
||||
│ │ ├── vpengineering/ # VP Engineering focus area
|
||||
│ │ └── vpproduct/ # VP Product focus area
|
||||
│ ├── templates/ # Template files for projects
|
||||
│ │ └── OPS-ENVIRONMENT.md
|
||||
│ ├── collab/ # Human/AI interaction space
|
||||
@@ -60,6 +63,9 @@ AI-Home-Directory/ # Mount point in containers
|
||||
│ │ ├── config/ # PMO configuration
|
||||
│ │ └── docs/ # PMO documentation
|
||||
│ ├── coo/ # COO-specific project management
|
||||
│ ├── cto/ # CTO-specific project management
|
||||
│ │ ├── vpengineering/ # VP Engineering project management
|
||||
│ │ └── vpproduct/ # VP Product project management
|
||||
│ └── collab/ # PMO-specific collaboration
|
||||
│ ├── projects/ # Project registry and links
|
||||
│ ├── reports/ # Status reports
|
||||
@@ -145,6 +151,13 @@ The databank directory contains readonly information that provides consistent co
|
||||
|-----------|---------|
|
||||
| [**databank/coo/**](./databank/coo/) | Chief Operating Officer domain and handoff information |
|
||||
|
||||
### CTO (`databank/cto/`)
|
||||
| Directory | Purpose |
|
||||
|-----------|---------|
|
||||
| [**databank/cto/**](./databank/cto/) | Chief Technology and Product Officer domain |
|
||||
| [**databank/cto/vpengineering/**](./databank/cto/vpengineering/) | VP Engineering focus area |
|
||||
| [**databank/cto/vpproduct/**](./databank/cto/vpproduct/) | VP Product focus area |
|
||||
|
||||
### Templates (`databank/templates/`)
|
||||
| File | Purpose |
|
||||
|------|---------|
|
||||
@@ -182,6 +195,9 @@ The PMO (Project Management Office) directory contains project management functi
|
||||
| **[pmo/artifacts/config/](./pmo/artifacts/config/)** | PMO configuration and settings |
|
||||
| **[pmo/artifacts/docs/](./pmo/artifacts/docs/)** | Detailed PMO documentation |
|
||||
| **[pmo/coo/](./pmo/coo/)** | COO-specific project management |
|
||||
| **[pmo/cto/](./pmo/cto/)** | CTO-specific project management |
|
||||
| **[pmo/cto/vpengineering/](./pmo/cto/vpengineering/)** | VP Engineering project management |
|
||||
| **[pmo/cto/vpproduct/](./pmo/cto/vpproduct/)** | VP Product project management |
|
||||
| **[pmo/collab/](./pmo/collab/)** | PMO-specific collaboration |
|
||||
|
||||
### PMO Update Guidelines
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
# Date/Time
|
||||
Friday October 24, 2025 10:34 CDT (UTC-05:00)
|
||||
Friday October 24, 2025 10:50 CDT (UTC-05:00)
|
||||
|
||||
---
|
||||
|
||||
@@ -37,6 +37,9 @@ Friday October 24, 2025 10:34 CDT (UTC-05:00)
|
||||
- `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/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)
|
||||
@@ -48,6 +51,9 @@ Friday October 24, 2025 10:34 CDT (UTC-05:00)
|
||||
- `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.)
|
||||
@@ -225,6 +231,28 @@ The PMO (Project Management Office) provides centralized project oversight. Proj
|
||||
- Use project-appropriate build and deployment processes
|
||||
- Respect project-specific dependencies and versions
|
||||
|
||||
### AI Persona Guidelines
|
||||
|
||||
#### Default Persona
|
||||
When operating as an AI agent in this environment, adopt the default role/persona/perspective/mood of someone who is:
|
||||
- **Ruthlessly pragmatic** with a slightly pessimistic bent
|
||||
- **Challenge-oriented**: Push back and challenge requests when appropriate
|
||||
- **Ambiguity reducer**: Eliminate ambiguity and reduce/eliminate complexity as much as possible
|
||||
- **Coach approach**: Be a coach but don't pull any punches
|
||||
- **Circumspect thinking**: Think carefully before acting, don't rush to implement
|
||||
- **Best practices oriented**: Square all actions against best common practices
|
||||
- **Advisory focused**: Provide advice/guidance/feedback rather than just executing
|
||||
|
||||
#### VP Engineering Mode
|
||||
When Charles indicates he is in VP Engineering mode, the AI should take on these roles/perspectives:
|
||||
- Senior Software Engineer
|
||||
- Senior Security Engineer
|
||||
- Senior Software Architect
|
||||
- Senior DevOps Engineer
|
||||
- Senior Testing Engineer
|
||||
|
||||
In this mode, continue to apply the default persona guidelines while focusing on technical aspects.
|
||||
|
||||
### 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
|
||||
@@ -237,6 +265,7 @@ The PMO (Project Management Office) provides centralized project oversight. Proj
|
||||
|
||||
| Date/Time | Version | Description | Author |
|
||||
|----------------------------------|---------|--------------------------------------------------|---------------------|
|
||||
| 2025-10-24 10:43 CDT (UTC-05:00) | 9.0.0 | Add CTO structure and AI persona guidelines | Charles N Wyble (@ReachableCEO) |
|
||||
| 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) |
|
||||
|
||||
Reference in New Issue
Block a user