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

project template / candidate

Grant application — tools

The distinct tools record for Grant application. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID
project:grant-application
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, linked records, and evidence view.
  • Notebook Notes (interface · required) — Stores source-labelled research, requirements, assumptions, and open questions.
  • Notebook Paper (interface · required) — Owns draft narrative and document revisions.
  • Notebook Files (interface · required) — Stores local file references and custody metadata without hidden upload.
  • Notebook To-dos (interface · required) — Tracks workback tasks, deadlines, recurrence candidates, completion, priorities, and review signals.
  • Notebook Agenda (interface · required) — Shows source-bound deadlines, review blocks, conflicts, and held schedule changes.
  • Notebook Approvals (interface · required) — Separates proposed, approved, and held decisions with receipts.
  • PointGuard (interface · required) — Projects the current grant workspace, open loops, deadlines, linked notes, and held effects across Guth surfaces.
  • source-labelled project records (record · required) — Preserves canonical IDs, provenance, source locators, revisions, links, and lifecycle.

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

An instrument listed only for another lane does not become a tools-page assignment.

Use boundary

  • A source-labelled deadline may be copied incorrectly or lack a timezone.
  • A draft may be mistaken for an approved or submission-ready application.
  • Unverified eligibility or funder requirements may be presented as authoritative.
  • Sensitive organizational, financial, or personal information may be placed in local records or file references.
  • A workback may create false confidence when dependencies, holidays, or reviewer availability are unknown.
  • Budget estimates may be mistaken for accounting, tax, legal, or funder-approved figures.
  • External send, upload, calendar write, publication, or submission could occur without deliberate human action.
  • PointGuard projection could be confused with canonical record ownership.
  • Color-only status indicators could hide overdue, blocked, or held work.
  • Large attachments or malformed records could fail to persist and cause unnoticed data loss.

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

  • source_record:project:grant-application
  • project:grant-application
  • NotebookCollectionKind.project
  • NotebookTodoPayload.dueAt
  • Notebook Agenda deadlines/workbacks
  • Notebook records provenance, source locators, revisions, lifecycle, tags, links, and attachments
  • PointGuard persistent cross-app context surface
  • APP_ROUTES:/app/notebook/projects/
  • APP_ROUTES:/app/notebook/to-dos/
  • APP_ROUTES:/app/notebook/agenda/
  • APP_ROUTES:/app/notebook/approvals/
  • APP_ROUTES:/app/notebook/paper/
  • APP_ROUTES:/app/notebook/files/
  • APP_ROUTES:/app/pointguard/