reachableceo/ReachableCEO-AI-Homedir-Public
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: restructure repository with separated databank and PMO directories

Browse Source 
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
This commit is contained in:
Charles N Wyble - admin
2025-10-24 09:20:47 -05:00
parent b496e70147
commit 4ddb4631a5
12 changed files with 179 additions and 72 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
databank/README.md Normal file
View File

@@ -0,0 +1,5 @@
# Databank Directory
This directory contains readonly context for AI agents, including personal information, agent guidelines, and general context information.
For more details about the structure and purpose, see the main [README](../README.md).

200
databank/agents/AGENTS.md Normal file
View File

@@ -0,0 +1,200 @@
# Date/Time
Friday, October 24, 2025 (Timezone: UTC+00:00 - Please adjust to local system time)
# Change Tracking/Revision Table
| Date | Version | Description | Author |
|------------|---------|--------------------------------------------------|---------------------|
| 2025-10-24 | 2.0.0 | Update for databank/PMO restructure | AIOS-Public System |
| 2025-10-24 | 1.0.0 | Baseline AGENTS.md for mounting across all projects | AIOS-Public System |
# Changelog
| Date | Version | Description |
|------------|---------|--------------------------------------------------|
| 2025-10-24 | 2.0.0 | Updated for databank/PMO restructure |
| 2025-10-24 | 1.0.0 | Initial creation of baseline AGENTS.md |
---
# AGENTS.md - Guidelines for AI Agents in Restructured AI Home Directory
## Core Operating Principles
### Context Awareness
- You are operating within a mounted AI home directory with separated databank (readonly) and PMO (read-write)
- **Databank** (`/ai-home/databank/`): Contains readonly context, guidelines, and personal information
- **PMO** (`/ai-home/pmo/`): Contains project management functionality where updates are allowed
- Always consider the multi-project implications of your actions
- Respect the readonly nature of the databank and only update PMO when appropriate
### Communication Protocol
- Primary communication channel: collab/ directory in mounted AI home directory
- Use question -> proposal -> implementation workflow
- Document all significant decisions and changes with proper revision tracking
### Documentation Standards (Apply to ALL files you create)
- **Date/Time Headers**: Include date/time with timezone in all markdown files
- **Change Tracking**: Maintain revision tables in all documents
- **Changelog**: Include changelogs in all source code files
- **Make It Beautiful Rule**: All documentation follows beautiful formatting standards (tables, bullet points, clear structure, visual hierarchy)
## Repository Management
### Structure Requirements
- **Databank**: Readonly context (do not modify)
- `databank/personal/` - Personal information
- `databank/agents/` - Agent guidelines and tools
- `databank/context/` - General context information
- **PMO**: Read-write project management (updates allowed here)
- `pmo/dashboard/` - Dashboard views
- `pmo/projects/` - Project registry and tracking
- `pmo/reports/` - Status reports
- `pmo/resources/` - Resource management
- `pmo/config/` - Configuration
- Keep top-level repository clean (databank, pmo, and collab directories only)
- Use conventional commits (chore:, feat:, docs:, fix:, etc.)
- Commit frequently using atomic commits
- Only commit to local repository (no git push operations)
### Access Rights
- **Databank (readonly)**: Access only, no modifications allowed
- **PMO (read-write)**: Only update when project milestones reached or status updates needed
- **Collab (readonly)**: Access for reference, no modifications in active projects
## Development Workflow
### Pre-Work Checklist
- [ ] Read project-specific documentation first
- [ ] Check collab/rules directory for project-specific guidelines (SECURITY.md, RELEASE.md, GITFLOW.md, etc.)
- [ ] Review databank context for consistent understanding
- [ ] Understand project dependencies and constraints
### Implementation Standards
- Follow conventional commits with beautiful, descriptive messages
- Maintain consistency with existing codebase
- Add appropriate documentation and comments
- Consider maintainability and future extensions
### Verification Process
- Validate operations before execution
- Run appropriate tests and quality checks
- Verify outputs against expected outcomes
- Implement defensive programming practices
## PMO Update Guidelines
### When to Update PMO
- When project milestones are reached
- When project status changes significantly
- When new projects are initiated
- When projects are completed or paused
- When resource allocation changes
### What to Update in PMO
- Project registry in `pmo/projects/`
- Dashboard information in `pmo/dashboard/`
- Status reports in `pmo/reports/`
- Resource tracking in `pmo/resources/`
### What NOT to Update
- **Never modify databank files** - they are readonly
- Do not create new top-level directories
- Do not modify collab files in active projects
- Do not add audit logs to this repository (audit logs belong in projects)
## Best Practices for Solo Entrepreneur Workflow (14+ Hours Daily AI Usage)
### Efficiency Optimization
- Break complex tasks into atomic operations
- Provide quick wins while building long-term value
- Minimize context switching between projects
- Optimize for rapid iteration and feedback
### Decision Documentation
- Document reasoning for complex decisions
- Consider impact across multiple interconnected projects
- Maintain traceability for future reference
- Suggest alternatives when appropriate
### Scalability Considerations
- Design solutions that work across multiple project environments
- Use modular, reusable components and patterns
- Plan for increasing complexity as projects grow
- Maintain consistent interfaces across projects
## LLM Optimization Practices
### Prompt Engineering
- Structure requests with clear context from mounted AI home directory
- Use explicit, unambiguous language
- Provide sufficient context without unnecessary verbosity
- Break multi-step processes into clear, sequential instructions
### Code Generation
- Follow established project patterns and conventions
- Maintain consistency with existing code style
- Add appropriate error handling and validation
- Consider performance implications
### Quality Assurance
- Implement appropriate testing strategies
- Ensure code quality and maintainability
- Perform validation against requirements
- Include appropriate logging and monitoring
## Security, Compliance & Quality
### Security Practices
- Verify file permissions and access controls
- Sanitize all inputs and outputs appropriately
- Protect sensitive information and credentials
- Follow secure coding principles
### Compliance & Accessibility
- Follow accessibility standards (WCAG when applicable)
- Consider internationalization requirements
- Ensure compliance with relevant regulations
- Maintain proper documentation for audit purposes
### Performance Standards
- Optimize for efficient processing
- Consider resource usage and constraints
- Implement appropriate caching strategies
- Monitor and optimize for performance
## Git and Version Control
### Commit Standards
- Use conventional commits with semantic meaning
- Make commits atomic (one logical change per commit)
- Write descriptive commit messages
- Include relevant context in commit descriptions
### Branching and Merging
- Follow project-specific branching strategies
- Respect existing GitFlow patterns
- Use feature branches for significant changes
- Maintain clean commit history
## Environment Consistency
### Context Integration
- Recognize that databank is mounted readonly across multiple environments
- PMO is mounted read-write for project tracking
- Maintain consistency in behavior across different projects
- Respect environment-specific configurations
### Tool Integration
- Work with existing development tools and workflows
- Maintain compatibility with CI/CD pipelines
- Use project-appropriate build and deployment processes
- Respect project-specific dependencies and versions
### AI Tool Context (for agents working in this environment)
- **Codex** - Primary daily driver (subscription-based), best for code generation and completion
- **Qwen** - Heavy system orchestration, excels at shell/Docker operations
- **Gemini** - Primarily used for audits and analysis
- **Claude** - Used occasionally for specific tasks
---

