Warning
A major rework is ongoing. Many components and workflows may be incomplete or non-functional. Feature descriptions, setup examples, and availability claims across the documentation are stale and may describe earlier implementations or planned behavior. They do not establish current functionality. Check the relevant repository's recent changes, release evidence, and known issues before adopting a component.
FS-GG is a collection of F# tools and libraries for application development. Its scope includes workspace templates, agent-assisted development, GitHub coordination, and UI, game, audio, and networking components. Availability and integration vary by component during the rework.
Note
The FS-GG Unified Development Roadmap tracks the rework. Its current progress report links completed evidence, active work, and remaining requirements. A completed implementation does not by itself establish that a component is published, configured, or working in a particular workspace.
These areas describe the platform's scope, not a verified list of working features:
- Workspace creation: templates, repository setup, and provider integration.
- Spec-driven development (SDD): specifications, implementation, validation, and delivery.
- Agent coordination: GitHub boards, task ownership, parallel work, and cross-repository dependencies.
- Formal models: adoption of Quint, an executable specification language for modeling state, transitions, and properties.
- Application components: UI, game, audio, networking, and optional governance packages.
- Telemetry: development activity and configured runtime observations; coverage depends on collection and publication being active.
- Documentation index — guides and reference material; check dates and implementation evidence.
- Architecture — component relationships and design boundaries.
- Workspace templates — template source, releases, and issues.
- SDD — development lifecycle source, releases, and issues.
- Repositories — component-specific code and maintenance activity.
- Telemetry dashboard — published observations; inspect source timestamps and coverage before drawing conclusions.
Board automation can act on issues and Project data. Restrict modification rights to trusted actors. Public GitHub content remains untrusted input; the trust boundary defines how agents must handle it.
MIT.