Notebook and scientific context
Labbook entries, memory, and capturing scientific decisions.
Status: Available
In OVAITY, the researcher-facing “notebook” is the labbook, not a Jupyter notebook UI.
Labbook scopes
| Scope | Route | Use |
|---|---|---|
| Personal | /hub/labbook, /hub/labbook/[entryId] | Personal scientific notes |
| Project | /hub/[projectId]/labbook | Project chronological memory |
| Lab | /labs/[labId]/labbook, .../[entryId] | Lab-level notebook with review flows where enabled |
Creating entries
- Open the relevant labbook (personal, project, or lab).
- Create a new entry and capture experimental context, observations, and links to ongoing work.
- Attach files to a notebook entry when you need the source next to the note.
- Save and, where lab review is configured, follow the lab’s review process.
Connecting to projects and studies
- Project labbook entries belong to the project workspace.
- There is no Study entity to attach entries to; use project context, samples, datasets, and memory decisions instead.
Decisions and rationale
Use Memory tabs:
- Project:
/hub/[projectId]/memory - Lab:
/labs/[labId]/memory - Organization:
/organizations/[orgId]/memory
Memory is for durable decisions and rationale. Project, lab, and organization memory are separate. There is no partner connection that reads this memory.
Linking files, analyses, and other objects
Labbook and Ovaition flows support provenance links connecting artifacts, insights, and narrative outputs where those features are enabled in your environment. Exact link UI varies by surface.
Search and AI context
- Workspace header search and the assistant chat widget can use accessible project context subject to RBAC.
- The assistant does not bypass permissions. Cross-space retrieval is limited to projects you can access.
- Do not assume the AI “knows everything” in your organization.