What I read in Log 1

• Twenty of twenty. Everyone's in. Two of you sent it twice; once is enough.
• The quotes landed. "Hundreds of emails per day." "The information lives in a binder." "This work can be automated but I don't know where to start." "Every week [he] has to send my mom his travel and meeting schedule and [he] sometimes forget[s]." Those are inefficiency cards waiting to be written.
• Thirteen of you couldn't attach the screenshot. The form has no upload; that's on me, not you. Pasting what it printed counts. From now on: drop the picture in Drive, paste the share link.
• "Nothing yet" was fine. Dots and N/A are not. Five logs had fields with nothing in them. Revisions are free for 48 hours after I return them. Every week.

Two of you wrote install status under touch-point status. Touch points are the three places your harness meets the process owner's work. You don't have one yet; "none" is the answer.

Three things to fix before Wednesday

1. Turn the permission prompts back on. Five of you switched them off in week one, one of you at boot. That prompt is the hand on the thing before it leaves the building. Week 3 is how to make it fire only when it matters. Until then it fires every time.
2. Seven logs were under 500 words. The spec is 500 to 800. It isn't a length for its own sake: under 500 means a field got a sentence instead of what happened. Log 2 is the first one that counts toward the bundle at full weight.
3. Three gift plans are purchases. Five are apps. The exercise says made or done. A gift card isn't. An app can be, if it's in their hands by Friday. Ship the small version: the one screen they'd actually use.

None of this costs anything today. All of it costs something if it's still true Wednesday.

What one looks like

---
name: card
description: Turn a messy note about tedious work
  into a five-line inefficiency card with its
  bucket and a ten-more-customers check.
---
Given this note: $ARGUMENTS

Write exactly five lines:
1. Who does this (org, role, place)
2. What the hands actually do
3. How often, and how long each time
4. How I know (saw it / they told me / guessing)
5. Bucket: process, decision, discovery, outreach

Then one line: could ten other organizations
pay to stop doing this? If not, say "errand."
Refuse any note that doesn't name the organization.

Pick one

Or your own, if it's a job you'll do at least three times this term and you can name it in two words.

Build it (1 of 3) · 10 min

cd ~/ent1000
mkdir -p .claude/skills/card
claude

Create .claude/skills/card/SKILL.md.
Frontmatter: name and a one-sentence description
a stranger could use. Body: given $ARGUMENTS,
produce exactly [your format]. Refuse [your rule].
Show me the file.

Run it (2 of 3) · 15 min

1. Run it on a real input: your own note, your own reading, your own interview. Not an example you made up.
2. Run it on a second, different real input.
3. Now ask for the same thing without the skill, in plain words. Put the two outputs side by side.
4. Write one sentence: the skill did ___ that the plain request didn't. If you can't fill the blank, the skill isn't doing anything yet. Give it a rule.

Keep both outputs. They go in Friday's log under Experiments, and the sentence goes under Harness change.

Change one thing (3 of 3) · 10 min

• Something in the output annoyed you. Too long, wrong order, a section you'll never read, a guess where you wanted a question.
• Fix it in the file, not in the conversation. Rerun on the same input.
• That's version 1 → shipped. Friday's log wants the change and the reason, in one line each.

If nothing annoyed you, you didn't read the output.

When it doesn't work

Still stuck at 3:50: demo what you have. A broken, honest demo beats a polished one that only works on the easy case.

Wednesday, Sep 16

1. Co-Intelligence, intro and ch. 1–3, read. Come knowing Mollick's four rules and which one today's skill obeyed or broke.
2. Three inefficiencies, on paper. Five lines each: who, what the hands do, how often, how you know, bucket. One from a person you talked to. Every one names the organization. They go on the wall.
3. Teams form. Two or three. You pick each other by the cards on the wall, not by who you sat next to.

If you built /card today, run your three through it tonight. If you built /digest, run the reading through it. Either way, bring what it produced.

What goes in Log 2 (1 of 2)

Week 2 · Sep 14–18 · Log 2 · Fri 11:59pm · 500–800 words · the form, not Canvas

What goes in Log 2 (2 of 2)

Gift paragraph, skill sentence, classmate's name, four rules. If those four things are in the log, it passes. If they're vague, it comes back.