Reference
Use this page to look up the main terms and access concepts used in the internal pilot.
Key terms
Section titled “Key terms”| Term | Meaning |
|---|---|
| Culsma PAWS | The complete user-facing product, including AI workflows, web/app interfaces, workspaces, data services, and MCP connection. |
| Workspace | The top-level area that contains members, Lab Projects, samples, storage, and Analytics Projects. |
| Active workspace | The workspace currently used to authorize an AI or app request. |
| Lab Project | The operational project that contains laboratory samples and their context. |
| Analytics Project | A reusable analysis environment with separate datasets, roles, and lifecycle. |
| Dataset | A user-facing collection of related analytics tables or views. |
| Table | Structured analytics data organized into rows and columns. |
| View | A reusable, read-only result defined from analytics data. |
| MCP connection | The secure connection that allows an AI agent to use Culsma PAWS tools. |
| Change preview | A proposed write operation shown before it is applied. |
| Audit ID | An identifier used to trace an analytics query, load, or governed operation. |
Analytics roles
Section titled “Analytics roles”| Role | Main capability |
|---|---|
| Reader | Discover and query Analytics Project data. |
| Writer | Query data and add or update rows in existing datasets. |
| Publisher | Create or change schemas, tables, columns, and views. |
| Workspace Owner | Create Analytics Projects, link Lab Projects, and manage analytics roles. |
One person may have more than one analytics role. Linking a Lab Project does not copy its members or permissions into an Analytics Project.
MCP token permissions
Section titled “MCP token permissions”| Permission | Used for |
|---|---|
lab.read |
Read samples, projects, subjects, tags, and storage context. |
lab.write |
Preview and apply supported laboratory-data changes and imports. |
lab.analytics.read |
Discover and query authorized Analytics Project data. |
lab.analytics.write |
Create or maintain authorized analytics structures and data. |
The token permission and the user’s workspace or project role must both allow the operation.
Pilot inputs and clients
Section titled “Pilot inputs and clients”- Sample intake accepts structured CSV or Excel files.
- Analytics table loading uses CSV data.
- The current Getting Started flow covers OpenAI Codex and Claude Code.
- Other MCP clients require organization-specific validation and setup.
This reference describes the current internal pilot. Availability may also depend on the features and permissions enabled for your organization.