# Personal System Charter

Created:

Next review:

This charter describes what I need my student computing system to do and the
constraints that should guide my choices. It is a working document, not a test.
Complete the four **required now** sections first. Use `unknown`, `not
applicable`, or `return later` when that is the honest answer.

## First pass

### 1. Work to protect — required now

What work would be difficult or impossible to replace? Consider drafts, notes,
data, code, feedback, and final submissions.

My answer:

### 2. What must be rebuildable — required now

What applications, tools, settings, course add-ons, or project packages should
you be able to restore on a new or repaired computer?

Section 1 is for hard-to-replace content. This section is for replaceable tools
and setup. **Do not repeat the files named in the previous section.**

My answer:

### 3. Hard constraints — required now

What platform, budget, course requirement, privacy rule, accessibility need,
internet limitation, shared-device rule, or time limit must the system respect?

My answer:

### 4. One current priority — required now

Name one improvement that would protect the work, improve rebuildability, or
respect a hard constraint. Do not choose a tool yet.

My answer:

## Extend during later decisions

### Tasks that are confusing or repetitive — required when evaluating a change

What do you avoid, repeatedly search for, or perform manually in the same way?
Describe the problem before choosing a tool.

My answer:

### What I want to manage independently — optional for later review

What should you be able to understand, perform, verify, and troubleshoot by the
next review?

My answer:

### Complexity I am choosing not to add — required when considering it

Which tools, services, customizations, or automations are unnecessary for now?
What would need to change before you reconsider them?

My answer:

### Evidence that the system is working — collect after the action

What observable tests would show that the system is reliable and understandable?
Examples include finding a file, restoring a test file, rebuilding a project,
or explaining a routine process.

My answer:

## Later review

After testing the first priority, keep it, revise it, or add at most two more.

1.
2.
3.

### Questions to revisit

Record any `unknown` or `return later` answer that could change a decision.

-

> Safety reminder: Do not record passwords, API keys, access tokens, recovery
> codes, or private course data in this file.