The space

/:owner/:name/space is the map as a plane you move through (#10444). It is linked from the map page ("The same work as a space to move through"). Its data is /:owner/:name/space.json, the same plane for an agent. In the terminal it is the space entry in the palette (src/tui/screens/space.ts): pillars with their counts, issues by state, who of the crew is on what, and the week's landings, from the same spaceOf and so the same gate as the page (a guest sees what is public, an admin everything).

Use

The MCP map tool answers view: "space" with the same spaceOf result, scoped to the caller like the page.

How it is built

space.json carries an ETag (the body's hash): a refetch after an event whose change the plane does not draw is answered 304, and the body is encoded by the server (http/compress.ts) otherwise. About 1.5 MB at forge scale before encoding.

Without script the page is the pillar list alone: the canvas, bars and scrubber show only once the script sets space-on. If the first load fails the list stays and says so. State is told by a cluster's label and position and by weight (muted as work ages), not by hue; the accent is for the crew and the controls.

Assumptions shown: the week's landed work is the closed issues the map's graph still carries (those on an edge); issues closed more than 7 days ago are not drawn. Before an issue landed, it is drawn in review, its slot there reserved by the layout (history of earlier states is not stored).

Test: test/space-model.test.ts places 12,000 issues and checks the size of the JSON (under 3 MB; the time is logged, not asserted); test/space-view.test.ts tests the client's placement, crew, hash and tap functions, which the page ships from src/web/space_view.ts; the canvas's own paint is measured by hand on a device, not in a test.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs