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

job / candidate

Grant research and drafts — field guides

The distinct field guides record for Grant research and drafts. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID
job:tilly:grant-research-and-drafts
Parent lifecycle
candidate
Page lane
docs_urls
Lane lifecycle
proposed
Owner
Tilly
Owner role
Pointguard and independent reviewer
Owner status
WORKING
Qualification result
NOT RUN · held for evidence and human review

Working browser surface: Agent jobs — builder overview — Inspect the package and stage a local project. 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 or update the research brief and project link.
  2. Capture each opportunity from a source-labelled record; preserve locator, provenance, revision, and source hash when available.
  3. Extract explicit eligibility, dates, deliverables, and restrictions into a qualification record.
  4. Create a deadline workback with source deadline, time zone, internal review deadline, correction buffer, and submission-owner checkpoint.
  5. Collect applicant and project evidence in Notebook notes and linked file references; do not imply hidden upload or protected storage.
  6. Map each material claim to a citation and record contradictory or missing evidence.
  7. Run qualification checks and mark unresolved requirements as unclear or held rather than guessing.
  8. Draft application sections using only reviewed or clearly labelled provisional evidence.
  9. Use the claim examiner and citation checks to identify unsupported, overstated, or conflicting language.
  10. Submit the dossier and draft to an independent reviewer; Tilly must not approve her own evidence.
  11. Record revisions, decisions, receipts, and handoff state in the agent log and approvals surface.
  12. Hold final publication, funding commitments, credential access, and edits to another agent’s source until the designated owner or human approves.

Handoff boundary

  • Grant pages and requirements may change; preserve source revisions and access dates.
  • A directory or index may be mistaken for an official funder source; require an official source locator for qualification.
  • Eligibility language may be ambiguous; do not convert interpretation into fact.
  • Draft impact, capacity, budget, or outcome claims may exceed receipts.
  • Conflicting sources may be silently reconciled; preserve both and escalate.
  • Deadline time zones and submission channels may be misread.
  • Sensitive applicant, credential, or financial information may be placed in an unprotected local record; minimize collection and keep credential access held.
  • A draft may be mistaken for a submitted application or public claim.
  • Tilly may be pressured to approve her own evidence; enforce independent review.
  • Native app routes are prototypes or indexes and do not prove connected web behavior.

Sources and evidence

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

  • agents/index.html#tilly
  • source_record:job:tilly:grant-research-and-drafts
  • native contract: records preserve canonical IDs, origin, source locators, source SHA-256, provenance, revision, lifecycle, tags, links, attachments, and record revisions
  • native contract: PointGuard is a persistent cross-app context surface; specialist apps remain execution and canonical-record owners
  • native contract: current GuthHub app routes are local prototypes or indexes; provider, credential, database, customer, publication, and production effects are held
  • source record existing tools: Pointguard; Instrument catalog; Claim examiner; Citation checks
  • source record existing guides: Instrument packets; Qualification records; Grant dossiers; Public-claim routes
  • source record principal gates: Final publication; Funding commitments; Credential access; Changes to another agent's source
  • source record never rules: Approve her own evidence; Hide a contradiction; Turn a draft into a public claim
  • job:tilly:grant-research-and-drafts
  • Observed native contract: Notebook records and revisions
  • Observed native contract: PointGuard persistent cross-app context surface
  • Observed app routes: /app/pointguard/, /app/notebook/field-guides/, /app/notebook/approvals/, /app/notebook/paper/, /app/notebook/agent-logs/