Guth
NewsDocs
Page actions
View as Markdown ↗
Explore MCP tools ↗

project template / candidate

Research study — field guides

The distinct field guides record for Research study. This page is proposal-only.

Status: proposedLifecycle: candidate

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.

Related field-guide records

  • /app/notebook/field-guides/

Source-proposed guide paths are references, not proof that those paths resolve.

Operating sequence

  1. Create the project record with canonical ID, origin, source references, provenance, revision, lifecycle, tags, and visibility.
  2. Complete intake and assign project owner, research lead, reviewer, and approver.
  3. Approve scope, exclusions, assumptions, source-quality rules, contradiction rules, and stop conditions.
  4. Create milestones and deliverables with owners, dependencies, acceptance criteria, and due dates.
  5. Enter the final decision date and generate a workback with internal review, evidence freeze, analysis, drafting, and buffer deadlines.
  6. Register dependencies and create due items for each blocking handoff.
  7. Collect source-labelled notes and file references; preserve source locators, hashes where available, and revision history.
  8. Create evidence records linking each material claim to its supporting source and record contradictory evidence explicitly.
  9. Review findings against acceptance criteria; mark unsupported, conflicting, or incomplete findings as held.
  10. Submit scope changes, material findings, and final closure for human approval.
  11. Run closure checks for milestone completion, evidence coverage, citation completeness, open contradictions, and overdue dependencies.
  12. Close, extend, or hold the project with a preserved receipt and follow-up tasks.

Handoff boundary

  • A named route may be a local prototype or index rather than a connected feature.
  • Unverified sources, missing locators, stale revisions, or unsupported summaries may produce false findings.
  • Contradictory evidence may be suppressed unless the form requires explicit linking and resolution status.
  • Overdue work can be obscured by silent rescheduling or unclear ownership.
  • Agent suggestions may be mistaken for approved findings or completed work.
  • File references must not imply that files were uploaded, copied to protected storage, or made authoritative.
  • Agenda and message surfaces may draft changes or communications but must not imply external writes or final sends.
  • Research conclusions may be overgeneralized beyond the declared population, time period, geography, or source boundary.
  • Sensitive notes or attachments may be exposed if visibility and audience fields are omitted.
  • Accessibility failures in long, multi-section forms may prevent review or completion.

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/