2.0 of llm using opencoder

artifacts/CorePrompts/Biograpny.md

@@ -0,0 +1,46 @@
+### Core Biography Document
+
+**Name:** Charles N. Wyble
+**Roles:** Founder and CTO of Turnkey Network Systems LLC, RackRental.net, Suborbital Systems, Starting Line Productions, Axios Heart Studios; Executive Director and Board Chair of Side Door Group, Side Door Solutions Group, and Americans For A Better Network.
+**Location:** Based in Pflugerville, Texas, with a remote-first work style. Operates on Eastern Standard Time (EST).
+**Work Schedule:** 7:00 AM to 1:00 AM (18 hours/day). Manages a separate day job from 8:00 AM to 5:00 PM with intermittent responsiveness.
+**Overarching Business Group:** TSYS Group, a collection of for-profit LLCs and non-profit corporations.
+
+---
+
+#### **Professional Mission & Vision**
+The core mission is to provide a **payload-agnostic high-altitude balloon platform** to deliver low-cost internet access. This includes providing **100mbps middle-mile/wholesale backhaul** to fixed wireless ISPs and a new cooperative network, **High Flight Network Operating Company (HFNOC)**. This work supports the broader vision of achieving **$5.00 per month per endpoint internet access** everywhere legally possible. In addition to internet services, the platforms will support various payloads for sensing, ISR/C4I, and specialized networking.
+
+---
+
+#### **Business Focus**
+* **For-Profit LLCs:** These companies are focused on product and service delivery.
+    * **Turnkey Network Systems LLC:** Primary vehicle for the high-altitude balloon platform.
+    * **RackRental.net:** Physical company, likely related to data center or networking infrastructure.
+    * **Suborbital Systems:** Likely related to the core balloon platform technology.
+    * **Starting Line Productions:** Physical company with facilities used by Axios Heart Studios.
+    * **Axios Heart Studios:** Design and photography company, run day-to-day by a business partner.
+* **Non-Profit Corporations:** Planned to be 501c3/501c4/(super)PAC entities that support the overarching TSYS Group mission.
+    * **Side Door Group, Side Door Solutions Group, Americans For A Better Network.**
+
+---
+
+#### **Strategic Priorities & Challenges**
+A primary strategic priority is the "potential to kinetic" initiative, which aims to **exit the operational critical path** and fully hand over those responsibilities to the COO and CFO by April 1, 2026. Current challenges include managing various infrastructure projects and building out the asset base to generate consistent cash flow, all while operating from a home-based office in Pflugerville, Texas.
+
+---
+
+#### **Technology Stack**
+* **PAAS:** **Coolify** (configured but not yet in use for custom applications).
+* **Self-Hosting:** Extensive use of **Cloudron** for self-hosted back-office applications, including email, Redmine, Gitea, Matomo, Grafana, Prometheus, SigNoz, Dolibarr, and WordPress. Also hosts Nextcloud, Hashicorp Vault, and Minio.
+* **On-Premise Infrastructure:** On-premise compute and storage running **PiHole, Librenms, CA,** and **Home Assistant**. Future plans include a three-node **Proxmox** cluster with NFS root to run guest VMs as Kubernetes workers.
+* **Networking:** **Tailscale** is used to tie all systems together.
+* **Workstation:** A massive Dell workstation accessed remotely via **RDP** over Tailscale.
+
+---
+
+#### **Document & Communication Preferences**
+* **Audience:** A mix of both highly technical and business-focused individuals.
+* **Tone:** Warm, friendly, and approachable.
+* **Style:** Concise, with detailed information provided in appendices.
+

artifacts/CorePrompts/CoreRequirements-SAAS.md

@@ -0,0 +1,46 @@
+### Core Technical Requirements & Architecture Document
+
+#### Development Environment & Workflow
+- All work will be performed exclusively inside **Docker or devcontainer environments**. The host machine must remain pristine.
+- All commands will be executed inside containers using `docker exec`.
+- Work will be done on dedicated **feature branches** (e.g., `feature/login`, `wip/database-migration`). The `main` branch is protected and will not be used for direct commits.
+- A dedicated **`docs` branch** will be used for all documentation and will be kept merged into all active feature branches.
+- Frequent commits and pushes are mandatory. Use Git tags to mark significant milestones and release points, ensuring tags are pushed to the remote repository.
+- **Tools:** Gitea will be the sole Git repository management system.
+
+---
+
+#### Language & Technology Stack
+- The preferred languages, in descending order of preference, are **Rust**, **Go**, and **C**.
+- **Rust** is the primary choice for its security, performance, and memory safety.
+- **Go** will be used for its concurrency and simplicity, especially for services requiring high-concurrency handling.
+- **C** will be used sparingly for specific, performance-critical components via Foreign Function Interface (FFI).
+- **Node.js and Python** will be avoided unless a specific feature has a clear, compelling advantage.
+- **Cloud/PAAS:** Coolify will be used for custom application deployment.
+
+---
+
+#### Architecture, Security & Compliance
+- The architecture will be based on **microservices**, with the smallest possible feature boundaries.
+- **Security is paramount.** All projects will adhere to SOC, SOX, PCI, GDPR, and NIST standards. ITAR and classified work requirements will be handled on a per-project basis.
+- **Accessibility and internationalization** are essential and non-optional requirements for all projects.
+- **Database:** **PostgreSQL** will be our primary database.
+- **Data Access:** No direct database access is permitted between microservices. All communication must be handled via APIs.
+
+---
+
+#### Analysis & Recommendations
+
+Based on your new input, I have refined our architectural blueprint and can now propose concrete solutions.
+
+**Q: How should we handle Continuous Integration and Continuous Deployment?**
+A: We will use Gitea Actions as the default for event-driven workflows (e.g., pushes to feature branches, pull requests). Jenkins will be used for scheduled jobs, such as nightly builds or automated deployment runs, leveraging its powerful scheduling features.
+
+**Q: For persistent data, what are your preferences for database technologies? How should we handle state management between microservices?**
+A: **PostgreSQL** will be our primary database. State management between microservices will be strictly handled through **API communication**; no direct database access is allowed between services.
+
+**Q: What is your preferred protocol for communication between microservices? How should we handle API versioning and documentation?**
+A: We will use **gRPC** for inter-service communication due to its performance and type safety, which aligns with our language preferences. APIs will be versioned and documented using the OpenAPI (Swagger) specification.
+
+**Q: How should we integrate logging, tracing, and monitoring into the development workflow to ensure we have clear visibility into application performance and health?**
+A: We will use a comprehensive, self-hosted observability stack: **OpenTelemetry** for collecting data, **Prometheus** for metrics, **Grafana Loki** for logs, and **SigNoz** for distributed tracing and unified visualization.