Capstone Charter Template

Module 10, Lesson 10.1 · frozen-scope worksheet · produces /capstone/capstone-charter.md

Save this as: /capstone/capstone-charter.md. Freeze at end of Lesson 10.1 after passing the Capstone scope check with 7/7.

Use it again: re-read at the top of every build session in Lessons 10.2–10.5. Amendments go below Section 6, dated and signed.

Audience = only you. Three components, three shapes. Freeze makes change a decision.

The charter is the binding scope for Lessons 10.2 through 10.5. Narrowing is free; enlarging requires a dated amendment and, if it crosses a posture line, the reviewer’s sign-off.

Header

Student:

Started: Frozen:

Reviewer (parent or peer):

Binding scope for Lessons 10.2–10.5. Amendments below this line are dated and signed.

Section 1 — One-sentence purpose

What the system does, in one sentence

Written for a reader who has never heard of your life. Present tense. No more than one sentence. Example: “My capstone summarizes my open browser tabs every Sunday evening and turns them into a one-page weekly reading plan I review Monday morning.”

Section 2 — Audience

One sentence naming yourself as the sole consumer

Explicitly state at least one cross-household write or public-output write the system will NOT do. Example: “The one-page plan goes to a folder I review. The system does not auto-post to any shared channel, does not auto-send email to anyone, and does not write to my family calendar.”

Who consumes the output:

What the system does NOT do (at least one real “does not”):

Section 3 — Components

Three components, at least three different shapes

For each, four fields: name, shape, one-sentence job, tool. Shape must be one of: scheduled/automated, coding/build, research-or-inbox, custom skill/plugin. Tick one shape per row.

#	Name	Shape	One-sentence job	Tool
1		☐ scheduled/automated ☐ coding/build ☐ research-or-inbox ☐ custom skill/plugin
2		☐ scheduled/automated ☐ coding/build ☐ research-or-inbox ☐ custom skill/plugin
3		☐ scheduled/automated ☐ coding/build ☐ research-or-inbox ☐ custom skill/plugin
4		☐ scheduled/automated ☐ coding/build ☐ research-or-inbox ☐ custom skill/plugin

Row 4: optional additional component. Three components is the default. More components = more surface area.

Section 4 — Data

Highest data class per component, with routing rule

For each component, the highest data class it touches (public / personal / sensitive) and the routing rule that follows from the Module 9 posture. Sensitive routes local; the others may route cloud.

#	Highest data class	Routing rule
1	☐ public ☐ personal ☐ sensitive	☐ cloud ☐ cloud ☐ local
2	☐ public ☐ personal ☐ sensitive	☐ cloud ☐ cloud ☐ local
3	☐ public ☐ personal ☐ sensitive	☐ cloud ☐ cloud ☐ local

Section 5 — Out of scope

What the capstone will NOT do

Three to seven items. At least one must be a real temptation you rejected — a public-output feature you wanted, a cross-household write you almost built, a scope-creep component you considered.

At least one real temptation you rejected — not just filler. If the whole list is obvious ceiling-stuff, the scope exercise didn’t land. Go back and name the one you actually wanted to build.

Section 6 — Signature and commitment

Student:

Date:

Reviewer (parent or peer):

Commitment (read and sign):

I will operate this system for seven consecutive days under the Module 9 posture before freezing. I will not auto-publish output to any audience beyond myself. I will amend this charter in writing (dated and signed below) rather than change scope silently during the build.

Student signature:

Reviewer signature / initials:

Amendments

Dated, signed edits go here

Narrowing amendments do not require reviewer sign-off; enlargement amendments do. Date every line.

This template accompanies Lesson 10.1 of AI Architect Academy. The three-shape component rule, the audience-equals-you constraint, and the freeze are concept. Component names and tool choices are recipe.