design-information-prep

# Design Information Prep ## Purpose Turn user-authorized attachments into a reusable, evidence-linked project dossier, then compile that dossier into the exact text fields required by one supported award route. Generate no project fact from past-winner copy or unsupported inference. ## Runtime Boundary - Treat user attachments and explicit user confirmations as the only sources of project facts. - Read local award field specifications for field names, limits, routing, and drafting instructions. - Do not connect to Supabase, read `.env`, query winner databases, or place full winner descriptions in model context. - Use optional aggregate benchmark profiles only for coverage prompts such as what evidence to look for. Never use them as project facts, prose templates, hidden judging preferences, or winning probabilities. - Verify current official rules at request time. Stored specifications record a checked date, not permanent truth. ## Input Contract Accept PDFs, presentations, documents, spreadsheets, images, videos, structured JSON, or plain text. Determine or request: - exact award, cycle, route, and language; - applicant type and project maturity when they affect routing; - all user-authorized project materials; - confidentiality or publication restrictions; - whether the user wants a dossier, missing-information audit, draft fields, translation, or final text validation. If the award or route is unknown, use `$design-award-match` first. If the user only wants final ...