progress snapshot
This commit is contained in:
@@ -1,53 +0,0 @@
|
||||
# Intake Directory
|
||||
|
||||
This directory contains structured intake templates and responses for comprehensive information gathering.
|
||||
|
||||
## Purpose
|
||||
|
||||
- **Structured Collection**: Formal templates for gathering comprehensive information
|
||||
- **Consistent Updates**: Standardized approach to updating databank content
|
||||
- **Complete Coverage**: Ensure all relevant information captured during updates
|
||||
|
||||
## Structure
|
||||
|
||||
```
|
||||
intake/
|
||||
├── templates/ # Structured intake templates
|
||||
├── responses/ # Completed intake responses
|
||||
└── README.md # This file
|
||||
```
|
||||
|
||||
## Workflow
|
||||
|
||||
1. **Template Selection**: Choose appropriate template for update type
|
||||
2. **Information Gathering**: Conduct structured interview using template
|
||||
3. **Response Recording**: Record responses in responses/ directory
|
||||
4. **Processing**: AI processes responses and updates databank/artifacts/
|
||||
5. **Validation**: Review and confirm updates to databank/artifacts/
|
||||
|
||||
## Templates
|
||||
|
||||
Common intake templates include:
|
||||
|
||||
- **Personal Information**: Updates to biographical and preference information
|
||||
- **AI Tools and Preferences**: Changes to tool usage and agent guidelines
|
||||
- **Operational Procedures**: Updates to workflows and processes
|
||||
- **Project Information**: New projects or updates to existing projects
|
||||
- **Relationship Changes**: Updates to professional networks and collaborations
|
||||
|
||||
## Guidelines
|
||||
|
||||
### For Humans
|
||||
- **Use Appropriate Template**: Select template matching update type
|
||||
- **Be Comprehensive**: Provide complete information when responding
|
||||
- **Follow Structure**: Maintain template format for easy processing
|
||||
- **Be Accurate**: Provide current and accurate information
|
||||
|
||||
### For AI Agents
|
||||
- **Guide Through Process**: Help humans complete templates accurately
|
||||
- **Clarify Questions**: Explain ambiguous template items
|
||||
- **Validate Responses**: Ensure responses are complete and consistent
|
||||
- **Process Thoroughly**: Convert responses to appropriate databank updates
|
||||
- **Maintain History**: Track changes and updates over time
|
||||
|
||||
---
|
||||
@@ -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*
|
||||
@@ -9,27 +9,28 @@ Complete this template with current and accurate information about yourself.
|
||||
## Identity Information
|
||||
|
||||
### Legal Name
|
||||
Full legal name:
|
||||
Full legal name: Charles N Wyble
|
||||
|
||||
Preferred name/nickname:
|
||||
Preferred name/nickname: Charles
|
||||
|
||||
Online handles and professional identities:
|
||||
- GitHub:
|
||||
- Twitter:
|
||||
I use @reachableceo everywhere
|
||||
|
||||
- LinkedIn:
|
||||
- Other relevant platforms:
|
||||
|
||||
Contact preferences and methods:
|
||||
- Email:
|
||||
- Phone:
|
||||
- Signal:
|
||||
- Other secure messaging:
|
||||
- Email: charle@@turnsys.com
|
||||
- Phone: 818 280 7059
|
||||
- Signal: 818 280 7059
|
||||
|
||||
That number/email should find me on all platforms
|
||||
|
||||
|
||||
Geographic location:
|
||||
- Current location:
|
||||
- Planned moves:
|
||||
- Current location: Austin Texas
|
||||
- Planned moves: Raleigh North Carolina in April 2026
|
||||
|
||||
Age/birth year:
|
||||
Age/birth year: 41 years old, 1984
|
||||
|
||||
## Professional Background
|
||||
|
||||
@@ -41,30 +42,18 @@ Chronological list of significant positions:
|
||||
|
||||
### Core Competencies
|
||||
List your primary skills and expertise areas:
|
||||
-
|
||||
- Technology Operations
|
||||
-
|
||||
-
|
||||
|
||||
### Industry Experience
|
||||
List industries where you have significant experience:
|
||||
-
|
||||
-
|
||||
-
|
||||
|
||||
### Certifications and Qualifications
|
||||
List relevant certifications and qualifications:
|
||||
-
|
||||
-
|
||||
-
|
||||
|
||||
### Notable Achievements
|
||||
List significant professional achievements:
|
||||
-
|
||||
-
|
||||
-
|
||||
|
||||
### Current Focus
|
||||
Describe your current professional focus and goals:
|
||||
|
||||
Building TSYS Group from scratch to the worlds first mutli trillion dollar cooperative.
|
||||
|
||||
Overall goal is to provide internet to all from high altitude balloons for $5.00 per month per endpoint for 5mbps symetric bandwidth
|
||||
-
|
||||
|
||||
## Philosophical Positions
|
||||
@@ -0,0 +1,222 @@
|
||||
# Personal Information Intake Template
|
||||
|
||||
This template guides the collection of personal information for databank population.
|
||||
|
||||
## Instructions
|
||||
|
||||
Complete this template with current and accurate information about yourself.
|
||||
|
||||
## Identity Information
|
||||
|
||||
### Legal Name
|
||||
Full legal name: Charles N Wyble
|
||||
|
||||
Preferred name/nickname: Charles
|
||||
|
||||
Online handles and professional identities:
|
||||
I use @reachableceo everywhere
|
||||
|
||||
- LinkedIn: https://linkedin.com/in/charlesnwyble
|
||||
|
||||
Contact preferences and methods:
|
||||
- Email: charles@turnsys.com
|
||||
- Phone: 818 280 7059
|
||||
- Signal: 818 280 7059
|
||||
|
||||
That number/email should find me on all platforms
|
||||
|
||||
|
||||
Geographic location:
|
||||
- Current location: Austin Texas
|
||||
- Planned moves: Raleigh North Carolina in April 2026
|
||||
|
||||
Age/birth year: 41 years old, 1984
|
||||
|
||||
## Professional Background
|
||||
|
||||
### Career Timeline
|
||||
Chronological list of significant positions:
|
||||
1. Founder/CTPO - TSYS Group (2024-Present)
|
||||
2. Senior Software Engineer - Various (Early Career)
|
||||
3. Technology Operations Lead - Various (Mid Career)
|
||||
|
||||
### Core Competencies
|
||||
List your primary skills and expertise areas:
|
||||
- Technology Operations
|
||||
- Cooperative Business Models
|
||||
- High-Altitude Balloon Infrastructure
|
||||
|
||||
|
||||
### Current Focus
|
||||
Describe your current professional focus and goals:
|
||||
|
||||
Building TSYS Group from scratch to the worlds first mutli trillion dollar cooperative.
|
||||
|
||||
Overall goal is to provide internet to all from high altitude balloons for $5.00 per month per endpoint for 5mbps symetric bandwidth
|
||||
- Focus on creating scalable cooperative technology infrastructure
|
||||
- Development of balloon-based internet solutions
|
||||
- Building community-owned networks
|
||||
|
||||
## Philosophical Positions
|
||||
|
||||
### Core Values
|
||||
List your fundamental values and beliefs:
|
||||
- Cooperative ownership models
|
||||
- Technology for social good
|
||||
- Open governance principles
|
||||
|
||||
### Political Affiliations
|
||||
Describe your political positions and civic engagement:
|
||||
- Fiercely FLO (Free/Libre/Open) advocate
|
||||
- Support for technology democracy
|
||||
- Community-centered governance
|
||||
|
||||
### Ethical Frameworks
|
||||
Describe your ethical frameworks and guiding principles:
|
||||
- Open governance materials
|
||||
- Community benefit over profit maximization
|
||||
- Democratic technology ownership
|
||||
|
||||
### Approach to Work
|
||||
Describe your approach to work and collaboration:
|
||||
- Ruthlessly pragmatic
|
||||
- Challenge-oriented
|
||||
- Focus on ambiguity reduction
|
||||
|
||||
### Views on Technology
|
||||
Describe your views on technology and AI integration:
|
||||
- Technology should serve communities, not corporations
|
||||
- AI as a tool for efficiency and scalability
|
||||
- Open source and collaborative development
|
||||
|
||||
### Stance on Privacy
|
||||
Describe your stance on data privacy and sovereignty:
|
||||
- User data ownership by individuals
|
||||
- Minimal data collection
|
||||
- Transparent privacy practices
|
||||
|
||||
## Technical Preferences
|
||||
|
||||
### Preferred Tools
|
||||
List your preferred tools and platforms:
|
||||
- Git for version control
|
||||
- Docker for containerization
|
||||
- VS Code for development
|
||||
- CLI tools for automation
|
||||
|
||||
### Technology Stack
|
||||
Describe your current technology stack and environment:
|
||||
- Linux-based development environment
|
||||
- Containerized applications
|
||||
- Git-based workflows
|
||||
- AI integration tools (Qwen, Codex, Gemini)
|
||||
|
||||
### AI Tool Usage
|
||||
Describe your AI tool usage patterns and preferences:
|
||||
- Codex for code generation and completion
|
||||
- Qwen for system orchestration and shell/Docker operations
|
||||
- Gemini for audits and analysis
|
||||
|
||||
### Development Methods
|
||||
List your preferred development methodologies and practices:
|
||||
- Atomic commits with detailed messages
|
||||
- Test-driven development
|
||||
- Code reviews and documentation
|
||||
- Continuous integration
|
||||
|
||||
### Security Practices
|
||||
Describe your security and privacy practices:
|
||||
- Principle of least privilege
|
||||
- Regular security audits
|
||||
- Secure coding practices
|
||||
- Privacy by design
|
||||
|
||||
### Automation Approaches
|
||||
Describe your approaches to automation and efficiency:
|
||||
- Routine automation
|
||||
- Infrastructure as code
|
||||
- Continuous deployment
|
||||
- AI-assisted development
|
||||
|
||||
## Lifestyle and Context
|
||||
|
||||
### Daily Schedule
|
||||
Describe your typical daily schedule and work patterns:
|
||||
- 14+ hours daily AI usage
|
||||
- Early morning deep work
|
||||
- Afternoon project management
|
||||
- Evening reflection and planning
|
||||
|
||||
### Communication Preferences
|
||||
Describe your communication preferences and style:
|
||||
- Direct and explicit communication
|
||||
- Written documentation preferred
|
||||
- Question -> proposal -> implementation workflow
|
||||
- Structured and clear requests
|
||||
|
||||
### Collaboration Approaches
|
||||
Describe your collaboration approaches and expectations:
|
||||
- Clear role definitions
|
||||
- Explicit communication protocols
|
||||
- Shared documentation
|
||||
- Defined decision-making processes
|
||||
|
||||
### Work-Life Balance
|
||||
Describe your work-life balance priorities:
|
||||
- Deep work during focused periods
|
||||
- Regular breaks for sustainability
|
||||
- Balance between multiple projects
|
||||
- Long-term health and productivity
|
||||
|
||||
### Ongoing Projects
|
||||
List your current ongoing projects and initiatives:
|
||||
- TSYS Group development
|
||||
- High altitude balloon internet project
|
||||
- Cooperative business model implementation
|
||||
- AI-assisted development workflows
|
||||
|
||||
### Future Plans
|
||||
Describe your future plans and aspirations:
|
||||
- Move to Raleigh, NC in April 2026
|
||||
- Scale TSYS Group to multi-trillion dollar cooperative
|
||||
- Deploy global balloon internet infrastructure
|
||||
- Build replicable cooperative technology models
|
||||
|
||||
## Relationships and Networks
|
||||
|
||||
### Key Professional Relationships
|
||||
List key professional relationships:
|
||||
- Albert (future COO)
|
||||
- Technical co-founders and engineers
|
||||
- Cooperative business advisors
|
||||
- Community stakeholders
|
||||
|
||||
### Organizational Affiliations
|
||||
List organizational affiliations:
|
||||
- TSYS Group (Founder)
|
||||
- Various technology communities
|
||||
- Cooperative business networks
|
||||
- Open source projects
|
||||
|
||||
### Community Involvement
|
||||
Describe community involvement:
|
||||
- Cooperative technology advocacy
|
||||
- Open source contributions
|
||||
- Community technology projects
|
||||
- Educational initiatives
|
||||
|
||||
### Mentorship Roles
|
||||
Describe mentorship and advisory roles:
|
||||
- Technology strategy advisor
|
||||
- Cooperative business mentor
|
||||
- AI tool implementation consultant
|
||||
- Entrepreneurship coach
|
||||
|
||||
### Collaboration Patterns
|
||||
Describe partnership and collaboration patterns:
|
||||
- Question -> proposal -> implementation
|
||||
- Clear communication protocols
|
||||
- Defined roles and responsibilities
|
||||
- Shared documentation and tracking
|
||||
|
||||
---
|
||||
61
databank/collab/intake/inbox/DevelopmentRules.md
Normal file
61
databank/collab/intake/inbox/DevelopmentRules.md
Normal file
@@ -0,0 +1,61 @@
|
||||
# Rules for developing software deliverables at TSYS Group
|
||||
*Adopt these principles and checklist items for every TSYS Group software deliverable—clear, testable, and production-ready.*
|
||||
|
||||
**Core Constraints**
|
||||
- Only perform host operations for:
|
||||
- git workflows (clone, fetch, commit, push, branch, tag)
|
||||
- Docker and Docker Compose (build, run, compose up/down, network operations)
|
||||
- All development and runtime tasks must be performed inside Docker containers.
|
||||
- Expose only the main application web interface to external networks; all other services/ports remain internal to the per-stack Docker network.
|
||||
|
||||
**Containerization & Deployment**
|
||||
- Ship the application as a Docker container image.
|
||||
- Provide and maintain a canonical docker-compose.yml that describes service dependencies, networks, volumes, and healthchecks.
|
||||
- Ensure the container:
|
||||
- builds reproducibly
|
||||
- starts reliably
|
||||
- passes automated smoke tests before any release or QA signoff
|
||||
|
||||
**Testing, QA & Reliability**
|
||||
- Follow Test-Driven Development (TDD) for all new features and bug fixes.
|
||||
- Create comprehensive automated test suites (unit, integration, E2E where applicable).
|
||||
- Maintain very high test coverage and ensure all tests pass in CI before merging.
|
||||
- Treat all warnings as errors; configure CI to fail on warnings where practical.
|
||||
- Include CI jobs that:
|
||||
- build the container
|
||||
- run linting
|
||||
- run tests
|
||||
- perform smoke/startup checks
|
||||
|
||||
**Security & Compliance**
|
||||
- Adhere to best practices for security, QA, engineering, and SRE/DevOps.
|
||||
- Ensure compliance with applicable regimes (PCI, GDPR, SOC, FedRAMP, accessibility standards).
|
||||
- Design for least privilege in containers and networks; avoid exposing credentials/secrets in images or source.
|
||||
- Integrate static analysis, dependency scanning, and container image vulnerability scanning into CI.
|
||||
|
||||
**Accessibility**
|
||||
- Prioritize accessibility from the start; satisfy applicable accessibility guidelines required by US Government contracts.
|
||||
- Include accessibility checks in test and QA processes.
|
||||
|
||||
**Code Quality & Maintainability**
|
||||
- Lint all artifacts (code, configuration, Dockerfiles, YAML).
|
||||
- Do not incur technical debt; add required tests, docs, and refactors as part of the change.
|
||||
- Maintain clear, organized repository and docs. Keep docker-compose.yml and runbooks up to date.
|
||||
|
||||
**Operational/SRE Requirements**
|
||||
- Provide healthchecks and metrics-friendly endpoints where applicable.
|
||||
- Document startup, configuration, and rollback procedures.
|
||||
- Ensure containers start quickly and deterministically for orchestration and smoke tests.
|
||||
|
||||
**Acceptance Checklist (must be satisfied before “done”)**
|
||||
- [ ] Code follows TDD and has adequate tests
|
||||
- [ ] Linting passes with zero warnings
|
||||
- [ ] Container image builds reproducibly
|
||||
- [ ] Container starts and passes smoke tests locally and in CI
|
||||
- [ ] docker-compose.yml reflects current service topology
|
||||
- [ ] Vulnerability and dependency scans show no critical issues
|
||||
- [ ] Accessibility and applicable compliance checks pass
|
||||
- [ ] Documentation and runbooks updated
|
||||
- [ ] No outstanding technical debt items left untracked
|
||||
|
||||
Follow this checklist and principles for every change to ensure secure, testable, and production-ready deliverables.
|
||||
Reference in New Issue
Block a user