Schoolhouse

Grades 9–12

College tracks

One project, four years. Pick a track and keep the same inquiry. The done bar each year is something a second person can check. Cryptography aims use the computer science track; the adversary work lands in grade 12.

Print this page for a paper log. Only Computer science, grade 12, will print.

Grade 12 this week — Computer science

Give a classmate one hour and a closed copy of a password check or a toy cipher you wrote. Tell them the goal in one sentence: produce an accepted password they were not given, or read a message without the key. Write whether they did it. If they did, change one thing and say what. The target is your program, not a live system.

Log for this week

Type every field (or print and write). Then hand the log to a second person and ask them to rebuild from it alone.

Pass: a second person rebuilds from your log without asking what you meant. Fail: they have to ask, or they cannot get a comparable result — rewrite the log.

Or send from this page (works without a mail app):

Could they rebuild without asking you?

Logs also reach hello@contact.schoolhouse.space.

What you send with the application

What you send

The application is this project. By the time you apply, the file has these parts:

Grade 9 — start the project

Grade 9 — start one project

You are on one track. The project lasts four years. This year you start it and keep a log. The log is the start of the file you will send. Do not open a second project.

Every week, do four things inside that project:

  1. Compute a quantity with units, state the uncertainty, and say what decision it supports.
  2. Write one claim, two reasons, and one real objection. About one page.
  3. Read one short original — a figure and its caption, a statute section, a schematic, or a specimen — and write what it says, separate from a summary.
  4. Add to the log.

Finish these rungs on the First Principles ladder. Each one has a gate. The rung is done only when the gate is done.

  1. Instructions a machine could follow
  2. Loops and branches
  3. Variables and state
  4. Function as a black box
  5. Balancing equations
  6. The coordinate plane
  7. Python: syntax and types
  8. Python: files and automation

School courses beside the project: algebra and geometry, and a first lab science, usually biology.

Computer science

Write a specification in sentences, then a program that meets it. A classmate chooses an input you did not use. The log includes a script that reads a real file from the project, reports something you did not already know, and runs on a second file without an edit.

Cryptography is not a separate track. If that is your aim, stay on this project: the specification still comes first, and by grade 12 a classmate tries to break a piece you designed (a toy cipher, a password check, a signature, or an access rule) on your own system in a closed setting — not on a live network.

Done when the classmate’s input is in the log with the result the specification promised and the result the program produced.

This week. Specification, in sentences: the program reads a text file of one number per line, prints how many numbers it read, their sum, and the mean, and refuses a file that contains a word. Write that before you write the program. A classmate supplies a second file you have not opened. The log records what the specification promised and what the program printed.

Log for this week. Date. Specification sentences, written before any code. Your file’s count, sum, and mean. Classmate’s file name. What the specification promised for that file. What the program printed. Where they disagree.

Teacher guide

Grade 9 — teacher guide

One student, one track, one project. Do not assign a second project. The “this week” task in the lesson is the required start, not an example to skip.

Ladder. Rungs 1–8 for every track except pre-law. Pre-law does rung 1 and the memo.

What to cut. Renderings, extra clinical hours, mock-trial travel, and a second app. The log and the done bar in the lesson stay.

Admission. The log is the record. Do not build a separate activities list this year.

Example of a finished week (files are made up unless a trial folder exists; the student must run their own). Date: 2026-09-12. Specification written first. Own file: count 4, sum 10, mean 2.5. Classmate file: samples-b.txt. Specification promised: count, sum, mean, or refuse a word. Program printed: count 3, sum 9, mean 3.0. Disagreement: none for that file. Word-file test refused as specified. A completed trial with real files lives in content/college-tracks/trials/cs-week-1/.

Grade 10 — predict, then revise

Grade 10 — predict, then revise

Same project as grade 9. This year you write the prediction before the next result, and you revise after someone disagrees. The first prediction stays in the log after you revise.

