Guide

Lenses / System map

The building blocks of a system map.

A system map draws a whole program on one page, and Yichus computes every mark from the program’s code. Each kind of thing has one mark and one place, so an empty place means Yichus looked and found none. Ask your agent what any mark means.

The places, left to right

Callers on the left, the program’s openings on the wall, shared steps in the middle, and the database, the model and the network on the right.

Every mark

Each sample is cut from a real map on this site.

Handed in, or built where it is used

The same routes twice: first handed the database, so a blue rail runs along the bottom; then each route building its own handle, so the rail is gone.

Loading the notes-api system map.

Loading the notes-api-local system map.

A service with many routes

Problemsapi has more routes than fit one to a line, so routes with the same marks share one thick line with a count.

Loading the problemsapi system map.

A program and its engines

The review desk keeps its rules in a pure program, and an engine performs what the program asks for. The struck opening is a request no engine performs.

Loading the review desk system map.

A journey

This is one shared step in Icetakes, opened on its own. Each route that goes through it comes in on the left. Tap the program’s name to see all of Icetakes.

Loading the Icetakes journey.

Ask your agent about anything here; it has the detail.

Where this fits

What this is about: Lenses and diagrams