Global Developer Network

Backed by:  Full Stack Engine
Pushed forward by: Christopher Hogan and a federated council of advisors.

 "We are re-inventing the development process for Full Stack applications with an emphasis on business requirements, domain driven operations, security-first specifications with conformance to industry-standard best practices, and test coverage. "

Global Developer Network (GDN)
Will launch on OpenSourceStacks.com

Open source provider of Full Stack Engine specifications utilizing the open Stack Standard API.  (stackStandard.com to launch Feb 1st).

1. Must be architected default secure, end-to-end encryption for LSP, and have solid IDE support for auto-completion, peeking, following classes and interfaces, etc.
2. All artifacts must be stored on encrypted disks, with encryption at rest and encryption on actions for data stores, and for data transport to archival storage.  For certain regulations we must comply with Gov Cloud, CloudHSM, and their equivalents on various clouds.
3. All code that transforms or replaces other code with RAC (Result As Code) functionality must be signed and encrypted with GPG or with DCT (Docker Content Trust) for Docker artifacts.
4. The language must work with LSP (Language Server Protocol) and be pluggable to support future  languages through "thin" layer modules in various package managers that are open source.  The thin loaders will spawn docker containers to bootstrap the CLI itself.
5. All core binaries must be released with CICD, pass commit checks, and be reviewed by the community as well as expert peers.  All CICD systems must use existing Peach technology (or equivalent) that Gitlab has been working on and musts support their DAST & Fuzzing systems for collaborative purposes to avoid overlap.
6. The system itself must describe queries, because the instructions will constantly change.
7. A decentralized, multi-az, multi-region, global deployment of the API specification must be made available.  
8. A CLI musts be available which generates code stubs and scaffolds large stack descriptions into  helm charts, and with each stack represented with a  `.stack` file written in FDSL, and a `.stack.gpg.pub` file providing a public key signature for verification by our CLI.
9. The initial stack backends must conform to Helm3 standards
10. The repository must provide an Open API 3 specification.
11. The repository must provide a Kubernetes CRD for enterprise deploys and on-premise.
12. The advisory council must provide expert security oversight for the project.
13. Telemetry data must not be collected on any of our products, ever.