Make reading notes with commits and sources attached.
Suggested learning time: 35 minutes.
- 1Rolling branch
- 2Fixed commit
- 3File and symbol evidence
- 4Dated reading note
Original learning map: arrows show the reading or decision sequence, not a measured execution trace.
Prerequisite chapter
Understand the boundaries before trying to read everything
Status of this chapter
This textbook was authored from reading sources. No actual repository builds, tests, debugging, API calls, or issue/PR posts were performed. Practical work below is an exercise to undertake; reading is not an execution result.
Learning objectives
- Make reading notes with commits and sources attached.
Pin the version
Links to main or master change. This textbook's references also point to rolling branches; it is not a pinned lab that has been executed. When you begin an exercise, save the target commit SHA and link to that version using GitHub permalinks. Leave any SHA you cannot retrieve as unverified.
The granularity of evidence
A claim that something depends on an SDK needs a manifest or import; a claim that a function is called needs the call site. Do not infer execution paths from directory names alone. Retain the repository, SHA, path, symbol, line range, verification date, evidence kind, and whether a statement is verified or conjecture.
Understand changes
If local results differ from the textbook, compare versions and environments first. Separate moves, renaming, and specification changes, and add a new note version without deleting the old one. Do not confuse a broken link with a failure to understand.
Practical exercise: Practice: create a fixed reference from a moving branch
- Choose the target commit.
- Save a permalink to one file.
- Write code facts and your own conjectures in separate fields.
- Use null or an unverified label for unknowns.
Deliverable: Three notes with sources.
Understanding checks
Answer in your own words before reading the answers. The answers and explanations below are for self-review, not automatic scores or execution results.
Is a link to main enough for reproducibility?
Answer: No. The target commit, environment, and execution conditions are needed.
Your learning progress
Recording mode: manual.
- Not started
- Read
- Tried
- Can explain
Viewing a page alone does not mean you completed the practical exercise.
Material used in this chapter
Bundle implementation, ApiClient implementation, Codex app-server documentation
Return to repository entry points · Offline experiment worksheet
MENTAL MODEL / REASONING ORDER
From an announcement to your own decision.
Compare the announcement with the conditions in the paper and official documentation.
Sources
Publication dates belong to the source; access dates record when it was checked. Community observations are separate from official statements.