Source: https://guthlabs.ai/docs/project-templates/research-study/forms/ project template / candidate # Research study โ€” forms The distinct forms record for Research study. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: project:research-study **Parent lifecycle**: candidate **Page lane**: forms **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. ## Proposed form sections Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth. ### Intake Establish why the study exists, who owns it, and what decision or question it supports. - project title - research question - decision or use supported - requester - project owner - research lead - reviewer - audience - priority - proposed start date - target completion date - success statement - source references - sensitivity or visibility level ### Scope and boundaries Define included work, exclusions, assumptions, and stop conditions before research begins. - in-scope questions - out-of-scope questions - population or subject boundary - time period - geographic boundary - source-quality requirements - contradiction-handling rule - citation requirements - assumptions - known unknowns - stop conditions - change-control rule ### Milestones and deliverables Break the study into reviewable outcomes with owners and acceptance criteria. - milestone name - milestone description - deliverable - milestone owner - planned start - due date - preceding milestone IDs - acceptance criteria - status - completion evidence - reviewer - revision notes ### Deadlines and workback Create deterministic due items and calculate work backward from the target completion date. - final decision date - internal review deadline - draft findings deadline - evidence freeze date - source collection deadline - analysis deadline - buffer duration - calendar or time-zone note - priority - recurrence candidate - completion state - revision history ### Dependencies and handoffs Expose work that cannot proceed until another record, person, or decision is available. - dependency ID - dependent milestone - dependency type - blocking record or task - dependency owner - needed-by date - status - fallback plan - escalation date - handoff receipt ### Ownership and authority Make responsibility explicit while preserving human review for consequential decisions and external effects. - project owner - research lead - evidence curator - analyst - reviewer - approver - backup owner - responsibility statement - authority boundary - handoff rule - approval required before progression ### Tools and guides Declare which native surfaces and procedures are used without implying connected provider behavior. - designated Notebook surface - designated PointGuard room - field guide reference - notes workflow - files reference workflow - to-do workflow - agenda draft workflow - messages draft workflow - approval workflow - agent-log review requirement - held external effects ### Evidence and citations Capture source-backed claims, provenance, contradictions, and review receipts. - evidence ID - claim or finding - source record ID - source locator - source SHA-256 - origin - access or observation date - supporting excerpt or note - confidence label - contradictory evidence IDs - resolution status - citation text - reviewer - revision ID - attachment or file reference ### Reviews and approvals Require explicit human decisions for scope changes, findings, and closure. - approval ID - decision requested - proposal summary - affected records - approver - review deadline - status: Needs review/Approved/Held - conditions - decision receipt - decision date - reopen trigger ### Risks and failure states Record foreseeable problems, detection signals, mitigations, and escalation paths. - risk ID - risk statement - category - likelihood - impact - risk owner - trigger - mitigation - contingency - review date - status - blocked milestones - escalation recipient ### Closure Confirm what was completed, what remains unresolved, and whether the record may be archived or held. - closure status - final deliverable reference - completed milestones - open questions - unresolved contradictions - evidence completeness check - citation completeness check - approval receipt - lessons learned - follow-up tasks - retention or visibility decision - closure owner - closure date ### Accessible state contract - Every field requires a visible and programmatic label. - Required and optional fields must be stated in text. - Invalid entries require an actionable message linked to the field. - Blocked and Held states remain visible without relying on color alone. ## Supporting documentation fields These fields come from the app_features lane and remain separate from the primary operating form. ### Study identity Define ownership, scope, and the bounded research question. - title - short_description - owner - research_question - scope_inclusions - scope_exclusions - target_audience - project_tags ### Method and evidence rules Make the evidence and contradiction controls explicit before collection. - source_types_allowed - inclusion_criteria - exclusion_criteria - minimum_source_count - citation_style_note - contradiction_handling_rule - reviewer_required ### Deadline and workback Set a final deadline and derive reviewable intermediate work. - final_deadline - timezone_label - milestone_dates - buffer_days - task_durations - task_dependencies - priority ### Linked records Attach local source-labelled records without implying external authority. - source_record_ids - file_record_ids - note_record_ids - existing_todo_ids - agenda_block_ids ### Conclusion and approval Prepare a bounded conclusion and hold it for human review. - draft_conclusion - limitations - open_questions - approval_status - reviewer_notes ## Required or proposed record references No record existence is asserted by this documentation page. - project record - source-labelled notes - source-labelled file references - to-dos with due dates - milestone records - dependency records - evidence records - risk records - approval records - closure record - research question record - source reference records - evidence note records - contradiction records - citation records - to-do records - agenda workback records - approval record - agent log record ## Sources and evidence These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment. - `source_record:project:research-study` - `project:research-study` - `NotebookCollectionKind.project` - `NotebookTodoPayload.dueAt` - `Notebook Agenda deadlines/workbacks` - `Observed native contract: records provenance and revision fields` - `Observed native contract: PointGuard cross-app context surface` - `Observed app route: /app/notebook/projects/` - `Observed app route: /app/notebook/to-dos/` - `Observed app route: /app/notebook/agenda/` - `Observed app route: /app/notebook/approvals/` - `Observed app route: /app/notebook/field-guides/` - `Observed app route: /app/notebook/agent-logs/` - `Observed app route: /app/notebook/notes/` - `Observed app route: /app/notebook/files/` - `Observed app route: /app/pointguard/` - `Notebook records provenance and revisions` - `PointGuard persistent cross-app context surface` - `APP_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/`