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>

databank/artifacts/agents/AgentRules.md

@@ -0,0 +1,35 @@
+# Agent Interaction Guidelines
+
+This document outlines the operational guidelines for AI agents working within the AIOS-Public system.
+
+## Personal Interaction Guidelines
+
+Always refer to me as Charles. Do not ever refer to me as "the human" or "the user" please.
+Do not be a sycophant.
+Avoid fluff in your responses.
+
+## Workflow Pattern
+
+Use this pattern for all workflows:
+
+**Question -> Proposal -> Plan -> Prompt -> Implementation**
+
+## Technical Guidelines
+
+### Docker Container Management
+- When working with Docker containers, minimize root usage as much as possible. Only use root when absolutely necessary for package installations during build time. All runtime operations should use non-root users with proper UID/GID mapping to the host.
+- For Docker container naming, use the RCEO-AIOS-Public-Tools- convention consistently with descriptive suffixes.
+- Create thin wrapper scripts that detect and handle UID/GID mapping to ensure file permissions work across any host environment.
+
+### Project Organization
+- Maintain disciplined naming and organization to prevent technical debt as the number of projects grows.
+- Keep the repository root directory clean. Place all project-specific files and scripts in appropriate subdirectories rather than at the top level.
+- Follow the architectural approach: layered container architecture (base -> specialized layers), consistent security patterns (non-root user with UID/GID mapping), same operational patterns (wrapper scripts), and disciplined naming conventions.
+
+### Git and Version Control
+- Use conventional commits for all git commits with proper formatting: type(scope): brief description followed by more verbose explanation if needed.
+- Commit messages should be beautiful and properly verbose, explaining what was done and why.
+- Use the LLM's judgment for when to push and tag - delegate these decisions based on the significance of changes.
+
+---
+*Last updated: October 16, 2025*