What I read in Log 2

• Twenty of twenty. Two late. Sixteen Satisfactory, four back for a small fix; revisions are free for 48 hours.
• The gifts landed. "This gift makes me feel seen and loved by you." "All students doing A-levels in the UK should have access to something like this." "Even though I have other ways to track my workouts, I'll definitely use it for some things." That last one is what most first reactions sound like.
• Sixteen of nineteen skills read a syllabus or summarize a document. Fine for a first skill. None count toward Harness v1: three skills doing one job each in your team's automation by Oct 19.
• Eleven of you didn't name the witness. Graded on substance this once. From Log 3 it's literal. And the form is the record; Canvas is a receipt.

Three logs under 500 words. "Nothing yet" in a field is a sentence about why, not the word. Nobody could say what a touch point is; that's on me, 3:13.

Four rules. Seventeen of you cited one.

Four more wrote about the book without picking a rule: uneven ability, AI as collaborator, why we humanize it, and "AI is unbiased."

A touch point is a place on this path

Not a conversation. Not a calendar lookup. A place on the path where your harness does gather, synthesize, sense-make, or disseminate, and a human keeps the decision until a rule makes delegation safe. Log 3 asks for your first sketch of three.

Words you'll be graded on

Seven teams

The first call is where you start, not what you're assigned. Friday's Brief names the design partner you actually got.

Eight minutes, one sheet

1. Sit together. Now.
2. Write: names, the anchor card, two alternates, and for each the name of the person you'll call this week. No name, no candidate.
3. Pick the caller. Before Wednesday, one of you asks the anchor's process owner hunt-page questions 3, 5, and 8. Verbatim notes.
4. Sheet to me before the build starts.

Fri Sep 25, 11:59pm: the Inefficiency Brief, 2–3 pages, one per team: design partner, process owner's agreement to three meetings, the ten-more list, three touch points, assumptions ledger, data agreement, research plan. Log 3 is still yours alone.

What one looks like

{
  "hooks": {
    "PostToolUse": [{                       ← the moment: after a tool runs
      "matcher": "Write|Edit",              ← which tools: file saves
      "hooks": [{
        "type": "command",
        "command": "jq -r '.tool_input.file_path' | { read -r f;
          if grep -nE '[0-9]{3}[-. ][0-9]{3}[-. ][0-9]{4}' \"$f\"; then
            echo \"PHONE NUMBER FOUND in $f: check the data agreement
                  before this leaves the building\" >&2;
            exit 2;                         ← 2 = stop and tell Claude
          fi; }"
      }]
    }]
  }
}

Event, matcher, command. The command gets the tool call as JSON on stdin. Exit 0: carry on. Exit 2: stop, and what you wrote to stderr goes to Claude. Without the exit 2 it's a line in a transcript nobody reads.

Build yours. Pick one.

Or your own, if you can say the event, the matcher, and the one thing it does. New folder: mkdir -p ~/ent1000-hooks/.claude && cd ~/ent1000-hooks. JSON on the next three slides.

The guard · .claude/settings.json

{
  "hooks": {
    "PostToolUse": [{
      "matcher": "Write|Edit",
      "hooks": [{ "type": "command", "command":
        "jq -r '.tool_input.file_path' | { read -r f; if grep -nE '[0-9]{3}[-. ][0-9]{3}[-. ][0-9]{4}|[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\\.[a-z]{2,}' \"$f\"; then echo \"PERSONAL DATA in $f: check the data agreement before this leaves the building\" >&2; exit 2; fi; }"
      }]
    }]
  }
}

Start claude in the folder, ask it to save a note with a phone number in it. Then one without.

The ledger · .claude/settings.json

{
  "hooks": {
    "Stop": [{
      "hooks": [{ "type": "command", "command":
        "echo \"$(date '+%Y-%m-%d %H:%M') · finished a turn in $(basename \"$PWD\")\" >> log.md"
      }]
    }]
  }
}

No matcher: Stop has no tool to match. Ask Claude anything, then cat log.md.

The gate · .claude/settings.json

{
  "hooks": {
    "PreToolUse": [{
      "matcher": "Bash",
      "hooks": [{ "type": "command", "command":
        "c=$(jq -r '.tool_input.command'); if echo \"$c\" | grep -qE 'curl|wget|rm -rf'; then echo \"BLOCKED: $c. Nothing leaves the building and nothing gets deleted without a hand on it.\" >&2; exit 2; fi"
      }]
    }]
  }
}

Exit 2 before the tool runs means the command never runs. Ask it to fetch the course site with curl; then ask it to list the folder.

Build · fire · change one thing · 22 min

1. Build (10). JSON into .claude/settings.json. Start claude there. /hooks lists it. Read the command back and say what it does.
2. Fire (8). One plain request that should trigger it; one that shouldn't. Write both down: that's your Log 3 experiments field.
3. Change one thing (4). Guard: a pattern your team's data has. Ledger: what the line records. Gate: one command your harness must never run. Restart, fire again.

Two guests

What goes in Log 3

Week 3 · Sep 21–25 · Fri 11:59pm · 500–800 words · the form, not Canvas · still individual