Foa Analysis

Parse the FOA text and extract:

• Eligibility criteria: Who can apply (institution type, country restrictions, career stage, PI requirements)
• Page or word limits: Per section and total
• Required sections: Ordered list of mandatory proposal sections
• Review criteria: Scoring dimensions and weights (e.g., Excellence 50%, Impact 30%, Implementation 20% for Horizon Europe)
• Deadlines: Submission deadline, pre-registration deadline (if any)
• Budget caps: Maximum funding amount, duration, co-funding requirements
• Special requirements: Ethics requirements, open access policy, gender dimension (EU), data management plan, consortium size requirements

3. Match Against Agency Template

Load the known agency template for validation:

uv run gw-agency info <agency> <mechanism>

Compare extracted requirements against the template. Flag any discrepancies — the FOA may have call-specific additions or modifications to the standard template.

4. Output Structured Requirements

Save the extracted requirements as foa_requirements.json in the output directory:

{
  "agency": "<agency>",
  "mechanism": "<mechanism>",
  "call_id": "<call identifier if found>",
  "deadline": "<submission deadline>",
  "eligibility": ["<criterion 1>", "<criterion 2>"],
  "sections": [
    {"name": "<section_name>", "words": <limit_or_null>, "required": true}
  ],
  "review_criteria": [
    {"name": "<criterion>", "weight": <percentage>}
  ],
  "budget": {
    "max_total": <amount_or_null>,
    "max_years": <N>,
    "currency": "<EUR|RON>"
  },
  "special_requirements": ["<requirement 1>", "<requirement 2>"],
  "notes": "<any call-specific deviations from standard template>"
}

5. Human Checkpoint

Human checkpoint: Present the extracted requirements to the PI for confirmation. Specifically ask:

1. Are the eligibility criteria correct? Is the PI eligible?
2. Are there any additional requirements not captured from the FOA?
3. Does the budget cap and duration match their expectations?
4. Are the deadlines correct?

Incorporate any corrections before proceeding.

Notes

• For EU agencies, pay special attention to: ethics issues table, gender dimension requirements, open science / open access mandates, and consortium composition rules.
• For Romanian agencies (UEFISCDI), check for language requirements — some calls require the proposal in Romanian.
• If the FOA is in a language other than English, extract requirements and present them in English for processing, noting the original language.

Error Handling

• --foa path missing or unreadable: Prompt the PI to paste the key requirements as text; skip extraction and proceed from parsing.
• gw-pdf extraction fails (scanned, encrypted, corrupt): Fall back to manual paste; do not guess requirements.
• URL fetch fails: Retry once, then ask the PI for an alternate URL or local copy of the FOA.
• Agency manifest missing (gw-agency info fails): Continue extraction but skip the template-matching step; note in the output that call-specific deviations were not cross-checked.
• Output directory not writable: Abort with the path and a permissions hint before writing foa_requirements.json.
• Ambiguous or conflicting requirements in the FOA: Record both interpretations in the notes field and escalate to the PI at the human checkpoint rather than silently picking one.