Ho System, Actually Build the software. Develop the judgment.

devlog

definition
depth 3/4 − deeper + surface

A structured write-up done after a session that records what was decided and learned, so the work reads as yours rather than the machine's.

Structured reflection written after a ho; "the artifact that distinguishes 'I built this' from 'AI built this while I watched.'" A learning journal in shu, a decision record in ha, dissolved into the ho document itself in ri—in current practitioner-shape documents its function is carried by the Reflect phase (ha) or Results (ri).

What a Devlog Is. A devlog is a structured reflection written by the learner after completing a ho. It records what was built, what was understood, what was hard, and what's still unclear. It's not a project log ("what I did today") and it's not a commit message ("what changed"). It's a learning document—the artifact that distinguishes "I built this" from "AI built this while I watched."

The devlog is the primary evidence of learning in the Ho System. Code can be generated. Tests can be generated. Configuration files can be generated. The devlog cannot be generated—it requires the learner to look back at their own experience and honestly assess what happened. An AI can write your code; it cannot write your reflection for you.

Three properties define a devlog:

Honest. The devlog rewards accuracy, not performance. "I don't understand how ffmpeg encoding works—it still feels like incantation" is more valuable than "I now have a solid grasp of the encoding pipeline." The first tells you exactly where the knowledge boundary is. The second tells you nothing.

Immediate. Written right after completing the ho, while the experience is fresh. Not the next day. Not "later." The details that matter most—the moment of confusion that resolved into understanding, the AI suggestion you overrode and why, the gotcha that cost twenty minutes—evaporate quickly. […]