refactor(cadence): drop dead cadence block from people/edpa configs (cadence is iteration-sourced)#53
Merged
Merged
Conversation
…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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The
cadence:block in thepeople.yamltemplate (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 thepi:block of.edpa/iterations/PI-*.yaml(_pi_loader.derive_pis), or inferred from each iteration'sweeks:/dates. The block had also been copied intoedpa.yamlexamples 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
cadence:frompeople.yaml.tmpl; add a breadcrumb to the iterationpi:block.people.yamlis now justteams+people.mcp_server.pyedpa://configresource description (it servesedpa.yamlbut claimed "PI, iterations, cadence, sync settings");backlog.py"(people, teams, cadence)" comment (cadence is loaded into the dict but never read).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).cadence:snippet from README / SETUP / quick-start / playbook (CZ+EN) and the web setup wizard's generated config;docs/cadence.mdgains a "Where cadence is configured" section. Conceptual 2/10-vs-1/5 content is unchanged.2.1.9 → 2.1.10+ CHANGELOG entry.Verification
pytest: 577 passed.npm run build(web): 28 pages built OK.pi_weeks/delivery_iterations_per_pi/ip_iterations_per_pioutsideCHANGELOG.md/docs/proposals/.backlog.py tree) loadspeople.yamlfine.No engine behaviour change — cadence was already iteration-sourced.
Follow-up (out of scope here)
setup.astroCZ+EN) generates a non-canonical config (edpa:/scoring:/outputs:shape doesn't match the real v2edpa.yaml/people.yaml/cw_heuristics.yamlsplit). Only the deadcadence:block was removed from its output; the generator needs a separate overhaul.web/package.json+ lockfile and doc version references (left to the release step).🤖 Generated with Claude Code