Browser workspace
BoardContext owns project discovery, active-board subscriptions, and the mutation surface shared by every view.
SYSTEM OVERVIEW
One project boundary, every route through it.
Orbicue is a Next.js App Router application backed by Firebase Authentication and project-scoped Firestore data, with server routes for privileged integrations and MCP.
The source repository is private. This public page documents the system boundaries, data ownership, and integration paths without sending visitors to an inaccessible code host.
BrowserMCP clientGitHub
Next.js routes + BoardContextUI, access checks, orchestration, integrations
projects/{projectId}members/{uid}boards/{boardId}project resources
Each surface has one clear job.
MCP clients
The public JSON-RPC endpoint validates a client identity, resolves accessible projects, and exposes bounded task tools.
GitHub integration
OAuth, webhooks, project sync, and repository context run through server routes instead of exposing provider credentials to the browser.
Project data
Projects are the shared tenancy boundary. Members, boards, goals, sprints, documents, and integration state stay project-scoped.
Project-first tenancy
Membership records live under each project and key authorization by user ID. Boards and shared resources inherit that project context. Private notifications remain account-owned.
One reactive data boundary
Views consume data through the shared board provider rather than opening independent Firestore listeners. That keeps board, list, table, calendar, timeline, analytics, and goals on the same task records.
Online and Demo Mode parity
The same product interactions work against Firestore for collaborative work and local storage for Demo Mode. Mutations deliberately preserve both paths.
Server-side integration authority
GitHub tokens, webhook processing, AI provider calls, media signing, and administrative writes stay behind server routes. Browser code receives only the result it needs.
ACCESS MODEL
Read MCP security guidance Identity opens a project, not the whole database.
Interactive users authenticate with Firebase. MCP currently uses the workspace Client ID as a bearer credential and resolves it through project membership, so it must be protected like a password.
See the system from the user side.
Open Demo Mode to explore the complete workspace without configuring a backend.