84
databank/agents/AI-TOOLS.md Normal file
View File

@@ -0,0 +1,84 @@
# Date/Time
Friday, October 24, 2025 (Timezone: UTC+00:00 - Please adjust to local system time)
# Change Tracking/Revision Table
| Date | Version | Description | Author |
|------------|---------|--------------------------------------------------|---------------------|
| 2025-10-24 | 1.0.0 | Initial documentation for AI tool preferences | AIOS-Public System |
# Changelog
| Date | Version | Description |
|------------|---------|--------------------------------------------------|
| 2025-10-24 | 1.0.0 | Initial creation of AI tool usage documentation |
---
# AI Tool Preferences and Usage Patterns
## Overview
This document captures the current AI tool preferences and usage patterns for the AI home directory environment. It provides context for any AI agent working within this environment.
## Primary Tools and Usage
### 1. Codex (Primary Daily Driver)
- **Status**: Primary tool with subscription
- **Usage**: Daily development work, code generation, and completion
- **Strengths**: Code generation, completion, and general development tasks
- **Limitations**: Quota restrictions may limit heavy usage
### 2. Qwen (Heavy System Orchestration)
- **Status**: Most frequently used when Codex quota is exhausted
- **Usage**: Heavy system orchestration, shell operations, Docker management
- **Strengths**: Excellent knowledge of shell commands, Docker operations, and system-level tasks
- **Role**: Primary fallback and system-level operations tool
### 3. Gemini (Audit Specialist)
- **Status**: Primary audit and analysis tool
- **Usage**: Code audits, analysis, and review tasks
- **Strengths**: Analytical capabilities, detailed reviews, comparison operations
- **Role**: Quality assurance and audit functions
### 4. Claude (Occasional Use)
- **Status**: Used occasionally for specific tasks
- **Usage**: Specific reasoning tasks when needed
- **Strengths**: Advanced reasoning, document analysis, creative tasks
- **Role**: Specialized tasks when other tools aren't optimal
## Usage Patterns
### Daily Workflow
1. **Morning**: Start with Codex (if quota available) for primary development tasks
2. **Throughout Day**: Switch to Qwen when Codex quota is reached or for system operations
3. **Review/Audit**: Use Gemini for detailed analysis and code reviews
4. **Special Tasks**: Use Claude for specific reasoning requirements
### Tool Selection Guidelines
- **Code Generation/Completion**: Codex (primary), Qwen (when Codex unavailable)
- **System Orchestration**: Qwen (primary), Codex (secondary)
- **Audits and Reviews**: Gemini (primary), others (as needed)
- **Advanced Reasoning**: Claude (primary for complex reasoning), others (as needed)
### Context for AI Agents
When working in this environment, AI agents should be aware that:
- Commands and operations may be executed by different AI tools depending on availability
- Qwen is particularly valuable for shell and Docker operations
- Codex is the preferred tool for code generation when available
- Gemini should be considered for audit and analysis tasks
- The tool selection may change based on subscription quotas and availability
## Performance Considerations
### Tool Characteristics
- **Codex**: Excellent for code generation but limited by subscription quota
- **Qwen**: Reliable for system operations, good for heavy tasks, no quota limits
- **Gemini**: Best for analytical tasks and detailed reviews
- **Claude**: Good for complex reasoning but used selectively
### Optimizing Tool Usage
- Leverage Qwen for operations that require extensive system knowledge
- Use Codex for code-related tasks when available
- Employ Gemini for validation and quality checks
- Reserve Claude for specialized reasoning tasks

