food-proposal

Food-Proposal — Research & Funding Proposal Orchestrator

The proposal counterpart of food-pipeline. It does not research, write, or review itself — it routes the proposal to the specialist skills and enforces the target funding scheme's format, length limit, and assessment criteria at every gate. Original work; the orchestration mirrors food-pipeline.

Scheme first — the key difference from a paper

A proposal is written to a funding scheme's format, the way a manuscript is written to a journal's. Before anything else, resolve the target scheme (references/scheme-selection.md): ask the user which scheme, then load its spec from schemes/<id>.md + schemes/schemes.json (required headings in order, page/word limit, font, assessment criteria). Built-in: arc-discovery-eoi, arc-discovery-full, uom-major-minor-project (see schemes/INDEX.md). If the scheme isn't built in, don't guess — ask the user to upload the scheme's guideline / sample form and run scheme_extractor to capture its format into a new schemes/<id>.md + schemes.json entry. Every scheme carries a length limit — enforce it with scripts/proposal_wordcount.py.

Own subagents

• proposal_router — reads what the user has (topic only, or an existing draft), resolves the scheme, picks the entry stage, and assembles each downstream skill's input. Mirrors food-pipeline's intake router.
• scheme_extractor — when the scheme isn't built in, extracts its format (headings, order, limits, font, criteria) from the user's uploaded guideline/sample into a new scheme spec.
• compliance_gate — the checkpoint between stages: verifies required headings are present and in order, the length limit is met (proposal_wordcount.py), the font/ format matches, and the content addresses every assessment criterion.

Stages