Page actions
field guide / candidate
Grant dossiers — related jobs
The distinct related jobs record for Grant dossiers. This page is proposal-only.
Status: proposedLifecycle: candidate
Record status
- Record ID
- field-guide:grant-dossiers
- Parent lifecycle
- candidate
- Page lane
- plan
- Lane lifecycle
- proposed
- Owner
- Tilly
- Owner role
- Not separately recorded
- Owner status
- Not separately recorded
- Qualification result
- NOT RUN · held for evidence and human review
Working browser surface: Field guides — documentation — Inspect the guide and persist local checkpoints. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.
Related Agent job handoffs
Handoff record requirements
The guide may supply evidence, checkpoints, and failure context to a job. The receiving job retains ownership and must record its own decision, approval, and receipt.
- source-labelled grant opportunity record
- grant dossier project record
- evidence records with source locator and SHA-256 where available
- draft narrative or response records
- deadline and workback to-do records
- review and reconciliation notes
- approval receipt record
- Grant dossier
- Funding opportunity record
- Source-labelled evidence notes
- File references and source locators
- Instrument qualification record
- Evidence reconciliation record
- Draft application materials
- Website claim review
- Approval receipts
- Bounded to-dos
Ownership boundary
The guide supports these jobs without importing their package descriptions, becoming the job owner, or gaining independent authority.
- A grant name or related job may be mistaken for proof that an opportunity is active, applicable, eligible, or qualified.
- Copied requirements can lose source context, version, cutoff time, or amendment history.
- Unsupported narrative claims may enter drafts through paraphrase or stale evidence.
- Conflicting sources may be silently reconciled instead of preserved and escalated.
- An internal workback date may be mistaken for the funder's deadline.
- Local approval may be mistaken for external submission or funding approval.
- Prototype routes may be mistaken for connected production features.
- Sensitive application material may be placed in an unapproved file or visibility surface.
- Accessibility failures may hide status, deadlines, errors, or held states.
Sources and evidence
These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.
source_record:field-guide:grant-dossiersagents/index.html#tillyObserved native contract: Notebook collections and lifecycleObserved native contract: Notebook deadlines and workback payloadObserved native contract: provenance, canonical IDs, source locators, SHA-256, revisions, and attachmentsObserved native contract: PointGuard context surface and specialist-app record ownershipObserved app routes supplied for Guth Hub, PointGuard, Notebook, Business, and related review surfacesAllowed verified-instrument directory supplied; no instrument selected because this dossier procedure has no demonstrated calculation requirementfield-guide:grant-dossiers/app/notebook/field-guides//app/notebook/notes//app/notebook/files//app/notebook/approvals//app/notebook/paper//app/notebook/to-dos//app/notebook/agenda//app/notebook/agent-logs/date-duration-calculatorcountdown-days-until-timer