The Green Line guide

This is the product manual: Green Line as its users meet it. It explains what gets installed into your repository, how a project moves through the pipeline, and what to do when something is refused. It never describes Green Line's internal machinery — that lives in docs/, the other documentation system.

The maintenance law (binding on every agent that edits this system): read the whole file before editing; fold changes where they belong, never append; a page that no longer tells the truth is rewritten or deleted, never annotated around. Keep the reader a consumer — no machinery vocabulary, no source paths, no dev-repo concepts.

Contents#

1. Quickstart — from init to your first shipped change
2. The pipeline — idea → decisions → spec → tickets → build → review → verify → close
3. Recipes — the light path, evidence, the harvest, and other everyday moves
4. The skills — what's installed and when each earns its moment
5. Doctor reference — every diagnostic code, what it means, how to fix it