Stacks
Anvil Coder describes the language, framework, versions and check commands in an optional stack profile. Java with Spring Boot is the most established path. Other stacks need the appropriate build and test tools available in the execution environment.
A stack profile tells the agents which language, versions and conventions to use. It does not install missing tools in the verification environment. Before starting, confirm that the build and test commands can run with the required dependencies.
| Stack | Evidence | Before running |
|---|---|---|
| Java / Spring Boot | The most established path, used to build Anvil Coder itself. | Match Java and build-tool versions to the repository. |
| PHP / Laravel | A reference run generated a fix and test; sandbox verification was unavailable. | Provide PHP, Composer and the test runner. |
| TypeScript / Angular, Node.js, Python, Go | Can be described in a stack profile; no measured run is presented here. | Confirm dependencies and build/test commands for the project. |
Read the Laravel reference run and its toolchain limitation. A configurable profile does not mean every framework version has been tested.
The customer documentation (in German) explains how a run proceeds and how the per-run rules act. The most relevant entry points arefollowing runs andguardrails.
Once a profile is set up, it acts twice. Up front it is translated into conditions that accompany every prompt — the same mechanism as the guardrails.At the back stand the gate commands: the result has to pass them, otherwise the step does not count as done. This rear check is enabled separately — the profile acts up front as soon as it is in place; the back needs a second switch.
A rule that only acts up front is a request. One that only acts at the back comes too late. Both together are the reason a declaration becomes a commitment.
The path on which Anvil Coder itself was built, and which has accordingly been walked most thoroughly, is Java with Spring Boot in a hexagonal architecture. Whoever starts there enters known terrain.
Other stacks work through the same path — they are simply less travelled. We will tell you honestly up front where you would be the first; that is cheaper for both sides than finding out afterwards.
Stack profiles are an optional feature. Without them the system works as before — the rules then come from the requirements and the guardrails.