Idea
The idea behind the experiments
Why an analyzable language?
To find out how a program computed a result, whether a handler can read another user’s data, or where the same logic is repeated, you usually read all of its code or trust a description of it. When an agent wrote the program, that description is the agent’s own summary.
The idea is borrowed. A type checker reads a program’s structure to answer a question before it runs, and Bazel’s Starlark keeps build rules separate from the engine that executes them. Yichus applies the same split to applications. Reusable engines in a conventional language handle execution and integrations, and code written in Bosatsu, a typed functional language, supplies the calculations, handlers, and policies. Our tools then read the compiled Bosatsu to explain results, map dependencies, and check permissions.
The engine keeps the libraries a young language lacks; its interface decides what the tools can inspect. See the service engine boundary.
Each check answers its own question and depends on what the engine promises. Choose a check by the question it answers.
Yichus is an experiment; the evaluation record keeps the unsuccessful comparisons too.
Ask your agent about anything here; it has the detail.