Grant application — deadlines

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.

Deadline and workback rules

• Store every external deadline with date, time, timezone, source locator, and source date.
• Require an internal target earlier than the external deadline; if no buffer is supplied, mark the workback as incomplete rather than inventing one.
• Derive workback tasks from the final packaging deadline backward and record each duration assumption.
• Require review and approval windows before the internal final-readiness check.
• Block a milestone from complete when its required evidence, attachment, approval, or owner is missing.
• Flag a deadline as at risk when a blocking dependency is unresolved at its needed-by date.
• Preserve every deadline revision with old value, new value, editor, timestamp, and reason.
• Treat missed deadlines as a visible failure state requiring owner, impact, recovery decision, and approval.
• Do not schedule or perform external submission, provider writes, publication, or customer communication automatically.
• Do not mark the application submitted unless a human records an externally verified submission receipt; this project template defaults to non-submission.
• Require an explicit deadline date, time, and timezone before generating a workback.
• Display the source locator beside every deadline and mark unsourced dates as unclear.
• Generate milestones backward from the deadline: requirements confirmed, outline, first draft, budget draft, review, revision freeze, package check, and human submission decision.
• Never schedule a task after the hard deadline unless it is explicitly marked late or recovery planning.
• Show overdue, due today, upcoming, blocked, and held states using text as well as color.
• If the deadline changes, preserve the prior revision and require confirmation before recalculating dependent workback dates.
• Do not create recurrence automatically; recurrenceCandidate remains a human-review signal.

Workback sequence

1. Create the project record and assign a human owner.
2. Add the opportunity source, locator, provenance, revision, and source-labelled requirements.
3. Record the deadline with timezone and create a workback.
4. Break the application into narrative, budget, attachment, and review records.
5. Draft each section in Paper and link it to source notes and project evidence.
6. Add local file references beside records; do not imply hidden upload or protected storage.
7. Create review to-dos with priorities, due dates, tags, and human-review signals.
8. Run a requirements checklist and mark each item complete, missing, unclear, or held.
9. Route proposed decisions through Approvals and preserve local receipts.
10. Package a local export or draft handoff only after human review; keep submission held.

Scheduling records

• milestone records
• deadline to-dos
• dependency records
• owner assignments
• workback schedule
• workback to the stated deadline

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
• NotebookCollectionKind.project
• NotebookTodoPayload.dueAt
• Notebook Agenda deadlines/workbacks
• Observed native contract: project_and_field_guide_collections
• Observed native contract: deadlines
• Observed native contract: records
• Observed native contract: pointguard
• Observed app routes: /app/notebook/projects/
• Observed app routes: /app/notebook/to-dos/
• Observed app routes: /app/notebook/agenda/
• Observed app routes: /app/notebook/approvals/
• Observed app routes: /app/notebook/paper/
• Observed app routes: /app/notebook/files/
• Observed app routes: /app/notebook/field-guides/
• Observed app routes: /app/pointguard/
• project:grant-application
• 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/