Skip to content

The services in space: each a star, what it serves its moons, comets along each link - #58

Merged
ngodzik merged 1 commit into
mainfrom
services-space
Nov 8, 2026
Merged

ngodzik merged 1 commit into
mainfrom
services-space

Conversation

@ngodzik

@ngodzik ngodzik commented Nov 8, 2026

Copy link
Copy Markdown
Owner

The services view now opens in 3D, in the universe's space, as the plan and the database do, and shows every service at once rather than one in the middle.

  • Each service is a star coloured by what it is: blue an API, violet MCP tools, orange an app, cyan a cloud resource, grey outside the project, pale an image used as it is. It is larger the more it serves and the more it is linked. The routes it serves (coloured by method) or the tools it offers are moons around it; past a dozen, one grey moon stands for the rest.
  • Those that reach no other gather at the heart; the others stand in shells around it, each outside what it reaches, near those of its repository or folder. Services that reach each other, directly or around a loop, share a layer.
  • Each link is an arc in the colour of its way (blue OpenAPI, violet MCP, yellow HTTP, cyan cloud), comets running along it from the service that reaches to the one reached, more for a link that carries more.
  • Pointing at a service lights its links, with what each carries on a label a click away, and names what it serves around its ring. A click glides the camera to it and shows it whole on the right, as flat; the names move to the left. A link's label shows the link.
  • 3D / 2D beside the title gives back the flat view, one service in the middle; the summary says who is in the middle only there.

Shared with the plan and the database, in space: the layering (loops sharing a layer), room on the right for details, and long names cut in the middle, which the plan's file names now use too. In the plan and the database, the names around the body chosen go to its right, the details covering the left.

Tried in the window on a public project's services: their routes, a link's label, the details, and 2D.

Tests cover the layering (a body a layer above what it rests on, a loop sharing one), the services' scene (a service outside what it reaches, its routes or tools as moons with one for the rest, the largest the one serving and linked the most, each kind its colour, the same services laid out once) and the cutting of long names.

🤖 Generated with Claude Code

…along each link

The services view now opens in 3D, in the universe's space, as the plan
and the database do, and shows every service at once rather than one in
the middle: each is a star coloured by what it is (blue an API, violet
MCP tools, orange an app, cyan the cloud, grey outside the project),
larger the more it serves and the more it is linked, the routes or tools
it serves moons around it. Those that reach no other gather at the heart;
the others stand in shells around it, each outside what it reaches, near
those of its repository or folder. Each link is an arc in the colour of
its way, comets running along it from the service that reaches to the one
reached, more for a link that carries more.

Pointing at a service lights its links, with what each carries on a label
a click away, and names what it serves around its ring. A click glides to
it and shows it whole on the right, the names moving to the left; a link's
label shows the link. 3D / 2D beside the title gives back the flat view,
one service in the middle.

Services that reach each other, directly or around a loop, share a layer;
the layering moved to `space`, with the camera's room for details on the
right and long names cut in the middle. In the plan and the database the
names go right of the body chosen, the details covering the left.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ngodzik
ngodzik merged commit fc28d0b into main Nov 8, 2026
5 checks passed
@ngodzik
ngodzik deleted the services-space branch November 9, 2026 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant