Reading the map

What each view shows, which way the arrows point, and why nothing on the page is a guess.

The views

Architecture: The components of a repository and how they connect. Each component has its own page with what it sends data to, what it receives from, and its documentation.
Data flow: What moves along those connections: the data a relationship declares, per link.
System architecture: Every repository on one map. In a workspace it can be filtered to some repositories, with what they connect to dimmed, and the filter is part of the link you share.
Documentation: The markdown each repository sent, rendered in one style.

The map is a desktop-first layout, usable down to 1024 pixels wide; below that the diagram scrolls inside its own area.

The way data moves: An arrow points in the direction data moves, whichever end declared the relationship.
Two ends, one edge: When both components declare the same link, the two declarations collapse into one edge and both are kept as its sources.
Different links stay different: Several relationships between the same two components stay several edges.
Self links: A relationship from a component to itself is counted and never drawn.

Per component: A component keeps its hue and icon everywhere, from the list to the system map.
Per repository: In a workspace, every component a repository owns shares its hue, in the order repositories were connected, so adding a repository recolours nothing.

Positions: Nothing in kimtu.yaml says where a component goes. The layout is computed, layered left to right in the direction data moves, and never stored.
Invented fields: Only fields the manifest carries are drawn. A field you left out is absent, not guessed.
Staleness: Nothing marks a page out of date; the commit and date a page carries are the thing to read.
Your source code: Kimtu never reads it. The map is rendered from kimtu.yaml and the markdown you chose to send.