Synthetic Demo Output
Source-grounded content intelligence report
This sample report shows the public-safe output pattern: retrieved evidence, visible source labels, and restrained claims based only on synthetic source notes.
Generated Report
Questions and cited evidence
What source-grounding and citation practices does the workflow need?
- Assessment Review Cycle Planning Notes, segment 1: The assessment team wants a repeatable review cycle that turns unstructured meeting notes into action items. The workflow should collect notes, normalize the language, segment the material by source, and preserve citations back to the original source.
- Assessment Review Cycle Planning Notes, segment 2: The first report should answer which concepts need reteaching, which items need revision, and which follow-up artifacts should be created. The report should avoid overclaiming and cite supporting source notes.
What workflow controls should remain under teacher or reviewer judgment?
- Feedback Workflow Retrospective, segment 1: The strongest results came when the rubric was explicit and the workflow returned structured evidence before generating student-facing language.
- Feedback Workflow Retrospective, segment 2: Teachers edited the language before release, and the next version should separate private grading notes from student-facing feedback.
What public safety rules govern the demo corpus?
- Curriculum Search Notes, segment 2: Public examples must be synthetic or public-license material and must not include student names, grades, private school documents, internal course links, or raw transcripts from private meetings or classes.