Every week, inside that project:

  1. Predict a number with units, measure it, and write the gap. The first prediction stays visible.
  2. Revise one claim after someone disagrees. Keep the strongest objection.
  3. Annotate one short original. Quote the sentence, line, or feature that does the work, separate from your summary.
  4. Add both results to the log.

Finish these rungs:

  1. Exponents and their inverse
  2. Logarithmic scale
  3. Polynomials and roots
  4. Complex numbers
  5. Deduction
  6. Proof technique
  7. Boolean algebra
  8. Counting
  9. Sets
  10. Arrays, lists, dicts, and Big O

School courses beside the project: advanced algebra and trigonometry, into precalculus, and chemistry with a lab.

Computer science

Extend the specification to include inputs that must fail. Write the tests in a separate file from the program. A partner runs tests you did not write. Any claim that the program is correct has to use its assumption, not wave at examples.

Done when the bug log quotes the specification and the actual result for at least one failing test, and the repair is a change you can point to.

This week. Add one sentence to the specification: a file that contains a word must stop with an error and must not print a mean. Put that case in a test file separate from the program. Run it. In the bug log, quote the specification sentence and the line the program actually printed. Repair one thing, and point to the change.

Log for this week. Date. New specification sentence. Test file name. What the program printed. What you repaired. Line that shows the change.

Teacher guide

Grade 10 — teacher guide

The prediction is written before the measurement or the visit. A revision that hides the first claim is not done. The first claim stays visible.

The “this week” task in the lesson is the required start for that grade.

Ladder.

Rungs 9–18.

What to cut. A new topic that abandons last year’s question. One change between the two results, not a redesign of everything.

Grade 11 — let someone break it

Grade 11 — let someone break it

Same project. Someone outside your household tries to break the result. Their paragraph stays in the log. That person is the one who can write the letter.

Before you register for grade 12, write three lines from the course list your desired college publishes: courses you will have finished, courses still missing, and the term you will take each missing one. Add a missing course around the project. Do not drop this track’s mathematics, lab line, or memo to make room for an elective.

Every week, inside that project:

  1. Use a rate, an accumulation, or a comparison, with units and the uncertainty, on the project's claim.

  2. Write a timed page a stranger could grade. Answer the other side in the text.

  3. Cite one paper, case, dataset, or specification. A textbook restatement does not carry the claim.

  4. Put the outside reader's paragraph in the log before you answer it.

  5. Limits

  6. The derivative

  7. Rules of differentiation

  8. The chain rule

  9. Integration and the fundamental theorem

  10. Series and convergence

Also finish:

  1. Recursion
  2. Trees and heaps
  3. Sorting and searching under constraint

School courses beside the project: precalculus finished and calculus started, and physics.

Computer science

State an invariant or write a proof for one piece of the program, on a claim you have not been shown worked. Separate the base case and the inductive step, and use the assumption. If the project is a recursive structure, a tree, or a search with a budget, that structure has to meet a time or space limit you wrote down first.

Done when a test that would violate the invariant is in the project, and the proof or the code changed because of it.

This week. Write one invariant for the file program: after each line, the running total equals the sum of the numbers read so far. State the base case, the empty file, separately. Add a test that would make the invariant false if the code is wrong. If the test fails, change the proof or the code, and point to that change.

Log for this week. Date. Invariant. Empty-file base case. Test that would falsify it. Result. Proof or code change, with the line pointed out.

Teacher guide

Grade 11 — teacher guide

The outside reader is not the household. Their objection goes in the log.

The course-list check happens before grade 12 registration. It does not replace the project or the track’s mathematics, lab line, or memo.

The “this week” task in the lesson is the required start for that grade.

Ladder.

Rungs 19–24.

Also rungs 25–27.

What to cut. A test designed only to confirm the model. A memo that summarizes authorities and never applies them.

Grade 12 — an artifact a stranger can grade

Grade 12 — an artifact a stranger can grade

Same project. The artifact is what a stranger can grade. One reviewer has watched the work long enough to describe it.

