Scaffold efforts convention + release-and-ci effort #33

Merged

mprihoda merged 1 commit from wip/efforts-scaffolding into main

2026-07-11 11:00:57 +00:00

mprihoda commented

2026-07-11 10:48:09 +00:00

(Migrated from github.com)

What

Introduces the efforts convention into iw-support and models the completed release/CI/quality work as the first effort.

project-management/efforts/
├── README.md              ← self-contained convention + single-repo home rule
└── release-and-ci/
    ├── intent.md          ← goal, before→after, invariants, fit test
    ├── decisions.md       ← RCI-D1..D4 (Propagates-to boxes checked)
    ├── map.md             ← 3 Done items → SUPP-9/24/28, 2 candidates
    └── worklog.md         ← state + dated creation entry

Why

An effort is the durable thread between vision and issue: one goal spanning many issues, read first on resume. This PR is primarily scaffolding — getting the structure into the repo — and demonstrates it with a real (already-complete) thread rather than inventing work.

Notes

Back-filled entirely from the three merged issues (SUPP-9 CI+hooks, SUPP-24 dual-publish, SUPP-28 testcontainers pin) — nothing invented.
Map items reference ../../issues/<id>/; no restated issue content.
The README bakes in the home rule: iw-support-development efforts live here; client-program efforts that merely pull an iw-support change belong in the program's coordination repo.
The effort is born closed (all three issues done); it stays open as the home for the distribution/quality axis, with two unverified candidates.

🤖 Generated with Claude Code

## What Introduces the **efforts** convention into `iw-support` and models the completed release/CI/quality work as the first effort. ``` project-management/efforts/ ├── README.md ← self-contained convention + single-repo home rule └── release-and-ci/ ├── intent.md ← goal, before→after, invariants, fit test ├── decisions.md ← RCI-D1..D4 (Propagates-to boxes checked) ├── map.md ← 3 Done items → SUPP-9/24/28, 2 candidates └── worklog.md ← state + dated creation entry ``` ## Why An *effort* is the durable thread between vision and issue: one goal spanning many issues, read first on resume. This PR is primarily **scaffolding** — getting the structure into the repo — and demonstrates it with a real (already-complete) thread rather than inventing work. ## Notes - Back-filled entirely from the three merged issues (SUPP-9 CI+hooks, SUPP-24 dual-publish, SUPP-28 testcontainers pin) — nothing invented. - Map items **reference** `../../issues/<id>/`; no restated issue content. - The README bakes in the home rule: iw-support-development efforts live here; client-program efforts that merely pull an iw-support change belong in the program's coordination repo. - The effort is born **closed** (all three issues done); it stays open as the home for the distribution/quality axis, with two unverified candidates. 🤖 Generated with [Claude Code](https://claude.com/claude-code)