Give the address of a GitHub or GitLab repository, or of a folder in one. The browser draws the diagrams, lists the behavior views and shows the knowledge files kept in its .dev/ folders, and you walk from one folder into the next by clicking the parts in the drawings.
Or open retro-games as an example. The views follow the skills and the knowledge catalogue of human-assisted software development.
A private repository needs you to sign in with GitHub, or an access token. Give its address and the browser will ask; a token pasted here stays in this browser and goes to that host alone.
What a folder is made of, and what each part depends on.
Where the code runs: clients, hosts, processes and stores.
The types a folder declares and how they relate.
Every state a machine can be in, and what moves it on.
Who does what, step by step, and what happens when it goes another way.
What a part of the system can do, and who may ask for it.
The behavior offered, its outcome and the limits on it.
The callable entrypoints: what each does, who may call it and how it can fail.
A person's way toward a goal over time, stage by stage, across touchpoints.
What a folder knows about itself: vision, backlog, decisions, requirements, delivery and operation.