# Harbor — where a person had to step in

The adapted example on the Ideas in motion page was made the way the page's own
instructions say, from the served installer, in a clean folder, with a fresh fictional
brief. This is the record of every point where a person did something the instructions
did not do for them, so the next customer knows what to expect.

**Brief.** Harbor, a shift-scheduling tool for small clinics. One job: the roster has a
gap, Harbor fills it, the team sees it on their phones. Warm, calm, exact. Destination
`harbor.example`. Fact to preserve: nobody over 40 h without a manager override. Every
name, number and screen is invented.

## What ran exactly as written

1. Downloaded `plate_toolkit-1.2.4-py3-none-any.whl` from production and checked its
   SHA-256 against the one on the download page — matched.
2. Installed it into a new virtual environment (Python 3.11). `python -m plate_toolkit
   doctor` reported 1.2.4 and the MCP tools; `license` reported `active`.
3. Created the project with `plate_create_project(name="ideas", …)` into an empty
   folder. 41 files, `plate.project.json` written, nothing overwritten.
4. `npm run recipe -- workflow` produced `motion-plan.json` with the five beats the guide
   describes.
5. Edited only the three files the guide names: `film.json`, `src/projects.json`,
   `motion-plan.json`. Every value inside the guide's limits on the first try, because
   the guide states each limit.
6. `npm run check`: lint, runtime, layout, motion and 42/42 contrast checks passed. The
   first run fetched the pinned HyperFrames 0.8.31 renderer and the Inter font (network).
7. `npm run render`: 22.0 s, 1920×1080, 60 fps, stereo audio, 5.1 MB, in 1 m 41 s on an
   RTX 3070.
8. Revision: changed the feature beat from the phone to the coverage chart and the
   collection from grid to ribbon — two fields in `motion-plan.json` — then `check` and
   `render` again. Nothing else in the project was touched.

## Where a person stepped in

- **The licence was already on this machine.** Activation (`python -m plate_toolkit
  activate --browser`, then pasting the key from the Polar portal) was done on 5
  September and not repeated here. A new customer does it once.
- **The demo imagery was authored, not supplied.** A fictional product has no real
  screenshots. The instructions tell the agent to ask rather than invent product
  imagery; as the operator I built six labelled demo screens ("HARBOR · DEMO DATA ·
  FICTIONAL CLINIC") in HTML and captured them at 1920×1200. A real customer supplies
  real screenshots and skips this entirely.
- **The logo was authored** the same way: one small SVG mark.
- **`plate_create_project` was called from Python**, not through an MCP client. It is
  the same function the tool wraps, with Pro enforced inside it; the agent path uses the
  tool.
- **Copy limits were counted by hand** before running the check, because a violation
  fails the build rather than warning. The guide lists every limit, so this took one
  pass; a helper that reports lengths would remove the step.

## Not done here

- Nobody listened to the Harbor render. The audio track is the sample film's music,
  measured present; the credit (Neon by Scott Buckley, CC BY 4.0) is on the project
  page and must stay with the film.
- One machine, one agent path (the operator standing in for the agent). Claude Code,
  Codex and Cursor each receive the same instructions; none was run against this brief
  in this pass.