Topoo
Desktop documentation home for the Topoo work surfaces and the shared TopooUI system.
Topoo is the board that defines the core product framing of the system.
The Topoo section explains the product and its shared system configuration before a reader enters a solution board:
Aboutexplains what Topoo is and why the product is split into distinct boardsConfigurationmaps the authority levels where shared system settings belongMCPdefines how external execution clients connect to Topoo capabilitiesAPIdefines the automation and control-plane boundary
The boards that follow are the concrete solution lanes and implementation lanes:
toAgentfor agent interaction and orchestrationtoWorkfor document and artifact flowstoProjectfor project architecture and execution structuretoMemoryfor recall, persistence, and schema-facing memory surfacesTopooUIfor the shared UI foundation and docs primitives used across the product
Topoo desktop docs are organized by work surface. Use the top navigation to jump between product boards, and use TopooUI for the shared interface and documentation system rules.
Chat surface documentation for agent conversations, orchestration, and output flows.
Document surface guidance for work artifacts, editing flows, and publishing structure.
Project surface docs for project headers, delivery structure, and execution views.
Memory surface docs for recall, schemas, persistence views, and retrieval contracts.
Shared UI foundation, component reference pages, docs primitives, and styling patterns.
Private cloud control-plane concepts for projects, Nodes, resources, deployments, and operating state.
Current structure
- Topoo: desktop-level documentation home.
- About / Configuration / MCP / API: product definition and shared system configuration.
- toAgent / toWork / toProject / toMemory: board-specific documentation lanes.
- Topoo Cloud: the private cloud control-plane model and infrastructure product language.
- TopooUI: the shared UI and document system reference library.
How to read this system
Use Topoo first when the question is product-level:
- why the product is split the way it is
- how conversation becomes durable system truth
- how documentation, project, and execution relate
- how the boards relate to one another
- which ideas are core framing versus local implementation
Enter a solution board when the question becomes surface-specific:
toAgentfor conversation and operator interactiontoWorkfor document creation and publishingtoProjectfor project-centered architecture and executiontoMemoryfor memory-facing product surfaces
Use TopooUI when the question is about shared interface language, docs primitives, and reusable rendering patterns.
Next build lane
Start filling each board with concrete page flows while keeping reusable UI content under TopooUI.