Page actions
project template / candidate
Research study — tools
The distinct tools record for Research study. This page is proposal-only.
Record status
- Record ID
- project:research-study
- Parent lifecycle
- candidate
- Page lane
- app_features
- Lane lifecycle
- proposed
- Owner
- Not separately recorded
- Owner role
- Not separately recorded
- Owner status
- Not separately recorded
- Qualification result
- NOT RUN · held for evidence and human review
Working browser surface: Project templates & workflows — overview — Create a local project from this template and validate its forms. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.
Authoritative app_features lane tools and interfaces
Canonical tools-page assignments
- Notebook Projects (interface · required) — Owns the project grouping, lifecycle, membership ordering, linked records, and project state.
- Notebook Notes (interface · required) — Stores source-labelled evidence notes, claim excerpts, interpretations, and revision history.
- Notebook Files (interface · required) — Keeps local source-labelled file references beside records without hidden upload or protected-storage claims.
- Notebook To-dos (interface · required) — Tracks collection, review, synthesis, and approval work with due dates, priority, tags, completion, and revisions.
- Notebook Agenda (interface · required) — Displays source-bound deadlines, time blocks, conflicts, and drafted schedule changes while external writes remain held.
- Notebook Approvals (interface · required) — Holds the conclusion for human review and preserves approved, held, or needs-review state.
- Notebook Search (interface · required) — Provides local filtering and retrieval while respecting private and held partitions.
- PointGuard (interface · required) — Provides a persistent cross-app context room for current study work, linked records, and review signals.
- Notebook records (record · required) — Preserve canonical IDs, origin, locators, source SHA-256, provenance, lifecycle, tags, links, attachments, and revisions.
Only the page's admitted lane is rendered as an assignment. Other lane inventories remain source records but are not merged here. Tool kind and required/optional status are preserved.
Authoritative lane instrument assignments
Canonical tools-page assignments
No verified instrument is assigned to this tools lane.
An instrument listed only for another lane does not become a tools-page assignment.
Use boundary
- Treating an unlinked note or file reference as verified evidence.
- Confusing source excerpts with researcher interpretation or final claims.
- Allowing unresolved contradictions to disappear through filtering or project closure.
- Silent deadline changes that invalidate an existing workback.
- Assuming a named Agenda or Messages surface performs provider writes.
- Citation identifiers or locators copied incorrectly from source records.
- Sensitive research material exposed through broad local search or PointGuard context.
- Accessibility failures caused by color-only status indicators, focus loss, or inaccessible drag reordering.
- Overstating a locally drafted conclusion as externally published or qualified.
Sources and evidence
These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.
source_record:project:research-studyNotebookCollectionKind.projectNotebookTodoPayload.dueAtNotebook Agenda deadlines/workbacksNotebook records provenance and revisionsPointGuard persistent cross-app context surfaceAPP_ROUTES:/app/notebook/projects/APP_ROUTES:/app/notebook/notes/APP_ROUTES:/app/notebook/files/APP_ROUTES:/app/notebook/to-dos/APP_ROUTES:/app/notebook/agenda/APP_ROUTES:/app/notebook/approvals/APP_ROUTES:/app/notebook/search/APP_ROUTES:/app/pointguard/