Add core architecture patterns and GIS/weather components from AIOS-Public

GUIDEBOOK/AboutMe.md

@@ -0,0 +1,12 @@
+My full name is Charles N Wyble. I use the online handle @ReachableCEO. 
+I am a strong believer in digital data soverignity. I am a firm practicer of self hosting (using Cloudron on a netcup vps and soon Coolify on another Cloudron VPS).
+I am 41 years old.
+I am a democrat and believe strongly in the rule of law and separation of powers.
+I actively avoid the media. 
+I am solo entrepenuer creating an ecosystem of entities called TSYS Group. (Please see TSYS.md for more on that)
+My professional background is in production technical operations since 2002
+I use many command line ai agents (codex,coder,qwen,gemini) and wish to remain agent agnostic at all times
+I am located in the United States of America . As of October 2025 I am located in central texas
+I will be relocating to Raleigh North Carolina in April 2026
+I want to streamlne my life using AI and relying on it for all aspects of my professional, knowledge worker actions.
+I prefer relaxed but professional engagement and dont want to be flattered.

GUIDEBOOK/AgentRules.md

@@ -0,0 +1,26 @@
+This file is rules for you to follow
+
+
+Always refer to me as Charles. Do not ever refer to me as "the human" or "the user" please. 
+Do not be a sychophant
+Avoid fluff in your responses
+
+Use this pattern for workflows:
+
+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.
+- 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.
+- All projects should include a collab/ directory with subdirectories: questions, proposals, plans, prompts, and audit.
+- 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.

GUIDEBOOK/ArchitecturalApproach.md

@@ -0,0 +1,47 @@
+# Architectural Approach
+
+This document captures the architectural approach for project development in the AIOS-Public system.
+
+## Container Architecture
+
+### Layered Approach
+- Base containers provide foundational tools and libraries
+- Specialized containers extend base functionality for specific use cases
+- Each layer adds specific capabilities while maintaining consistency
+
+### Naming Convention
+- Use `RCEO-AIOS-Public-Tools-` prefix consistently
+- Include descriptive suffixes indicating container purpose
+- Follow pattern: `RCEO-AIOS-Public-Tools-[domain]-[type]`
+
+### Security Patterns
+- Minimize root usage during build and runtime
+- Implement non-root users for all runtime operations
+- Use UID/GID mapping for proper file permissions across environments
+- Detect host user IDs automatically through file system inspection
+
+### Operational Patterns
+- Create thin wrapper scripts that handle environment setup
+- Use consistent patterns for user ID detection and mapping
+- Maintain same operational workflow across all containers
+- Provide clear documentation in README files
+
+### Organization Principles
+- Separate COO mode (operational tasks) from CTO mode (R&D tasks) containers
+- Create individual directories per container type
+- Maintain disciplined file organization to prevent technical debt
+- Keep repository root clean with project-specific files in subdirectories
+
+## Documentation Requirements
+- Each container must have comprehensive README
+- Include usage examples and environment setup instructions
+- Document security and permission handling
+- Provide clear container mapping and purpose
+
+## Implementation Workflow
+1. Start with architectural design document
+2. Create detailed implementation plan
+3. Develop following established patterns
+4. Test with sample data/usage
+5. Document for end users
+6. Commit with conventional commit messages

GUIDEBOOK/StartHere.md

@@ -0,0 +1,9 @@
+This repository is where I will start all of my AI interactions from.
+
+Unless we are making new tools, you won't be doing any work in this repository (other than when I tell you to commit/push anything in the tree).
+
+You will be doing all your work in a new repository that I will tell you about. You will have all of the core knowledge from
+the GUIDEBOOK directory files and you will follow the workflow and rules outlined in AgentRules.md in that new project repository.
+
+Think of this repository like the top level of a users home directory who is hyper organized. These markdown files and docker containers are kind of the dotfiles.
+Any work would be done in a sub directory off of the users home directory, not at the top level. 

GUIDEBOOK/TSYS.md

@@ -0,0 +1,36 @@
+This file documents the TSYS Group.
+
+Legal Entities (all filed and domiciled in the great state of Texas)
+
+Turnkey Network Systems LLC (a series LLC) 
+RackRental.net Operating Company LLC (a stand alone LLC) (all consulting and SAAS operations are run from here)
+Suborbital Systems Development Company LLC (a stand alone LLC) (this is my "moonshot" business and will be where all fundraising is done)
+
+Americans For A Better Network INC (a Texas non profit) (plan to be a 501c3) (want to get a fiscal sponsor by end of 2025)
+Side Door Group (a Texas non profit) (plan to be a 501c4)
+Side Door Solutions Group INC (a Texas non profit) (super PAC)
+
+
+The overaall goal of TSYS Group is to solve the digital divide through a combination of :
+
+R&D
+Operations
+Advocacy/Lobbying/Education
+
+We are firecly FLO and also our governance materials are open. 
+
+We want our operations/business model to be adopted by other passionate pragmatic individuals to solve big problems (clean water, clean energy, governance, food shortages etc). We believe strongly that only a combination of private enterprise and government can solve these issues.
+
+
+Series of Turnkey Network Systems LLC
+
+High Flight Network Operating Company (HFNOC) (will be a coop in all states that recognize it) in early formation stages currently . This will be the entity (a collection of sub entities under this banner) that will own and operate (in coop/collective trust) balloons and ground stations for MorseNet (what we are calling the network we are building)
+
+High Flight Network Finance Company (HFNFC) (will also be a coop just like HFNFC , also in early formation stages currently). This will be the entity that handles network finance/construction/loans etc. The idea is to raise financing from main street. To the extent wall street participates, it's only given financial interest, not governance. 
+We will not do security bundling and chase returns. The capital will earn a reasonable rate of return and reinvest into the coop to build more networks and keep debt and interest rates low.
+
+RWSCP
+
+RWFO
+
+AP4AP