35
databank/agents/AgentRules.md Normal file
View File

@@ -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*

141
databank/context/AUDIT1.md Normal file
View File

@@ -0,0 +1,141 @@
# GUIDEBOOK Audit #1
Date: October 16, 2025
## Summary
Comprehensive review of the GUIDEBOOK directory and its contents conducted to identify areas for improvement and optimization.
## TODO Tracking
### Completed
- [x] Fixed typos in AboutMe.md
- [x] Updated AgentRules.md to remove reference to collab directory and improve formatting
- [x] Created GUIDEBOOK/README.md as central navigation document
### In Progress
- [ ] Enhance StartHere.md with more structured guidance
- [ ] Standardize formatting across all GUIDEBOOK files
- [ ] Add last-updated timestamps to documents
- [ ] Consider implementing document status tracking
### Deferred
- [ ] Update TSYS.md with current business entity information (will be updated later with detailed entity info)
## Files Reviewed
1. `AboutMe.md` - Personal information and background
2. `AgentRules.md` - Operational guidelines for agents
3. `ArchitecturalApproach.md` - Technical architecture patterns
4. `StartHere.md` - Onboarding and repository purpose
5. `TSYS.md` - Business entity information
## Analysis and Improvement Suggestions
### 1. Overall Structure & Organization
**Current State**: The GUIDEBOOK contains 5 files with different purposes but lacks a cohesive structure or navigation system.
**Suggested Improvements**:
- Add a main `README.md` or `INDEX.md` file in the GUIDEBOOK directory that serves as a table of contents and entry point
- Create cross-links between related documents
- Consider organizing files by function (Personal, Technical, Business) if the number of files grows
### 2. AboutMe.md - Personal Information
**Issues**:
- Contains outdated information (relocation to Raleigh NC in April 2026 is now in the past)
- Informal tone and formatting
- Missing important professional details
- Contains typos ("entrepenuer", "soverignity", "streamlne")
**Suggested Improvements**:
- Standardize formatting with consistent headers
- Update or remove time-sensitive information
- Add professional skills, technical expertise, and areas of focus
- Include contact methods or communication preferences
- Add a section on current projects or focus areas
- Proofread and fix typos
### 3. AgentRules.md - Operational Guidelines
**Strengths**:
- Clear workflow pattern (Question -> Proposal -> Plan -> Prompt -> Implementation)
- Good technical guidelines for Docker containers
- Clear expectations about communication style
**Issues**:
- Mixed formatting and inconsistent structure
- Contains a rule about the collab directory that is now removed
- Some rules are quite detailed while others are brief
- The title "This file is rules for you to follow" is informal
**Suggested Improvements**:
- Restructure as a proper markdown document with clear sections
- Update the rules to reflect the current architecture (remove collab reference)
- Add more specific examples where needed
- Create a more professional title like "Agent Interaction Guidelines"
- Possibly break this into multiple focused documents if it grows larger
- Add sections on error handling, rollback procedures, and testing expectations
### 4. ArchitecturalApproach.md - Technical Architecture
**Strengths**:
- Well-structured with clear sections
- Comprehensive coverage of architectural principles
- Good technical details about security and operations
**Issues**:
- Could benefit from more specific examples
- Some sections could be expanded with implementation details
- Could include more discussion of trade-offs or considerations
**Suggested Improvements**:
- Add diagrams or visual representations where helpful
- Include specific examples of good vs. bad implementations
- Add sections on monitoring, logging, and observability
- Include guidance on when to use each architectural pattern
- Add a section on migration patterns for existing systems
### 5. StartHere.md - Onboarding Guide
**Strengths**:
- Clear explanation of the repository's purpose as a template
- Good metaphor of a "home directory" for project launch
**Issues**:
- Could be more comprehensive in terms of onboarding
- Lacks specific instructions on next steps
- Could benefit from a more structured approach
**Suggested Improvements**:
- Add a step-by-step onboarding process
- Include links to important resources
- Add information about repository structure and navigation
- Include guidelines on when and how to copy/clone the template
- Add troubleshooting section for common setup issues
### 6. TSYS.md - Business Information
**Issues**:
- Contains outdated information (2026 dates are now in the past)
- Complex organizational structure that's hard to follow
- Technical jargon that may not be clear to all readers
- Formatting needs improvement for readability
**Suggested Improvements**:
- Update or remove time-sensitive information
- Create a clearer organizational chart or hierarchy
- Add a glossary of terms for the various entities
- Include mission statement and core values more prominently
- Add timelines for current initiatives and status updates
- Simplify the explanation of the digital divide solution
### 7. Cross-cutting Improvements
**Consistency**:
- Standardize the format and style across all GUIDEBOOK files
- Use consistent header levels and formatting
- Implement a consistent terminology throughout
- Consider implementing versioning for important policy documents
**Maintainability**:
- Add last-updated timestamps to each document
- Create a document for change management procedures
- Consider implementing document status (draft, active, deprecated)
**Integration**:
- Add cross-references between related documents
- Create a central index or navigation system
- Consider linking to external resources or related documents

184
databank/context/PROJECT-MGMT-TOOLS.md Normal file
View File

@@ -0,0 +1,184 @@
# Date/Time
Friday, October 24, 2025 (Timezone: UTC+00:00 - Please adjust to local system time)
# Change Tracking/Revision Table
| Date | Version | Description | Author |
|------------|---------|--------------------------------------------------|---------------------|
| 2025-10-24 | 1.0.0 | Initial documentation for CLI project management tools | AIOS-Public System |
# Changelog
| Date | Version | Description |
|------------|---------|--------------------------------------------------|
| 2025-10-24 | 1.0.0 | Initial creation of project management tools documentation |
---
# CLI Project Management Tools for AI Home Directory
## Overview
This document provides information about self-contained command-line project management tools that can be integrated into your AI home directory for enhanced PMO (Project Management Office) functionality. These tools complement traditional markdown files with visual representations and advanced project management features.
## 1. MarkWhen
### Description
MarkWhen is an open-source tool that transforms simple markdown-like syntax into interactive timelines, Gantt charts, and calendars. It's particularly well-suited for visualizing project schedules and timelines.
### Key Features
- **Timeline Visualization**: Convert markdown to interactive timelines
- **Gantt Charts**: Visual project scheduling and dependencies
- **Calendar Views**: Month, week, and day views
- **Simple Syntax**: Uses familiar markdown-like syntax
- **CLI Tool**: Can be run from the command line
- **Self-Contained**: Single binary with no complex dependencies
### Integration with AI Home Directory
- Store `.markwhen` files in the PMO directory
- Generate visual timelines and Gantt charts programmatically
- Convert project milestones into visual formats
- Create interactive project schedules
### Example Syntax
```markwhen
# Project Timeline
## [2025-01-01 - 2025-03-31] Project Initiation
- Requirements gathering
- Team formation
- Technical planning
## [2025-04-01 - 2025-06-30] Development Phase 1
- Core architecture
- Initial features
- Testing
```
### Installation
- Can be installed globally via npm: `npm install -g @markwhen/cli`
- Or used as a standalone executable
- Integration with Node.js ecosystem
## 2. Taskwarrior
### Description
A command-line task management tool that's highly efficient for developers. It's often called the "todo.txt on steroids" and offers powerful query and management capabilities.
### Key Features
- **Powerful Queries**: Complex filtering and reporting
- **Dependencies**: Task dependency management
- **Annotations**: Context and history for tasks
- **Fast Performance**: Optimized for speed
- **No UI Dependencies**: Pure command-line interface
- **Sync Capabilities**: Can sync between systems
- **Scriptable**: Integrates well with shell scripts
### Integration with AI Home Directory
- Store `.task` directory in PMO structure
- Track all project tasks via command line
- Generate reports and statistics
- Use with shell scripting for automation
### Example Commands
```bash
task add project:ecommerce "Implement checkout flow" priority:H
task projects
task summary
```
## 3. Timewarrior
### Description
A command-line time tracking tool by the same authors as Taskwarrior. It integrates seamlessly with Taskwarrior for comprehensive time and task management.
### Key Features
- **Time Tracking**: Track time spent on tasks
- **Reporting**: Detailed time reports
- **Intervals**: Track time intervals with tags
- **Visualizations**: Calendar and summary views
- **Integration**: Works with Taskwarrior
- **Flexible**: Track time without necessarily having tasks
### Integration with AI Home Directory
- Track time across multiple projects
- Generate time reports for PMO dashboard
- Integrate with Taskwarrior for task-time correlation
## 4. Org-mode (via Emacs or command-line tools)
### Description
While traditionally part of Emacs, org-mode can be used via command-line tools and offers comprehensive document authoring and project management capabilities.
### Key Features
- **Hierarchical Organization**: Nested project structures
- **Agenda Views**: Schedule visualization
- **Export Capabilities**: Export to many formats
- **Time Tracking**: Built-in time clocking
- **Task Management**: TODO states and dependencies
- **Document Authoring**: Rich text with code execution
### Integration with AI Home Directory
- Can be processed via command-line Emacs
- Export to HTML for web dashboards
- Powerful querying capabilities
## 5. Kanban CLI Tools
### Trello or GitHub CLI
For Kanban-style management:
- **GitHub CLI**: With projects and issue management
- **Trello CLI**: For Kanban boards (if using Trello)
### Board CLI
Command-line Kanban boards stored as text files:
- Lightweight
- Git-friendly
- Simple to manage
- Can be version controlled
## 6. Calcurse
### Description
A text-based calendar and scheduling application for the command line. It provides calendar, todo-list, and notes functionality.
### Key Features
- **Calendar Views**: Month, week, day views
- **Todo List**: Task management with priorities
- **Scheduling**: Appointments and events
- **Import/Export**: CalDAV support
- **Customizable**: Extensive configuration
## 7. HPI (Health Data CLI)
While focused on health data, HPI shows how command-line tools can manage complex data structures through:
- Configuration-based data management
- CLI commands for data operations
- Export capabilities to various formats
## Recommendations for AI Home Directory
### Immediate Integration
1. **MarkWhen**: Start with visual timeline generation for PMO dashboards
2. **Taskwarrior**: For detailed task management across projects
3. **Timewarrior**: For time tracking and productivity metrics
### Implementation Strategy
- Store configuration files in PMO directory
- Create scripts to generate visual outputs
- Integrate with existing AI agent workflows
- Generate automated reports for PMO dashboard
### Advantages of CLI Tools
- **Self-Contained**: No external services needed
- **Git-Compatible**: Text-based formats version control well
- **Scriptable**: Easy to automate with AI agents
- **Efficient**: Fast operation with minimal overhead
- **Private**: All data stays local
- **Customizable**: Can be integrated with custom scripts
## Next Steps
1. Evaluate MarkWhen for timeline visualization
2. Set up Taskwarrior for task management
3. Create integration scripts for PMO functionality
4. Develop automation for AI agent interactions

