A model writing Go spends a real fraction of its output on braces, semicolons and import blocks, and every one of those is a chance to produce something that will not parse. Removing the surface syntax removes that class of failure entirely. What you trade is everything a human reader gets from source code — you cannot review opcodes, and no one else can maintain them. Interesting as a direction, not as a dependency.
A bytecode-style language designed to be written by a model rather than a person. There is no syntax to get right — the model emits opcodes as JSON and the server compiles them.
- Opcode JSON in, a built artefact out — a Go binary, a React app, an iOS or Android scaffold, or a compose file
- The build runs server-side, so what comes back is a URL to the artefact rather than source to compile yourself
Run the server; the model supplies the opcodes. Licence is unspecified.
Build from source — clone the repository and build it, then point your client at the binary