Languages & Platforms
- Python
- C#
- .NET
- TypeScript
- JavaScript
- PowerShell
- Luau
FDS // TECHNICAL FOUNDATIONS
A stack matters because of what it enables. This map connects the major FDS systems to the languages, runtimes, engines, and technical areas actually used in their current repositories.
| System | Technologies / areas | Why they are there |
|---|---|---|
| CodeForge | TypeScript, Node.js, Electron, React, SQLite, Git, VS Code, model/provider APIs | Repository intelligence, autonomous task execution, desktop/CLI/editor surfaces, and free-first model routing. |
| GEMS / Training Grounds | Python, model post-training, evaluation, curriculum systems, CUDA/GPU environments | Specialization, teaching, held-out evaluation, checkpoints, and hardware-aware model research. |
| KyraBlox | C#, .NET 8, WPF, Luau/Roblox, C++/Unreal, engine plugins, local protocols | Project inspection, governed missions, engine integration, approvals, validation, and recovery. |
| ForgerEMS | C#, .NET, WPF, Windows APIs, PowerShell, USB and hardware interfaces | Technician diagnostics, drive validation, USB tooling, system information, and local-first assistance. |
| FDS Website | Astro, TypeScript, Vitest, Cloudflare Workers, GitHub Pages | Static public publishing plus the separately deployed Kayla site-guide runtime. |
Technologies / areas
TypeScript, Node.js, Electron, React, SQLite, Git, VS Code, model/provider APIs
Why they are there
Repository intelligence, autonomous task execution, desktop/CLI/editor surfaces, and free-first model routing.
Technologies / areas
Python, model post-training, evaluation, curriculum systems, CUDA/GPU environments
Why they are there
Specialization, teaching, held-out evaluation, checkpoints, and hardware-aware model research.
Technologies / areas
C#, .NET 8, WPF, Luau/Roblox, C++/Unreal, engine plugins, local protocols
Why they are there
Project inspection, governed missions, engine integration, approvals, validation, and recovery.
Technologies / areas
C#, .NET, WPF, Windows APIs, PowerShell, USB and hardware interfaces
Why they are there
Technician diagnostics, drive validation, USB tooling, system information, and local-first assistance.
Technologies / areas
Astro, TypeScript, Vitest, Cloudflare Workers, GitHub Pages
Why they are there
Static public publishing plus the separately deployed Kayla site-guide runtime.
The grouped technical areas behind the systems above — context, not an inventory to rank.
Model learning, agent execution, and evaluation areas used where a project requires them.
Environments used for experiments and workloads. Use of a provider does not imply partnership.
Engines and environments explored where appropriate for FDS projects.
Product and platform names belong to their respective owners. A name here indicates use or investigation—not endorsement, sponsorship, certification, or partnership. Planned integrations are not treated as current support.