Bdc Report Writer

BDC report writer

1. Agree on audience, objective, expected length and source scope before authoring.
2. Keep local-only files local. Read only user-selected files and assign neutral aliases such as LOCAL-01; never expose absolute paths, credentials or unrelated file content.
3. For large sources, split at heading/paragraph boundaries. Create one evidence card per chunk with facts, definitions, figures, limitations and the alias plus page/heading. Reduce evidence cards hierarchically when they exceed the client model context. Never truncate the tail of a source silently.
4. Design an outline first. For each section, retrieve only relevant evidence cards and keep source_refs; distinguish sourced facts, model inference and recommendations.
5. Use short prose, explicit assumptions, measurable findings and a useful conclusion. Never fabricate citations or claim that an unread source was reviewed.
6. Prefer a structured visual (flow, cycle, comparison, hierarchy, timeline) with 2–6 labels. Add accessible alt_text. Add illustration_prompt only when a real illustration would add value; image generation is optional and must not block the report.
7. Call mcp_generate_report with the authored sections. Review returned Markdown, Mermaid, citations and visual_coverage before sharing or uploading derived text to LMS.
8. Report which sources stayed local and exactly what derived material, if any, was sent to BDC LMS or an external model provider.