Every project gets
its own room.
Isolated containers. Tools load when the domain needs them, so a biology programme never carries a trading toolchain, and the reverse. The drawing is one workspace, pulled apart to read.
- Access policy: members, roles, visibility
- Tools: loaded per domain, on demand
- Mounts: storage reached by contract only
- Runtime: isolated container, small kernel
Loadable modules
Load a toolchain for the domain.
Choose a domain, then load or unload its apps. The tile lifts onto the Tools layer and its mount lights up on the layer below. Nothing else in the workspace changes.
| Module | Type | Access | State | |
|---|---|---|---|---|
| Sequence toolsReads imported sequence files. | Optional app | Workspace members | Enabled | |
| FoldingHeavy compute stays in the workspace. | Optional app | Workspace members | Enabled | |
| SimulationVersioned inputs, reproducible runs. | Optional app | Workspace members | Not loaded |
1{2 "name": "Sequence tools",3 "type": "Optional app",4 "access": "Workspace members",5 "state": "Enabled",6 "note": "Reads imported sequence files."7}- Access policy: members, roles, visibility
- Tools: loaded per domain, on demand
- Mounts: storage reached by contract only
- Runtime: isolated container, small kernel
Anatomy
What a workspace holds.
The console reads a workspace as one record. These are its real parts. Select one to see where it lives in the manifest.
1{2 "id": "biology",3 "name": "Computational Biology",4 "domain": "Computational Biology",5 "lead": "Research lead",6 "accessProfile": "Assigned members and admins",7 "team": [8 {9 "name": "A. Researcher",10 "role": "Researcher",11 "access": "Collaborator",12 "userType": "External",13 "status": "Active"14 }15 ],16 "board": [17 {18 "title": "Calibration notes",19 "owner": "A. Researcher",20 "tag": "Note"21 }22 ],23 "tasks": [24 {25 "title": "Re-run calibration",26 "status": "Queued",27 "owner": "A. Researcher"28 }29 ],30 "channels": [31 {32 "id": "general",33 "label": "general"34 }35 ],36 "collaboration": {37 "meetings": [38 {39 "title": "Weekly review",40 "host": "Research lead",41 "state": "Scheduled"42 }43 ],44 "live": [45 {46 "name": "Standup",47 "type": "Voice room",48 "state": "Standby"49 }50 ]51 },52 "folders": [53 "Imports"54 ],55 "files": [56 {57 "name": "calibration.csv",58 "format": "CSV",59 "size": "18 KB",60 "owner": "A. Researcher"61 }62 ],63 "imports": [64 {65 "source": "Manual",66 "item": "Reading list",67 "status": "Queued"68 }69 ],70 "exports": [71 {72 "target": "Partner review pack",73 "status": "Available"74 }75 ],76 "archive": [77 {78 "title": "Literature summary pack",79 "type": "Knowledge pack",80 "status": "Indexed",81 "lane": "Knowledge",82 "visibility": "Workspace members"83 }84 ],85 "versions": [86 {87 "label": "archive",88 "type": "Workspace",89 "detail": "A. Researcher indexed “Literature summary pack”."90 }91 ],92 "modules": [93 {94 "name": "Sequence tools",95 "type": "Optional app",96 "access": "Workspace members",97 "state": "Enabled",98 "note": ""99 }100 ],101 "controls": {102 "branch": "main",103 "digestEnabled": true,104 "appVisibility": "workspace",105 "exportHandoff": "Ready"106 },107 "ai": {108 "name": "Computational Biology Agent",109 "status": "Available",110 "summary": "Governed workspace AI collaborator.",111 "queue": [],112 "prompt": {113 "proposals": []114 }115 }116}Lifecycle and permissions
Who may do what, and when.
Contributing is open to everyone assigned. Changing what the workspace allows is reserved for managers.
Create
Platform administrator
A workspace is created with a name, a domain, a lead and a summary. Nothing is shared with it yet.
POST /api/workspacesInvite
Workspace manager
A named person is invited with a role and an access level. The link is single-use and expires after seven days.
POST /api/workspaces/:id/invitesConfigure
Workspace manager
Apps are enabled, previewed or disabled, controls are set, and contracts are declared for the Helper Plane.
POST /api/workspaces/:id/actionsWork
Assigned members
Notes, tasks, messages, imports and drafts. Every accepted action writes an event and reaches members live.
POST /api/workspaces/:id/actionsHand off
Assigned members
Finished work leaves through the export handoff the workspace names, and the export is recorded.
export action
Any assigned member
- Add a board note
- Create, move or complete a task
- Post a message
- Send workspace mail
- Schedule a meeting or open a room
- Create a folder
- Queue an import or create an export
- Index an archive record
- Queue an AI request
- Propose or review a prompt change
Workspace managers only
- Enable, preview or disable an app
- Update workspace controls
- Update workspace details
- Remove a team member
- Configure the workspace AI agent
- Declare helper contracts and sources
- Add access, drive and governance policies
- Add shared inboxes and routing rules
How it behaves
Questions a reviewer asks.
How isolated is one workspace from another?
What actually loads in a workspace?
Who can change what a workspace allows?
Can a programme be isolated further?
Where do files and imports go?
How are changes tracked?
Latest papers
Infrastructure
First papers are in preparation.
Each piece states what it claims and what it does not. See what the institute has published so far in Papers.
Ask for a room of your own.
Access is invite-only. Tell us what you are working on and an administrator will review it.