Skip to article
DOCS
DashboardProduct
Browse documentation
DocsWorkspaces & rooms
CONCEPTS

Workspaces & rooms.

How the campus, rooms, desks, tasks, managers, and Markdown plans fit together.

Product guideAEXGrid / Gridspawn LLC
On this page

The campus is the operating view

The campus is one connected canvas rather than a stack of cards. Pan and zoom, select an occupied desk to inspect its agent, or select an empty desk to open the provider wheel for that room.

Room position, size, name, color, and desk layout persist locally. Moving or resizing a room does not restart its agents; Tidy rooms restores automatic placement and fits the canvas.

Workspace and room hierarchy

THE WORKSPACE MODEL LIVE PRODUCT STRUCTURE
WorkspaceThe bigger picture
ROOM 01
ManagerCoordinates
WorkerWorker
ROOM 02
ManagerCoordinates
WorkerWorker
The hierarchy is implemented; the diagram is not a limit on room or agent counts.
PartResponsibility
WorkspaceSelected folder, overall topology, persisted configuration, and workspace-manager scope.
RoomA named visual group with desks, workers, an optional room manager, and capacity.
DeskA retained launch/session position. Stopped agents remain visible until retired.
RosterThe same running instances as the campus; both surfaces select the same agent.

Four durable destinations

DestinationPurpose
CampusRun and inspect agents in the visual room layout.
TasksCreate, assign, track, review, reopen, and cancel bounded work.
ManagersConfigure workspace and room managers, policies, scheduling, and workload.
PlansEdit workspace Markdown plans with revision-aware saves and task links.

Plans and tasks stay connected

Plans are ordinary Markdown files under plans/ in the selected workspace. Tasks can pin up to eight links as required or supporting implementation specifications, deliverables, or evidence.

Required unfinished plans block completion unless a manager or user records a reasoned waiver. Missing files, changed revisions, stale edits, and reopened required work stay visible.

Bounded by design

AEXGrid bounds active and retained agents, tasks, terminal and transcript history, provider frames, manager snapshots, tool payloads, and receipts. Reaching a bound produces an explicit refusal instead of accepting unbounded state.

KEEP EXPLORING

Search AEXGrid documentation

Explore the documentationLOCAL SEARCH

Copy this link

Your browser did not allow automatic copying. Select and copy the address below.