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

Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
This commit is contained in:
2025-10-24 12:15:36 -05:00
parent 61919ae452
commit 919349aad2
34 changed files with 1154 additions and 14 deletions

View File

@@ -0,0 +1,117 @@
# AI Tools and Agent Preferences Intake Template
## Overview
This template guides the collection of AI tool preferences and agent interaction guidelines.
## Interview Structure
### 1. Current Tool Usage
- Primary tools and their roles
- Subscription status and limitations
- Usage patterns and workflows
- Strengths and limitations of each tool
- Quota management and availability strategies
- Backup and alternative tool selections
### 2. Agent Guidelines and Rules
- Core operating principles
- Communication protocols and expectations
- Documentation standards and formats
- Quality assurance and validation approaches
- Error handling and recovery procedures
- Security and privacy considerations
### 3. Workflow Preferences
- Preferred interaction styles
- Response length and detail expectations
- Formatting and presentation preferences
- Decision-making and approval processes
- Feedback and iteration approaches
- Collaboration and delegation patterns
### 4. Technical Environment
- Development environment preferences
- Tool integration and interoperability
- Version control and change management
- Testing and quality assurance practices
- Deployment and delivery mechanisms
- Monitoring and observability requirements
### 5. Performance Optimization
- Token efficiency strategies
- Context window management
- Response time expectations
- Resource utilization considerations
- Cost optimization approaches
- Scalability and reliability requirements
## Response Format
Please provide responses in the following structured format:
```yaml
tool_usage:
primary_tools:
- name: ""
role: ""
subscription_status: ""
usage_patterns: []
strengths: []
limitations: []
quota_management:
strategies: []
backup_selections: []
workflow_integration:
primary_flows: []
backup_flows: []
agent_guidelines:
core_principles: []
communication_protocols: []
documentation_standards: []
quality_assurance: []
error_handling: []
security_considerations: []
workflow_preferences:
interaction_styles: []
response_expectations:
length_preference: ""
detail_level: ""
formatting_preferences: []
decision_processes: []
feedback_approaches: []
collaboration_patterns: []
technical_environment:
development_preferences: []
tool_integration: []
version_control: []
testing_practices: []
deployment_mechanisms: []
monitoring_requirements: []
performance_optimization:
token_efficiency: []
context_management: []
response_time: []
resource_utilization: []
cost_optimization: []
scalability_requirements: []
```
## Validation Criteria
- Alignment with current tool subscriptions
- Consistency with documented workflows
- Practicality of implementation
- Completeness of coverage
- Clarity of expectations
## Frequency
This intake should be updated:
- Semi-annually for tool changes
- As-needed for workflow modifications
- Quarterly for performance optimization reviews

View File

@@ -0,0 +1,112 @@
# Operations and Project Management Intake Template
## Overview
This template guides the collection of operational procedures and project management approaches.
## Interview Structure
### 1. Operational Procedures
- Daily/weekly/monthly routines and rituals
- System administration and maintenance tasks
- Monitoring and alerting procedures
- Backup and recovery processes
- Security and compliance practices
- Documentation and knowledge management
### 2. Project Management Approaches
- Project initiation and planning methods
- Task tracking and progress monitoring
- Resource allocation and scheduling
- Risk management and contingency planning
- Communication and stakeholder management
- Quality assurance and delivery processes
### 3. Infrastructure and Tools
- Hosting platforms and deployment targets
- Development and testing environments
- Monitoring and observability tools
- Security and compliance tooling
- Collaboration and communication platforms
- Automation and orchestration systems
### 4. Knowledge Management
- Information organization and categorization
- Documentation standards and practices
- Knowledge sharing and dissemination
- Learning and improvement processes
- Archive and retention policies
- Search and discovery optimization
### 5. Continuous Improvement
- Retrospective and review processes
- Metric tracking and analysis
- Process refinement and optimization
- Technology evaluation and adoption
- Skill development and training
- Innovation and experimentation approaches
## Response Format
Please provide responses in the following structured format:
```yaml
operational_procedures:
routines:
daily: []
weekly: []
monthly: []
system_administration: []
monitoring_procedures: []
backup_recovery: []
security_practices: []
documentation_management: []
project_management:
initiation_planning: []
task_tracking: []
resource_allocation: []
risk_management: []
stakeholder_communication: []
quality_assurance: []
infrastructure_tools:
hosting_platforms: []
development_environments: []
monitoring_tools: []
security_tooling: []
collaboration_platforms: []
automation_systems: []
knowledge_management:
information_organization: []
documentation_practices: []
knowledge_sharing: []
learning_processes: []
archive_policies: []
search_optimization: []
continuous_improvement:
retrospective_processes: []
metric_tracking: []
process_refinement: []
technology_evaluation: []
skill_development: []
innovation_approaches: []
```
## Validation Criteria
- Alignment with current operational reality
- Completeness of key operational areas
- Practicality of implementation
- Consistency with documented procedures
- Relevance to current projects and initiatives
## Frequency
This intake should be updated:
- Quarterly for operational reviews
- As-needed for procedure changes
- Semi-annually for infrastructure updates
- Annually for comprehensive process reviews

