# Education Data Flow Artifact

Effective Date: February 27, 2026

This artifact explains how session data, user data, course data, and
session artifacts move through Sukma across institution-managed and
independent learner workflows.

## Institution-Managed Flow

1. Learner, educator, host, and agent activity is recorded inside the governed session context.
2. Audience questions are stored as governed session records and normalized into lifecycle status records.
3. Session artifacts such as examples, assessments, whiteboards, and summaries are created as part of the learning workflow.
4. Host or agent actions update question status, instructional artifacts, and session state for review and follow-up.
5. The institution's retention policy is applied to governed conversation content, including learner, host, educator, and agent conversation records stored in session events.
6. After the retention window, governed conversation payloads can be redacted while metadata remains available for audit history.
7. If the institution requests an explicit purge, Sukma can remove governed conversation records, audience queries, examples, assessments, whiteboards, and session summaries for the selected scope.

## Independent Learner Flow

1. An independent learner runs a personal session.
2. Session interactions and a summary are generated.
3. The learner can optionally add verified summary recipients.
4. Personal-account privacy and retention policies apply.

## Design Principles

- Institutions receive governance and accountability for student-facing activity and learning artifacts.
- Independent learners receive privacy controls without institution-style governance.
- Continuity is supported by summaries and structured records rather than indefinite raw-message storage.