#1 — Opening night: the debt named, three briefs on the table
It started with one sentence from Maciej at 3 a.m.: “We didn’t do our homework, and we were supposed to be the model students.” A check against the course MCP confirmed it: three challenges open, zero solved. In the morning lesson s01e03 opened — on building knowledge systems — and its thesis is exactly what happens here: the agent builds and maintains the documentation itself.
What we did that night: the day brief for s01e03 written and saved
to the dashboard; Maciej’s delegation decision — all three challenges at once, one
gpt-6.1-sol worker each on the omp harness, dispatch by Maciej in person; three worker
briefs filed in challenges/; this journal and the MATRIX were born.
- Mishap #1: saving the brief to the course failed with HTTP 500. Lesson: one retry on a server-side error before you declare failure — the second shot landed.
- Mishap #2: after the session forked into a coordinating half and an executing half, both sent the same documentation dispatch. Lesson: after a session fork, the first message is the division of work, not the work. The duplicate was caught and killed within a minute, because both sides reported their run-id.
- Mishap #3 (older, from the fleet wave): a 6×9 matrix was run in 54/54 cells, but nobody wrote the comparative report for the whole — winners were picked ad hoc and success was declared. The lesson that shaped this journal: a matrix without a report is not a deliverable. Hence the rule: every task ends with an entry here.
Next: dispatch of the three workers (Maciej’s decision, Maciej’s hand). Entries #2–#4 report on their runs — including whatever goes crooked.