fix: correct databank architecture and implement proper CTO/COO structure\n\n- Remove incorrectly placed human/llm directories from databank root\n- Restructure databank with everything under databank/artifacts/ as requested\n- Implement proper CTO/COO structure under pmo/artifacts/ with complete PMO components\n- Create comprehensive collab/ directory structure for human/AI communication\n- Remove Joplin processing scripts and references as requested\n- Create proper scaffolding directories for quick domain standup\n- Update README documentation to reflect corrected architecture\n- Ensure only collab/ directories are editable by humans\n- AI agents manage databank/artifacts/ based on collab/ communications\n- Create structured intake templates and collaboration workflows\n- Maintain clear separation between readonly databank and read-write PMO\n- Implement proper single source of truth with AI-managed artifacts
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
This commit is contained in:
@@ -1,12 +1,40 @@
|
||||
# Databank Artifacts Directory
|
||||
# Databank Artifacts
|
||||
|
||||
This directory is fully managed by AI agents as they see fit for storing various artifacts.
|
||||
This directory contains all databank artifacts in their canonical form. Files in this directory are:
|
||||
|
||||
- Managed by AI agents based on communications in `../collab/`
|
||||
- Organized by domain for efficient access
|
||||
- Maintained as single source of truth for all context
|
||||
- Updated only through AI processing of collab communications
|
||||
|
||||
## Structure
|
||||
|
||||
```
|
||||
artifacts/
|
||||
├── personal/ # Personal information and biography
|
||||
├── agents/ # AI agent guidelines and tools
|
||||
├── context/ # General context information
|
||||
├── operations/ # Operational environment information
|
||||
├── templates/ # Template files for new content
|
||||
├── scaffolding/ # Template structure for new domains
|
||||
├── coo/ # Chief Operating Officer domain
|
||||
├── cto/ # Chief Technology and Product Officer domain
|
||||
└── README.md # This file
|
||||
```
|
||||
|
||||
## Purpose
|
||||
|
||||
- AI-managed documentation ([docs/](./docs/))
|
||||
- AI-managed code artifacts ([code/](./code/))
|
||||
- AI-managed configuration ([config/](./config/))
|
||||
- AI-managed templates ([templates/](./templates/))
|
||||
Files in this directory represent the authoritative versions of all databank content. They are:
|
||||
|
||||
The AI has complete control over this directory and can organize, create, modify, and delete content as needed to support various functions and operations.
|
||||
- Updated only by AI agents processing `../collab/` communications
|
||||
- Never edited directly by humans
|
||||
- Maintained as single source of truth
|
||||
- Organized for efficient AI access patterns
|
||||
|
||||
## Relationship to Other Directories
|
||||
|
||||
- **`../collab/`** - Human/AI communication space (input)
|
||||
- **This directory** - Canonical content storage (storage)
|
||||
- **`../../../pmo/artifacts/`** - Project management updates (output)
|
||||
|
||||
---
|
||||
53
databank/artifacts/scaffolding/README.md
Normal file
53
databank/artifacts/scaffolding/README.md
Normal file
@@ -0,0 +1,53 @@
|
||||
# Scaffolding Templates
|
||||
|
||||
This directory contains templates for quickly standing up new domains in the databank.
|
||||
|
||||
## Structure
|
||||
|
||||
```
|
||||
scaffolding/
|
||||
├── domain-template/ # Template for new domains
|
||||
│ ├── README.md # Domain overview and purpose
|
||||
│ ├── context/ # Context information for this domain
|
||||
│ │ └── overview.md # Overview of domain context
|
||||
│ ├── operations/ # Operational information
|
||||
│ │ └── procedures.md # Standard operating procedures
|
||||
│ ├── personnel/ # Personnel and roles
|
||||
│ │ └── roles.md # Role definitions and responsibilities
|
||||
│ ├── tools/ # Tools and technology
|
||||
│ │ └── stack.md # Technology stack and tools
|
||||
│ └── artifacts/ # Domain-specific artifacts
|
||||
│ └── samples/ # Sample artifacts for reference
|
||||
└── README.md # This file
|
||||
```
|
||||
|
||||
## Purpose
|
||||
|
||||
The scaffolding directory provides templates for quickly creating new domains when needed. To create a new domain:
|
||||
|
||||
1. Copy the `domain-template/` directory to a new domain name
|
||||
2. Customize the README.md with domain-specific information
|
||||
3. Fill in context, operations, personnel, and tools information
|
||||
4. Add domain-specific artifacts as needed
|
||||
|
||||
## Usage
|
||||
|
||||
To create a new domain called "marketing":
|
||||
|
||||
```bash
|
||||
cp -r domain-template/ ../marketing/
|
||||
cd ../marketing/
|
||||
# Edit README.md to describe marketing domain
|
||||
# Customize other files as appropriate
|
||||
```
|
||||
|
||||
## Templates
|
||||
|
||||
Each template provides a starting point for new domains with:
|
||||
|
||||
- Standard directory structure
|
||||
- Placeholder content for customization
|
||||
- Consistent formatting and organization
|
||||
- Cross-domain linking patterns
|
||||
|
||||
---
|
||||
35
databank/artifacts/scaffolding/domain-template/README.md
Normal file
35
databank/artifacts/scaffolding/domain-template/README.md
Normal file
@@ -0,0 +1,35 @@
|
||||
# Domain Template
|
||||
|
||||
This is a template for creating new domains in the databank.
|
||||
|
||||
## Purpose
|
||||
|
||||
This template provides the standard structure for all domains in the databank.
|
||||
|
||||
## Structure
|
||||
|
||||
```
|
||||
domain-template/
|
||||
├── README.md # Domain overview and purpose
|
||||
├── context/ # Context information for this domain
|
||||
│ └── overview.md # Overview of domain context
|
||||
├── operations/ # Operational information
|
||||
│ └── procedures.md # Standard operating procedures
|
||||
├── personnel/ # Personnel and roles
|
||||
│ └── roles.md # Role definitions and responsibilities
|
||||
├── tools/ # Tools and technology
|
||||
│ └── stack.md # Technology stack and tools
|
||||
└── artifacts/ # Domain-specific artifacts
|
||||
└── samples/ # Sample artifacts for reference
|
||||
```
|
||||
|
||||
## Customization
|
||||
|
||||
To customize this template for a specific domain:
|
||||
|
||||
1. Rename the directory to the domain name
|
||||
2. Update README.md with domain-specific information
|
||||
3. Customize context, operations, personnel, and tools information
|
||||
4. Add domain-specific artifacts as needed
|
||||
|
||||
---
|
||||
@@ -0,0 +1,21 @@
|
||||
# Sample Artifacts
|
||||
|
||||
This directory contains sample artifacts for reference when creating domain-specific content.
|
||||
|
||||
## Purpose
|
||||
|
||||
Provide examples of the types of artifacts typically created in this domain.
|
||||
|
||||
## Types of Artifacts
|
||||
|
||||
List common artifact types for this domain.
|
||||
|
||||
## Templates
|
||||
|
||||
Provide templates for common artifacts.
|
||||
|
||||
## Examples
|
||||
|
||||
Include examples of completed artifacts.
|
||||
|
||||
---
|
||||
@@ -0,0 +1,21 @@
|
||||
# Domain Context Overview
|
||||
|
||||
This file provides an overview of the domain context.
|
||||
|
||||
## Purpose
|
||||
|
||||
Describe the purpose and scope of this domain.
|
||||
|
||||
## Scope
|
||||
|
||||
Define what is included and excluded from this domain.
|
||||
|
||||
## Relationships
|
||||
|
||||
Describe how this domain relates to other domains in the organization.
|
||||
|
||||
## Key Concepts
|
||||
|
||||
List key concepts and terminology specific to this domain.
|
||||
|
||||
---
|
||||
@@ -0,0 +1,25 @@
|
||||
# Standard Operating Procedures
|
||||
|
||||
This file describes the standard operating procedures for this domain.
|
||||
|
||||
## Daily Procedures
|
||||
|
||||
Describe daily procedures and routines.
|
||||
|
||||
## Weekly Procedures
|
||||
|
||||
Describe weekly procedures and reviews.
|
||||
|
||||
## Monthly Procedures
|
||||
|
||||
Describe monthly procedures and reporting.
|
||||
|
||||
## Quarterly Procedures
|
||||
|
||||
Describe quarterly procedures and planning.
|
||||
|
||||
## Annual Procedures
|
||||
|
||||
Describe annual procedures and reviews.
|
||||
|
||||
---
|
||||
@@ -0,0 +1,25 @@
|
||||
# Role Definitions and Responsibilities
|
||||
|
||||
This file defines roles and responsibilities within this domain.
|
||||
|
||||
## Key Roles
|
||||
|
||||
List key roles within this domain.
|
||||
|
||||
## Role Descriptions
|
||||
|
||||
Provide detailed descriptions of each role.
|
||||
|
||||
## Responsibilities
|
||||
|
||||
Define specific responsibilities for each role.
|
||||
|
||||
## Authority
|
||||
|
||||
Describe the authority levels for each role.
|
||||
|
||||
## Reporting Structure
|
||||
|
||||
Define the reporting structure and relationships.
|
||||
|
||||
---
|
||||
@@ -0,0 +1,25 @@
|
||||
# Technology Stack and Tools
|
||||
|
||||
This file describes the technology stack and tools used in this domain.
|
||||
|
||||
## Primary Tools
|
||||
|
||||
List primary tools and platforms.
|
||||
|
||||
## Supporting Tools
|
||||
|
||||
List supporting tools and utilities.
|
||||
|
||||
## Integration Points
|
||||
|
||||
Describe integration points with other systems.
|
||||
|
||||
## Security Considerations
|
||||
|
||||
List security considerations for tools and platforms.
|
||||
|
||||
## Access Requirements
|
||||
|
||||
Describe access requirements and permissions.
|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user