# Student Ownership Agreement

Student:

Mentor or support person:

Created:

Next review:

Complete one responsibility first. Add another row only when the student is
ready to assume it. The troubleshooting, privacy, and security guidance below
applies throughout; it is not a set of blank fields.

## First responsibility

Responsibility:

Student owns:

Mentor or expert owns:

Evidence of independence:

One escalation condition:

## Add responsibilities as ownership transfers

| Responsibility | Student owns | Mentor or expert owns | Evidence | Escalation condition |
|---|---|---|---|---|
| | | | | |

## Reference guidance

Before routine troubleshooting, state the expected and observed behavior,
record the starting state, form one testable hypothesis, run the smallest safe
test, and verify the result. Escalate when the risk or evidence requires it.

Discuss administrator access, account changes, paid subscriptions, security
settings, and changes that affect protected schoolwork before acting. Stop and
escalate suspected malware, account recovery, data loss, hardware failure,
private-data exposure, or an urgent institutional deadline.

- Do not share passwords, access tokens, or recovery codes.
- Use official recovery and support processes.
- Keep private course and institutional data out of unapproved services.

## Review notes — complete after evidence exists

What responsibility changed, and what evidence supported the change?