Knowledge Report Supply

Output Rules

• Return structured supply, not a final report narrative.
• Keep the evidence set compact and relevant.
• Preserve source names or identifiers whenever possible.
• Surface template-fit signals clearly:
  • preferred columns
  • preferred sections
  • grouped dimensions
  • report task hints
• For static-page outputs without an explicitly named custom template, provide concept-page guidance:
  • recommended sections
  • recommended cards
  • recommended charts
  • primary grouping dimension
• If coverage is weak, say so explicitly instead of padding with invented material.

Read references/supply-contract.md before producing output.

Domain Priorities

• Resume libraries: prioritize candidates, companies, projects, skills, education, timelines.
• Bid libraries: prioritize sections, response requirements, qualifications, risks, and submission materials.
• Order libraries: prioritize platforms, categories, sales metrics, inventory, forecast, replenishment, anomalies.
• Formula libraries: prioritize ingredients, strains, benefits, audiences, doses, and evidence strength.
• Contract libraries: prioritize obligations, terms, dates, deliverables, payments, and risk clauses.
• Technical or research libraries: prioritize methods, systems, modules, APIs, deployment, metrics, and evidence quality.

Failure Boundaries

• If the request is library-grounded but the scope is weak, return the best bounded evidence set and mark the gap.
• If the request is clearly outside the selected libraries, do not compensate with unrelated external content.
• Never fabricate missing evidence to satisfy a template.
• Never switch into generic freeform assistant mode.