I am releasing three large software systems I developed privately over several years as a solo effort, without institutional backing, corporate sponsorship, or a formal engineering team.
These are not concepts or mockups. They are real, deployable systems. They install through Docker, Helm, or Kubernetes, start successfully, and produce observable results. They are currently running on cloud infrastructure. That said, they should be understood as unfinished foundations, not polished products.
Together, the ecosystem totals roughly 1.5 million lines of code.
The Platforms
ASE — Autonomous Software Engineering System
ASE is a closed-loop platform for code creation, monitoring, evaluation, and iterative self-improvement. Its purpose is to automate parts of the software lifecycle by producing artifacts from high-level tasks, monitoring outcomes, feeding corrections back into the process, and refining itself over time. It runs today, but agent tuning is uneven, some features are incomplete, and output quality varies by configuration.
VulcanAMI — Transformer / Neuro-Symbolic Hybrid AI Platform
VulcanAMI is an AI system built around a hybrid architecture combining transformer-based language modeling with structured reasoning, orchestration, and governance. The goal is to address weaknesses in purely statistical models by integrating symbolic and system-level controls. It deploys and operates, but reliable transformer integration remains a major challenge.
FEMS — Finite Enormity Engine
FEMS is a practical multiverse simulation platform for large-scale scenario exploration, counterfactual analysis, and causal modeling. It aims to apply techniques often confined to research settings. It runs and produces results, but its models require expert mathematical tuning and should not be treated as scientifically validated.
Current Status
All three systems are:
Deployable
Operational
Complex
Incomplete
Known limitations include rough user experience, incomplete documentation in places, limited formal testing compared to production software, feasibility-driven architecture, incomplete security hardening, and the presence of bugs.
Why Release Now
Further progress would benefit from outside expertise and perspective. As a solo developer, I lack the resources to fully mature projects of this scale. This release is not tied to funding, a product launch, or an institutional program. It is simply the opening of work that exists, runs, and remains unfinished.
About Me
My name is Brian D. Anderson. My primary career has been as a fantasy author, not a traditional software engineer. I am self-taught, began learning software systems later in life, and built these platforms independently on consumer hardware.
That background will invite skepticism. It also explains the character of the work: ambitious in scope, uneven in polish, and driven by persistence rather than formal process. These systems were built because I wanted them to exist.
What This Is — and Is Not
This is:
A set of deployable foundations
A snapshot of ongoing independent work
An invitation to explore, critique, and improve
A record of what has been built so far
This is not:
A finished product suite
A turnkey solution
A claim of breakthrough performance
A promise of support or roadmap
If you explore the code, assume some parts are over-engineered, others under-developed, naming may be inconsistent, and much internal knowledge is not yet externalized. If any part is useful or interesting, you are free to build on it under the license terms.
The systems exist. They run. They are unfinished. If they prove useful to someone else, that is enough.
— Brian D. Anderson
Repos:
The Code Factory: https://github.com/musicmonk42/The_Code_Factory_Working_V2.git
These are not concepts or mockups. They are real, deployable systems. They install through Docker, Helm, or Kubernetes, start successfully, and produce observable results. They are currently running on cloud infrastructure. That said, they should be understood as unfinished foundations, not polished products.
Together, the ecosystem totals roughly 1.5 million lines of code.
The Platforms
ASE — Autonomous Software Engineering System ASE is a closed-loop platform for code creation, monitoring, evaluation, and iterative self-improvement. Its purpose is to automate parts of the software lifecycle by producing artifacts from high-level tasks, monitoring outcomes, feeding corrections back into the process, and refining itself over time. It runs today, but agent tuning is uneven, some features are incomplete, and output quality varies by configuration.
VulcanAMI — Transformer / Neuro-Symbolic Hybrid AI Platform VulcanAMI is an AI system built around a hybrid architecture combining transformer-based language modeling with structured reasoning, orchestration, and governance. The goal is to address weaknesses in purely statistical models by integrating symbolic and system-level controls. It deploys and operates, but reliable transformer integration remains a major challenge.
FEMS — Finite Enormity Engine FEMS is a practical multiverse simulation platform for large-scale scenario exploration, counterfactual analysis, and causal modeling. It aims to apply techniques often confined to research settings. It runs and produces results, but its models require expert mathematical tuning and should not be treated as scientifically validated.
Current Status
All three systems are:
Deployable
Operational
Complex
Incomplete
Known limitations include rough user experience, incomplete documentation in places, limited formal testing compared to production software, feasibility-driven architecture, incomplete security hardening, and the presence of bugs.
Why Release Now
Further progress would benefit from outside expertise and perspective. As a solo developer, I lack the resources to fully mature projects of this scale. This release is not tied to funding, a product launch, or an institutional program. It is simply the opening of work that exists, runs, and remains unfinished.
About Me
My name is Brian D. Anderson. My primary career has been as a fantasy author, not a traditional software engineer. I am self-taught, began learning software systems later in life, and built these platforms independently on consumer hardware.
That background will invite skepticism. It also explains the character of the work: ambitious in scope, uneven in polish, and driven by persistence rather than formal process. These systems were built because I wanted them to exist.
What This Is — and Is Not
This is:
A set of deployable foundations
A snapshot of ongoing independent work
An invitation to explore, critique, and improve
A record of what has been built so far
This is not:
A finished product suite
A turnkey solution
A claim of breakthrough performance
A promise of support or roadmap
If you explore the code, assume some parts are over-engineered, others under-developed, naming may be inconsistent, and much internal knowledge is not yet externalized. If any part is useful or interesting, you are free to build on it under the license terms.
The systems exist. They run. They are unfinished. If they prove useful to someone else, that is enough.
— Brian D. Anderson
Repos: The Code Factory: https://github.com/musicmonk42/The_Code_Factory_Working_V2.git
VulcanAMI: https://github.com/musicmonk42/VulcanAMI_LLM.git
FEMS: https://github.com/musicmonk42/FEMS.git