Arkaik maps itself

The best proof of a map format is the tool's own anatomy, kept in it and open for you to explore.

A mapping tool that cannot map itself would be a bit suspicious. So Arkaik keeps its own anatomy in its own format: the self-map, a real bundle of Arkaik's flows, screens, data models and endpoints.

It ships as a built-in public seed project, so you can open it and wander around a product you are already using. It doubles as a tour: the journey map shows how you move through Arkaik, the system map shows what each screen stands on.

It is also a test. The validator runs against the self-map on every change, next to the other seeds, so a format change that would break a real project breaks here first.

And because Arkaik is an app plus a CLI plus an agent plugin, the self-map is where the tool meets its own edge cases, like several products sharing one graph. When the map feels awkward to keep, that is usually a sign the model needs to grow.