View File

@@ -0,0 +1,128 @@
# Personal Information Intake Template
## Overview
This template guides the collection of personal information for databank population.
## Interview Structure
### 1. Basic Identity
- Full legal name
- Preferred name/nickname
- Online handles and professional identities
- Contact preferences and methods
- Geographic location (current and planned moves)
- Age/birth year
### 2. Professional Background
- Career timeline and key positions
- Core competencies and specializations
- Industry experience and expertise areas
- Professional certifications and qualifications
- Notable achievements and recognitions
- Current professional focus and goals
### 3. Philosophical Positions
- Core values and beliefs
- Political affiliations and civic positions
- Ethical frameworks and guiding principles
- Approach to work and collaboration
- Views on technology and AI integration
- Stance on data privacy and sovereignty
### 4. Technical Preferences
- Preferred tools and platforms
- Technology stack and environment
- AI tool usage patterns and preferences
- Development methodologies and practices
- Security and privacy practices
- Automation and efficiency approaches
### 5. Lifestyle and Context
- Daily schedule and work patterns
- Communication preferences and style
- Collaboration approaches and expectations
- Work-life balance priorities
- Ongoing projects and initiatives
- Future plans and aspirations
### 6. Relationships and Networks
- Key professional relationships
- Organizational affiliations
- Community involvement
- Mentorship and advisory roles
- Partnership and collaboration patterns
## Response Format
Please provide responses in the following structured format:
```yaml
identity:
legal_name: ""
preferred_name: ""
handles:
- platform: ""
handle: ""
contact_preferences:
- method: ""
preference: "" # high/medium/low
location:
current: ""
planned_moves: []
birth_year: 0
professional_background:
career_timeline: []
core_competencies: []
industry_experience: []
certifications: []
achievements: []
current_focus: ""
philosophical_positions:
core_values: []
political_affiliations: []
ethical_frameworks: []
approach_to_work: ""
ai_integration_views: ""
data_privacy_stances: []
technical_preferences:
preferred_tools: []
technology_stack: []
ai_tool_patterns: []
development_methods: []
security_practices: []
automation_approaches: []
lifestyle_context:
daily_schedule: ""
communication_preferences: ""
collaboration_approach: ""
work_life_balance: ""
ongoing_projects: []
future_plans: []
relationships_networks:
key_relationships: []
organizational_affiliations: []
community_involvement: []
mentorship_roles: []
collaboration_patterns: []
```
## Validation Criteria
- Completeness of all sections
- Consistency with existing databank information
- Plausibility and internal coherence
- Relevance to professional and technical context
- Sufficient detail for AI agent understanding
## Frequency
This intake should be updated:
- Annually for major life changes
- Quarterly for ongoing project updates
- As-needed for significant changes in circumstances