Idea
How Yichus works
How the program, tools, and engine fit together.
The program is written in Bosatsu, whose compiler gives Yichus a structure it can inspect, while browser and server engines run the program and provide its external operations.
1. A data app’s Why view
Expand any result into the steps and values that produced it; nobody writes the explanation by hand.
Code & run Read and edit the data app’s two source files
2. Lenses and diagrams
Each lens draws the facts for one question about a program’s shape, and redraws when the source changes.
Code & run Edit the stock-allocation rule and redraw its dependencies
Your Bosatsu program
One typed program structureCompiled expressions, types, and source locations
- See the structureDefinitions and dependencies.
Layers, reuse, copied bodies. - Explain a runInputs, values, and effects.
Why did this result happen? - Check a guaranteeA property and its assumptions.
Evidence or a counterexample.
3. Service checks and execution
A Bosatsu service declares routes, handlers and policies; the engine serves HTTP and runs their database operations. Read why this helps a small language support useful applications →
Analyzable language / Bosatsu
The endpoint program
Routes, typed handlers, and policies.
For example: read the caller’s notes.
Conventional language / Host runtime
The server engine
Accept requests, execute handlers,
and interpret their storage operations.
Code & run Run and repair the Notes handler
4. Frontend updates from compiled bindings
The UI compiler knows which state feeds which part of the page, so an update patches only that part.
Code & run Read and run the counter
Yichus is an experimental project; the evaluation records include unsuccessful results.
Ask your agent about anything here; it has the detail.