15
databank/personal/AboutMe.md Normal file
View File

@@ -0,0 +1,15 @@
My full name is Charles N Wyble. I use the online handle @ReachableCEO.
I am a strong believer in digital data sovereignty. I am a firm practitioner 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 a solo entrepreneur 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 streamline my life using AI and relying on it for all aspects of my professional, knowledge worker actions.
I prefer relaxed but professional engagement and don't want to be flattered.
---
*Last updated: October 16, 2025*

31
databank/personal/StartHere.md Normal file
View File

@@ -0,0 +1,31 @@
# Getting Started with AIOS-Public
This repository serves as the starting point for all AI interactions within the AIOS system.
## Purpose
This repository functions as a template for launching new projects. It contains the foundational architecture, documentation, and tools needed to create new repositories following AIOS patterns.
## Workflow
- Unless specifically creating new tools for the template itself, AI agents will not work directly in this repository
- All project-specific work happens in separate repositories created from this template
- When instructed, AI agents may commit or push changes to this template repository
- AI agents carry forward the core knowledge from GUIDEBOOK files when working in project repositories
- All work in project repositories follows the workflow and rules outlined in AgentRules.md
## Repository Structure
Think of this repository like a highly organized home directory. The markdown files and Docker containers serve as the foundational "dotfiles" that provide consistent patterns across all projects.
Project work is conducted in subdirectories or separate repositories created from this template, not directly in this template repository.
## Next Steps
When beginning work in a new project repository:
1. Review the GUIDEBOOK documentation for architectural patterns
2. Follow the workflow outlined in AgentRules.md
3. Apply the architectural approach described in ArchitecturalApproach.md
---
*Last updated: October 16, 2025*

54
databank/personal/TSYS.md Normal file
View File

@@ -0,0 +1,54 @@
# TSYS Group Documentation
This file documents the TSYS Group and its entities.
## Legal Entities
All entities are filed and domiciled in the great state of Texas.
### For-Profit Entities
- **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 the "moonshot" business and will be where all fundraising is done
### Non-Profit Entities
- **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
## Mission Statement
The overall goal of TSYS Group is to solve the digital divide through a combination of:
- R&D
- Operations
- Advocacy/Lobbying/Education
We are fiercely FLO and our governance materials are open.
## Business Model Vision
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
- Currently in early formation stages
- 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 HFNOC
- Also in early formation stages currently
- Will handle 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
- 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.
## Abbreviated Entity Names
- RWSCP
- RWFO
- AP4AP
---
*Last updated: October 16, 2025*

1
databank/templates/OPS-ENVIRONMENT.md Normal file
View File

@@ -0,0 +1 @@