One graph, many products
An app and its back office share one graph, without the admin screens looking 'missing on iOS'.
Real projects rarely ship one product. There is the app and its back office, the end-user side and the author side, or a web app plus a CLI plus an agent plugin. They share data models and endpoints, so they belong in one graph, but they do not ship to the same places.
So Arkaik lets a project declare its products, each with its own list of platforms. Your diary app can run on web, iOS and Android while its admin lives on the web only. Flows and screens say which product they belong to; the platforms a screen can target are limited to what its product ships on.
Data models and endpoints never have to pick a side. Their product is worked out from the screens that use them, which means an endpoint card can tell you it is used by both the app and the admin.
The payoff is honest numbers. The delivery board stops counting admin screens against an Android column they will never join, and the acceptance matrix only shows the columns that can actually fill up.