Add organized Docker container structure with disciplined naming

- Create layered container architecture: Base, Light, Full, Computational
- Implement non-root user management with UID/GID mapping
- Add Markwhen timeline tool to documentation stack
- Create wrapper scripts for environment variable handling
- Update documentation across all containers
- Establish naming convention using RCEO-AIOS-Public-Tools- prefix
- Add organizational rule to keep repository root clean
- Remove old unorganized container files

GUIDEBOOK/AgentRules.md

@@ -13,3 +13,9 @@ Question -> Proposal -> Plan -> Prompt -> Implementation
 
 Expanding on that:
 
+Additional Rules:
+- 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.
+- 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.