Skip to content

refactor(cadence): drop dead cadence block from people/edpa configs (cadence is iteration-sourced)#53

Merged
jurby merged 1 commit into
mainfrom
chore/drop-dead-cadence
Jun 1, 2026
Merged

refactor(cadence): drop dead cadence block from people/edpa configs (cadence is iteration-sourced)#53
jurby merged 1 commit into
mainfrom
chore/drop-dead-cadence

Conversation

@jurby
Copy link
Copy Markdown
Contributor

@jurby jurby commented Jun 1, 2026

Why

The cadence: block in the people.yaml template (iteration_weeks / pi_weeks / delivery_iterations_per_pi / ip_iterations_per_pi) is dead config — nothing in the engine reads it. Effective cadence is derived per Planning Interval from the pi: block of .edpa/iterations/PI-*.yaml (_pi_loader.derive_pis), or inferred from each iteration's weeks:/dates. The block had also been copied into edpa.yaml examples and e2e fixtures with a misleading "must mirror" note (no code ever verified the match), so it invited "edit this to change the rhythm" mistakes.

This removes the dead artifact everywhere and points users at the real surface.

What changed

  • Templates: drop cadence: from people.yaml.tmpl; add a breadcrumb to the iteration pi: block. people.yaml is now just teams + people.
  • Code (doc-drift): mcp_server.py edpa://config resource description (it serves edpa.yaml but claimed "PI, iterations, cadence, sync settings"); backlog.py "(people, teams, cadence)" comment (cadence is loaded into the dict but never read).
  • Examples/fixtures: docs/kashealth-pilot/{edpa,people}.yaml.example, docs/examples/capacity-small-team.yaml, tests/e2e_v2_full/fixtures/{edpa,people}.yaml (incl. the stale "Wave C verifies this match" comment).
  • Docs/web: remove the cadence: snippet from README / SETUP / quick-start / playbook (CZ+EN) and the web setup wizard's generated config; docs/cadence.md gains a "Where cadence is configured" section. Conceptual 2/10-vs-1/5 content is unchanged.
  • Release: plugin 2.1.9 → 2.1.10 + CHANGELOG entry.

Verification

  • pytest: 577 passed.
  • npm run build (web): 28 pages built OK.
  • grep: no pi_weeks / delivery_iterations_per_pi / ip_iterations_per_pi outside CHANGELOG.md / docs/proposals/.
  • engine smoke (backlog.py tree) loads people.yaml fine.

No engine behaviour change — cadence was already iteration-sourced.

Follow-up (out of scope here)

  • The web setup wizard (setup.astro CZ+EN) generates a non-canonical config (edpa: / scoring: / outputs: shape doesn't match the real v2 edpa.yaml / people.yaml / cw_heuristics.yaml split). Only the dead cadence: block was removed from its output; the generator needs a separate overhaul.
  • A full 2.1.10 release should also bump web/package.json + lockfile and doc version references (left to the release step).

🤖 Generated with Claude Code

…cadence is iteration-sourced

The people.yaml `cadence:` block (iteration_weeks / pi_weeks / delivery_iterations_per_pi / ip_iterations_per_pi) was never read by the engine. Effective cadence is derived per Planning Interval from the `pi:` block of .edpa/iterations/PI-*.yaml (_pi_loader.derive_pis), or inferred from each iteration's weeks/dates. It was dead config — also wrongly duplicated into edpa.yaml examples/fixtures with a "must mirror" note — that invited "edit this to change the rhythm" mistakes.

- templates: remove cadence: from people.yaml.tmpl + breadcrumb to the PI pi: block
- code: fix edpa://config resource description + backlog.py comment (both named "cadence" though nothing reads it)
- examples/fixtures: drop cadence from kashealth-pilot + capacity-small-team + e2e fixtures (incl. stale "Wave C verifies this match" comment)
- docs/web: drop cadence snippet from README/SETUP/quick-start/playbook (CZ+EN) + web setup wizard; docs/cadence.md gains "Where cadence is configured"
- bump plugin 2.1.9 -> 2.1.10 + CHANGELOG

No engine behaviour change — cadence was already iteration-sourced. Full suite 577 passing; web builds.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jurby jurby merged commit a1fa196 into main Jun 1, 2026
1 check failed
@jurby jurby deleted the chore/drop-dead-cadence branch June 1, 2026 11:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant