Install LDD: a LOGIC.md beside every source file and directory

[brillout]

What

Installs Logic-Driven Development per the logic-driven-development skill: a LOGIC.md describing the business logic of each file and directory containing source code, written for the technical product manager who never reads the code.

• some-file.ext → some-file.LOGIC.md, some-dir/ → some-dir/LOGIC.md, across the whole monorepo (the product, the driver seam, the agent-data library, the four skills, the Chrome extension, the website, the prompts, the GitHub workflows).
• Written fresh from the code — not converted from any earlier documentation. Every file was read in full; test files get a "What the tests cover" list.
• One vocabulary across all files (agent, driver, turn, gate, pick, handoff, checkout, location, the agent-data branch, sweep, quota boundary, …), with a per-file glossary for the project's coined terms.
• Files with no business logic (build and test-runner configuration, styling, static assets) are named in their directory's LOGIC.md instead of getting one of their own.

Status

Work in progress on this branch: the root and packages/ files and the first slices are in; the remaining slices land in follow-up commits on this branch, then a consistency pass. No source file is modified.

🤖 Generated with Claude Code

https://claude.ai/code/session_01YcSwKgtQE6ndJYjdDitVFB

---

Generated by Claude Code