fix: correct databank architecture to match specification\n\n- Restructure databank/artifacts/ with only human/ and llm/ top-level directories\n- Remove all incorrectly placed domain directories from databank/artifacts/\n- Create proper LLMDatabankTOC.json for chat agent '@' function\n- Implement correct human/llm dual-format structure as specified\n- Remove scaffolding from databank as requested\n- Create proper PMO scaffolding in pmo/artifacts/scaffolding/ with domain templates\n- Update README documentation to reflect corrected architecture\n- Maintain clear separation: humans edit collab/, AI manages artifacts/\n- Ensure LLMDatabankTOC enables efficient navigation for chat agents\n- Correct repository structure diagram to show proper databank/artifacts/ structure\n- Remove all references to incorrectly placed directories\n- Maintain only collab/ as editable directory for humans
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
This commit is contained in:
161
databank/artifacts/llm/LLMDatabankTOC.json
Normal file
161
databank/artifacts/llm/LLMDatabankTOC.json
Normal file
@@ -0,0 +1,161 @@
|
||||
{
|
||||
"databank_toc": {
|
||||
"version": "1.0.0",
|
||||
"last_updated": "2025-10-24T12:00:00Z",
|
||||
"description": "Table of Contents for LLM-optimized databank content",
|
||||
"purpose": "Enable efficient navigation and retrieval of databank information by LLM agents",
|
||||
"usage": "Use @LLMDatabankTOC to access this file, then navigate to specific files as needed",
|
||||
"structure": {
|
||||
"organization": "Files organized by domain with both human and LLM formats available",
|
||||
"access_patterns": "LLM format prioritized for efficiency, human format for complex context"
|
||||
},
|
||||
"domains": {
|
||||
"personal": {
|
||||
"description": "Personal information and biography",
|
||||
"llm_files": [
|
||||
{
|
||||
"path": "personal/AboutMe.json",
|
||||
"purpose": "Structured personal information",
|
||||
"tags": ["identity", "professional", "preferences"]
|
||||
},
|
||||
{
|
||||
"path": "personal/TSYS.json",
|
||||
"purpose": "TSYS Group information",
|
||||
"tags": ["business", "organization", "entrepreneurship"]
|
||||
}
|
||||
],
|
||||
"human_files": [
|
||||
{
|
||||
"path": "personal/AboutMe.md",
|
||||
"purpose": "Beautiful personal information documentation",
|
||||
"tags": ["identity", "professional", "preferences"]
|
||||
},
|
||||
{
|
||||
"path": "personal/TSYS.md",
|
||||
"purpose": "TSYS Group documentation",
|
||||
"tags": ["business", "organization", "entrepreneurship"]
|
||||
}
|
||||
]
|
||||
},
|
||||
"agents": {
|
||||
"description": "AI agent guidelines and tools",
|
||||
"llm_files": [
|
||||
{
|
||||
"path": "agents/AGENTS.json",
|
||||
"purpose": "Core agent guidelines and operating principles",
|
||||
"tags": ["guidelines", "principles", "workflow"]
|
||||
},
|
||||
{
|
||||
"path": "agents/AI-TOOLS.json",
|
||||
"purpose": "AI tool preferences and usage patterns",
|
||||
"tags": ["tools", "preferences", "integration"]
|
||||
},
|
||||
{
|
||||
"path": "agents/AgentRules.json",
|
||||
"purpose": "Specific operational rules for agents",
|
||||
"tags": ["rules", "constraints", "boundaries"]
|
||||
}
|
||||
],
|
||||
"human_files": [
|
||||
{
|
||||
"path": "agents/AGENTS.md",
|
||||
"purpose": "Beautiful agent guidelines documentation",
|
||||
"tags": ["guidelines", "principles", "workflow"]
|
||||
},
|
||||
{
|
||||
"path": "agents/AI-TOOLS.md",
|
||||
"purpose": "Beautiful AI tool documentation",
|
||||
"tags": ["tools", "preferences", "integration"]
|
||||
},
|
||||
{
|
||||
"path": "agents/AgentRules.md",
|
||||
"purpose": "Beautiful agent rules documentation",
|
||||
"tags": ["rules", "constraints", "boundaries"]
|
||||
}
|
||||
]
|
||||
},
|
||||
"context": {
|
||||
"description": "General context information",
|
||||
"llm_files": [
|
||||
{
|
||||
"path": "context/AUDIT1.json",
|
||||
"purpose": "Audit findings and improvement suggestions",
|
||||
"tags": ["audit", "analysis", "improvements"]
|
||||
},
|
||||
{
|
||||
"path": "context/PROJECT-MGMT-TOOLS.json",
|
||||
"purpose": "Project management tool recommendations",
|
||||
"tags": ["tools", "project_management", "recommendations"]
|
||||
}
|
||||
],
|
||||
"human_files": [
|
||||
{
|
||||
"path": "context/AUDIT1.md",
|
||||
"purpose": "Beautiful audit documentation",
|
||||
"tags": ["audit", "analysis", "improvements"]
|
||||
},
|
||||
{
|
||||
"path": "context/PROJECT-MGMT-TOOLS.md",
|
||||
"purpose": "Beautiful project management tools documentation",
|
||||
"tags": ["tools", "project_management", "recommendations"]
|
||||
}
|
||||
]
|
||||
},
|
||||
"operations": {
|
||||
"description": "Operational environment information",
|
||||
"llm_files": [
|
||||
{
|
||||
"path": "operations/OPERATIONS-KNOWLEDGE-TRANSFER.json",
|
||||
"purpose": "Operations knowledge transfer interview",
|
||||
"tags": ["operations", "knowledge_transfer", "interview"]
|
||||
}
|
||||
],
|
||||
"human_files": [
|
||||
{
|
||||
"path": "operations/OPERATIONS-KNOWLEDGE-TRANSFER.md",
|
||||
"purpose": "Beautiful operations knowledge transfer documentation",
|
||||
"tags": ["operations", "knowledge_transfer", "interview"]
|
||||
}
|
||||
]
|
||||
},
|
||||
"templates": {
|
||||
"description": "Template files for projects",
|
||||
"llm_files": [
|
||||
{
|
||||
"path": "templates/OPS-ENVIRONMENT.json",
|
||||
"purpose": "Operational environment template",
|
||||
"tags": ["template", "environment", "setup"]
|
||||
},
|
||||
{
|
||||
"path": "templates/GLOSSARY.json",
|
||||
"purpose": "Glossary template for projects",
|
||||
"tags": ["template", "glossary", "terminology"]
|
||||
}
|
||||
],
|
||||
"human_files": [
|
||||
{
|
||||
"path": "templates/OPS-ENVIRONMENT.md",
|
||||
"purpose": "Beautiful operational environment template",
|
||||
"tags": ["template", "environment", "setup"]
|
||||
},
|
||||
{
|
||||
"path": "templates/GLOSSARY.md",
|
||||
"purpose": "Beautiful glossary template",
|
||||
"tags": ["template", "glossary", "terminology"]
|
||||
}
|
||||
]
|
||||
}
|
||||
},
|
||||
"navigation_instructions": {
|
||||
"step_1": "Identify the domain of interest from the domains list above",
|
||||
"step_2": "Choose appropriate format (llm_files for efficiency, human_files for context)",
|
||||
"step_3": "Access specific file using the provided path",
|
||||
"step_4": "For related information, check files with similar tags"
|
||||
},
|
||||
"update_policy": {
|
||||
"frequency": "Continuously updated based on collab/ communications",
|
||||
"process": "AI agents process collab/ updates and synchronize both formats",
|
||||
"validation": "Changes validated against collab/ source of truth"
|
||||
}
|
||||
}
|
||||
}
|
||||
53
databank/artifacts/llm/personal/AboutMe.json
Normal file
53
databank/artifacts/llm/personal/AboutMe.json
Normal file
@@ -0,0 +1,53 @@
|
||||
{
|
||||
"identity": {
|
||||
"full_name": "Charles N Wyble",
|
||||
"online_handle": "@ReachableCEO",
|
||||
"age": 41,
|
||||
"location": {
|
||||
"current": "Central Texas, USA",
|
||||
"relocating_to": "Raleigh, NC",
|
||||
"relocation_date": "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": {
|
||||
"type": "Solo Entrepreneur",
|
||||
"entities": "TSYS Group ecosystem",
|
||||
"description": "Creating an ecosystem of entities"
|
||||
},
|
||||
"ai_integration": {
|
||||
"workflow": "AI-centric, streamlining life using AI for all professional knowledge worker actions",
|
||||
"agent_agnosticism": "Uses multiple command line AI agents and maintains flexibility",
|
||||
"tools": [
|
||||
{
|
||||
"name": "Codex",
|
||||
"role": "Primary daily driver",
|
||||
"type": "subscription"
|
||||
},
|
||||
{
|
||||
"name": "Qwen",
|
||||
"role": "Heavy system orchestration",
|
||||
"expertise": "shell/Docker operations"
|
||||
},
|
||||
{
|
||||
"name": "Gemini",
|
||||
"role": "Audits and analysis",
|
||||
"usage": "primary"
|
||||
}
|
||||
]
|
||||
},
|
||||
"engagement_style": {
|
||||
"approach": "Professional but relaxed",
|
||||
"preference": "Genuine, straightforward interaction",
|
||||
"communication": "Direct communication over compliments"
|
||||
}
|
||||
}
|
||||
}
|
||||
Reference in New Issue
Block a user