One job each
General-purpose languages can do almost anything. Ours are deliberately narrow, so each has a clear job and a clear boundary.
The languages
Seventeen languages, one stack.
Each language has one job and states what it won’t do, from the hardware up to verification and governance.
Why we designed our own
Limits in the design
Declared limits, refusals and replay are design goals of the stack, rather than something each program has to add for itself.
Less outside dependence
Our goal is to use only our own languages for company projects. We aren’t there yet: third-party languages remain part of our tooling today.
The stack
Each language works on its own. Grouping shows what each is for, not a required pipeline.
Systems & Hardware
Where software meets machines, clusters and the physical world.
Data, Knowledge & Math
How information enters a system, is related, kept and computed on.
Agents & Software
How agents reason, communicate and run, and what they are allowed to do.
Verification & Governance
How systems are tested, measured, audited and traced.
Proprietary
All Belsic languages are proprietary and used only by Belsic; they are not available for outside use. All 17 have implementation work at differing levels of maturity, from limited prototypes to broader development profiles. These descriptions summarize scope, not full specifications.