# TK learning system

[Teacher notebook](/human/learn/tk)

## Inspect the teaching contract

- [Versioned curriculum and lesson package](/learning/tk/curriculum.json)
- [Proposal JSON schema](/learning/tk/proposal.schema.json)
- [Example proposal](/learning/tk/example-proposal.json)
- [Executable planning rules](/learning/tk/engine.js)

The curriculum includes explicit prerequisites, observable criteria, fresh tasks, original lesson plans, source links, immutable publication revisions and hashes, and pupil workbook pages. This is an original planning system, not a normed assessment or an outcome-validated intervention.

## Propose an improvement

1. Read the selected lesson and its exact baseRevision.
2. Create a proposal using the schema. State the rationale, a testable hypothesis, and what each source supports. Supply replacement text only for editable teaching fields.
3. Give the JSON file to the teacher. The notebook validates it and shows a field-by-field comparison before any trial.
4. A teacher can approve a classroom trial or decline it with a recorded reason. Approval is local to that private workspace and does not publish a public library revision.
5. New observations retain the exact proposal hash or published baseline revision. Compare the task, response, assistance, context, and date. A before/after change alone does not establish that the revision caused learning.

## Read a portfolio when authorized

The teacher can export a JSON portfolio containing private observations and work samples. Ask the teacher for that file only when authorized to review pupil work. The public curriculum package contains no pupil records. Imported portfolios merge by immutable record ID; conflicts are rejected and saved records remain intact.

Teacher workspaces use private recovery keys. Do not request or include a recovery key in a proposal, a URL, or published material. All outcome claims remain bounded by the recorded evidence; secure assessment questions and invented percentile scores are excluded.