Every week, until that artifact is the one you send:

  1. Use the mathematics your first college course will assume, on this project, with units.
  2. Keep the claim in a piece a reviewer can check against the sources.
  3. Let a primary source carry the claim. A summary does not.
  4. Write in the log what would change the conclusion.

Finish these rungs:

  1. Vectors
  2. Matrices as transformations
  3. Systems, determinants, rank
  4. Basis and change of basis

If grade 10 did not already finish them, finish Proof technique and Counting. For a cipher, a password check, a signature, or an access rule, also finish:

  1. Continuous distributions and PDFs
  2. Expectation, variance, covariance
  3. Bayes' theorem

Those three do not replace the linear-algebra rungs above. The break attempt below is where you use them.

School courses beside the project: calculus underway or complete. By the end of this year the lab sequence is biology, chemistry, and physics.

Computer science

Keep the specification. A classmate tries to break one piece you designed: a toy cipher, a password check, a signature on a message, or an access rule. The target is your system, in a closed setting. Write the adversary’s goal and whether the break worked. Finish the linear-algebra gates even if the break attempt is the center of the project.

Done when the writeup states the goal, the result, and the change you made if the break succeeded.

This week. Give a classmate one hour and a closed copy of a password check or a toy cipher you wrote. Tell them the goal in one sentence: produce an accepted password they were not given, or read a message without the key. Write whether they did it. If they did, change one thing and say what. The target is your program, not a live system.

Log for this week. Date. Adversary goal in one sentence. Did they succeed. Change made if they did. Confirmation the target was your program only.

What you send

The application is this project. By the time you apply, the file has these parts:

  1. The grade 12 artifact for your track.
  2. The log, showing the same question across four years and what changed.
  3. A letter from the person outside your household who tried to break the work.
  4. The course record this lesson names: calculus and the lab sequence where your track requires them. Also take the courses your desired college publishes as required. If one of those crowds out the project, add it around the project. Do not drop the lab line or the mathematics line to make room for an elective.
  5. The undergraduate admission test that college requires, on the calendar that college publishes. If your track has a mathematics line, take the test after that mathematics is underway. This is not the medical-school, law-school, or doctoral test, and it is not a substitute for the project.
  6. An essay that states the claim, the best objection, and what the project changed. It is not a list of activities.

What you enroll in

The first year of college keeps the next gate open. Add a course only when it serves that gate.

Once a week, in the hardest course you are in, take one problem the exam could ask. Close the notes. Write the diagram, the equation, or the rule before you look up the solution. Record whether you finished it and where the solution disagreed. That page is the log. A course you only follow in lecture is not done.

Computer science. Data structures and discrete mathematics in the first year. Computer organization when the department offers it. Linear algebra stays in the plan. Cryptography comes after proofs and probability are comfortable. It does not replace data structures.

Through the degree, to the gate

The first year is the start. The gate opens only if the later courses are the same kind of work.

Computer science. After data structures and discrete mathematics: algorithms, computer organization, and probability. Then a systems course and a theory or second algorithms course. The specification and the tests stay the way you are graded. Cryptography is a later course, after proofs and probability, and it adds an adversary to the specification. It does not replace algorithms or systems. Graduate computer science expects those courses. A cryptography direction expects you can state what an adversary is allowed to do and whether the scheme survived it.

Teacher guide

Grade 12 — teacher guide

A stranger grades the artifact. One reviewer who has seen the work over time can describe it. That description is the recommendation.

The “this week” task in the lesson is the required start of the grade 12 artifact.

Ladder.

Rungs 28–31, plus a closed-lab break attempt on the student’s own system. If that attempt is a cipher, a password check, a signature, or an access rule, also rungs 14, 16, and 38–40. Those do not replace 28–31.

What to cut. Clinical hours, competitions, and polish that crowd out the artifact. Cryptography practice stays on a system the student built. It is not an attack on a live network.

Course line still required beside the project. Biology, chemistry, and physics with labs, and calculus.

Back to the field guide

College tracks, grades 9–12 · Schoolhouse