Execution — bi-14-contribution

Steps extracted from CONCEPTS.md. Read the concepts first; this file is the doing.

Record results in observation.md; tick checkpoints in verification.md.

3. Practice

Verify against your checkout's docs/contributing.md and the linked process docs. The mechanical parts (git cl upload, git cl format, git cl owners, CQ dry run) are stable; the surrounding policy is not.

Keep a record per attempt — the specification asks for exactly this, and it is what turns a contribution into learning:

bug · reproduction · spec · suspected subsystem · source path · call path
· test · proposed fix · reviewer feedback · architectural lesson

6. Lab

  1. Rung 0 — a build that runs. (Blocked here; see the roadmap's build guide §2.0.)
  2. Rung 1 — land a docs or test-only change. Goal: complete the process once. Record every step that surprised you.
  3. Rung 2 — from your bi-13 candidate list, pick the smallest defensible correctness fix. Write the failing test first.
  4. Rung 3 — a Blink behaviour bug with a regression test, in a subsystem you studied.
  5. Maintain the record above for each, and write the architectural lesson even when the CL is rejected. A rejected CL with a clear lesson is a successful lab.