Architecture
Services, stores and boundaries. Every box that owns code carries the path it owns.
Open it on its own →tlk-truss
Architecture diagrams bound to real code. The drawings below are the tool's own output — one HTML file each, no network, no build step. Press Edit inside any of them: the whole engine ships in the page, so the diagram lays itself out again as you change it.
The part nobody else does
Every node can name the code it stands for. When that code moves or disappears, the diagram stops being a picture and starts being a failing build.
$ truss check docs/architecture.truss --ci
✗ docs/architecture.truss:14 E400 "ledger" is bound to src/ledger/**, which matches nothing
1 binding(s) no longer resolve
$ echo $?
1The four views
Sequence
One checkout, message by message, in the order the source lists them.
Open it on its own →Data flow
A pipeline read left to right; sources and sinks are drawn slanted.
Open it on its own →Lifecycle
What an order can be, including the state that loops back on itself.
Open it on its own →