# Usage Note

The Chapter 14 note that makes a share a share: **share the thing with the instructions, and the instructions are the share.** Write it the day you share, not the day you leave. Keep it on top of the file, first lines, so it answers questions before anyone asks.

## The Note

```
# Usage note for [TOOL NAME]

What this does: [Two sentences. What it takes in, what it produces.]
How to run it: [Steps a stranger can follow. Assume nothing: inputs, files, access.]
What it costs per run: [Pennies against the existing allotment, or the honest number.]
Who to ping: [Name] [What you own: "If it breaks or you want a field, ping me."]
```

## The Changelog

One line per change, written when the change happens, not when someone asks. This is the audit trail that gives the file a memory.

```
Date | What changed | Who asked | Why
[YYYY-MM-DD] | [One line] | [Name] | [Reason]
```

## The ROI Line

Three artifacts make a shared tool legible to management, and all three are cheap.

- The usage note's cost line: converts the AI line item into the thing we already pay for, used more.
- An adoption count: count the humans who ran it this week, not the runs. A number you can say out loud.
- A before-and-after estimate, honestly labeled: write the word estimate next to the number, because the label is what makes it credible.

## Rules That Travel With It

- One version, one owner of changes, changed in place. Never fork.
- No confidential data in shared prompts or shared files, per Chapter 3. Shared copies carry shapes, never data.
- Every output stays a draft with a named reviewer.
- Two corrections on the same thing means the note gets a line added. Writing it down means the third time never happens.