Arckit Grants

Find the project directory in projects/ (user may specify name/number, otherwise use most recent). Scan for existing artifacts:

MANDATORY (warn if missing but proceed):

• ARC-*-REQ-*.md in projects/{project}/ — Requirements specification
  • Extract: sector, budget range, objectives, TRL indicators, organisation type, compliance requirements
  • If missing: warn user to run $arckit-requirements first, but proceed using $ARGUMENTS as the project description

RECOMMENDED (read if available, note if missing):

• ARC-*-STKE-*.md in projects/{project}/ — Stakeholder analysis
  • Extract: organisation type, stakeholder funding expectations, partnership opportunities
• ARC-*-SOBC-*.md in projects/{project}/ — Business case
  • Extract: existing funding assumptions, budget gaps, cost-benefit data

OPTIONAL (read if available, skip silently if missing):

• ARC-000-PRIN-*.md in projects/000-global/ — Architecture principles
  • Extract: technology constraints that affect grant eligibility (e.g., open source requirements)

Step 2: Build Project Funding Profile

Extract from requirements and user arguments:

• Sector: health, defence, education, environment, digital, transport, energy, etc.
• Organisation type: public sector, SME, charity, academic, NHS trust
• TRL level: 1-9 (estimate from project maturity if not stated)
• Funding range sought: from budget/cost data or user input
• Project timeline: from project plan or requirements dates
• Key objectives: 2-3 bullet points summarising the project

Step 3: Read external documents

• Read any external documents listed in the project context (external/ files) — extract funding-relevant information
• Read any enterprise standards in projects/000-global/external/ — extract existing funding policies or constraints
• Citation traceability: When referencing content from external documents, follow the citation instructions in .arckit/references/citation-instructions.md. Place inline citation markers (e.g., [PP-C1]) next to findings informed by source documents and populate the "External References" section in the template.

Step 4: Research UK Grant Bodies

Use WebSearch and WebFetch extensively. Do NOT rely on general knowledge alone. Search for current, open funding rounds.

Search across these categories, skipping bodies clearly irrelevant to the project sector:

For each body:

1. Search for their current funding opportunities page
2. WebFetch the results to get current open calls
3. Filter for relevance to the project sector and TRL

360Giving/GrantNav: Search grantnav.threesixtygiving.org with project-relevant keywords (e.g., "digital government", "appointment booking", "NHS digital"). GrantNav aggregates published grant data from 200+ UK funders — use it to discover funders not in the list above and to find historical grants that indicate active programmes in the project's domain.

Step 5: Gather Grant Details

For each relevant grant found, collect via WebSearch/WebFetch:

• Grant name and programme
• Funding body
• Funding range (min-max)
• Eligibility criteria (organisation type, sector, TRL, co-funding requirements)
• Application deadline (specific date or "rolling")
• Application process summary (stages, timeline)
• Success rate (if published)
• URL to application/guidance page

Step 6: Score Eligibility

Rate each grant against the project funding profile:

• High — project meets all eligibility criteria, sector and TRL align, organisation type qualifies
• Medium — project meets most criteria, may need minor adaptation or partner involvement
• Low — partial match, significant gaps in eligibility or sector mismatch

Include a rationale for each score explaining what matches and what gaps exist.

Step 7: Read Template and Write Report

1. Read the template (with user override support):

   • First, check if .arckit/templates/grants-template.md exists in the project root
   • If found: Read the user's customized template (user override takes precedence)
   • If not found: Read .arckit/templates/grants-template.md (default)

2. Before writing, read .arckit/references/quality-checklist.md and verify all Common Checks pass. Fix any failures before proceeding.

3. Generate the document ID: ARC-{PROJECT_ID}-GRNT-{NNN}-v1.0 where {NNN} is the next available sequence number. Check existing files with Glob: projects/{project-dir}/research/ARC-*-GRNT-*.md

4. Write the complete report to projects/{project-dir}/research/ARC-{PROJECT_ID}-GRNT-{NNN}-v1.0.md using the Write tool (not inline output — avoids token limit).

Sort grant opportunities by eligibility score (High first, then Medium, then Low).

Step 8: Spawn Knowledge

Skip this step if the user passed --no-spawn in the original command arguments.

After writing the main grants report, extract reusable knowledge into standalone tech note files.

Slug Generation Rule:

1. Take the grant programme name (e.g., "Innovate UK Smart Grants")
2. Convert to lowercase: "innovate uk smart grants"
3. Replace spaces with hyphens: "innovate-uk-smart-grants"
4. Remove special characters
5. Remove leading/trailing hyphens
6. Collapse multiple consecutive hyphens to single

Examples:

• "MHRA AI Airlock" → "mhra-ai-airlock"
• "Wellcome Trust Digital Technology" → "wellcome-trust-digital-technology"
• "NIHR i4i Programme" → "nihr-i4i-programme"

Tech Notes:

For each grant programme researched in depth (2+ substantive facts gathered):

1. Check whether a tech note already exists: Glob for projects/{project-dir}/tech-notes/*{grant-slug}*
2. If no tech note exists: Read the tech note template at .arckit/templates/tech-note-template.md and create a new file at projects/{project-dir}/tech-notes/{grant-slug}.md. Populate from research findings.
3. If a tech note exists: Read the existing note and apply these merge rules per section:
   • Summary: Update only if understanding has significantly changed; otherwise keep existing
   • Key Findings: Append new findings; mark outdated ones with "(superseded as of YYYY-MM-DD)" rather than removing
   • Relevance to Projects: Add this project if not already listed
   • Last Updated: Update to today's date

Traceability:

Append a ## Spawned Knowledge section at the end of the main grants document listing all created or updated files:

## Spawned Knowledge

The following standalone knowledge files were created or updated from this research:

### Tech Notes
- `tech-notes/{grant-slug}.md` — {Created | Updated}

Deduplication rule: Always search for existing coverage before creating. Use filename glob patterns: projects/{project-dir}/tech-notes/*{topic}*. Slugs must be lowercase with hyphens.

Step 9: Return Summary

Return ONLY a concise summary including:

• Total grants found and breakdown by score (High/Medium/Low)
• Top 3 matches with funding amounts and deadlines
• Total potential funding range (sum of recommended grants)
• Nearest application deadlines
• Number of tech notes created/updated (unless --no-spawn)
• Suggested next steps: $arckit-sobc (Economic Case), $arckit-plan (project plan), $arckit-risk (grant-specific risks)

CRITICAL: Do NOT output the full document. It was already written to file. Only return the summary.

Important Notes

• All funding data must come from WebSearch/WebFetch — do not use general knowledge for grant amounts, deadlines, or eligibility
• Markdown escaping: When writing less-than or greater-than comparisons, always include a space after < or > to prevent markdown rendering issues
• Deadlines change frequently — always note the date of research and warn the user to verify deadlines before applying
• UK-only scope — this agent covers UK funding bodies only

Suggested Next Steps

After completing this command, consider running:

• $arckit-sobc -- Feed grant funding data into Economic Case
• $arckit-plan -- Create project plan aligned to grant milestones
• $arckit-risk -- Add grant-specific risks (rejection, compliance, reporting)