Skip to content

v5.06 — Every initiative in one live view, and dependencies read the right way round

Choose a tag to compare

@cody-hutson cody-hutson released this 08 Nov 22:12
Immutable release. Only release title and notes can be modified.
v5.06
b02fa16

Every initiative in one live view, and dependencies read the right way round

2026-11-08 · v5.06

You can now see every initiative and every epic that sits under none, with its epics and open work beneath it, in one view read live from the tracker. Milestone sequencing also stops guessing: a dependency written in an issue is read in the direction it points, so work is no longer ordered backwards.

Skip the rest unless you sequence milestones, read initiative progress, write dependencies into issue bodies, or run the platform's release tooling.

Who this affects

  • Anyone who sequences milestones or reads which work must land first
  • Anyone who reads initiative progress or decides which epics belong to which initiative
  • Authors who write "Blocked by" or "Dependencies" sections in issue bodies
  • Operators of an installed workspace (one step below)

What you need to do

  1. Only if you run an installed workspace: run ./update.sh --surfaces-only once. The release added the two new tools to the list of scripts the platform's safety checks let run, and the normal deploy does not carry that list to an installed workspace.

What changed for everyone using the platform

  • Every chain head is in one live view. One command lists each initiative, and each epic that belongs to no initiative, with its epics and open work underneath, read from the tracker when you run it; the roadmaps guide shows how to run it. Read on 2026-11-08 it showed 10 initiatives, 9 with an end point and 1 ongoing, over 709 open issues. Why it matters: you no longer assemble initiative status by hand from separate lists, and the view cannot drift from the tracker because it keeps no copy.

  • The view never reports a count it could not read as zero. When a read fails, the count is marked unmeasured. An ongoing initiative, one whose tracker label description begins with the word "Standing", shows no completion percentage, because it never finishes. Why it matters: a zero or a percentage in the view is a real reading, never a failed read or a meaningless number.

  • Which initiative an epic belongs to comes from its labels. An initiative is any initiative label that has open work, so adding an epic to an initiative takes only the label. An epic with no initiative label joins an ongoing initiative only when more than half of its children carry that initiative's label. Why it matters: there is no separate list of initiatives to keep up to date, and an epic is not pulled into an initiative on a thin majority.

  • Dependencies are read in the direction they point. Previously every issue number in an issue's dependency section counted as something that issue waits on, including "blocks" lines, which point the other way, and links to parent or child items. Now only real waits-on edges count, and a negated line such as "does not block" counts as nothing. Why it matters: the milestone order and the cross-milestone dependency check no longer put work ahead of the work it depends on.

  • A dependency no longer disappears behind extra blank lines. A section in an issue body now ends only at the next heading or a horizontal rule, so a heading followed by two blank lines no longer reads as an empty section. Why it matters: a dependency you declared is never silently dropped.

  • The tools that read issue bodies now read them the same way. Section reading lives in one place that the milestone-ordering tool and the dependency-mirroring tool both use, and the check for epics ready to close counts an epic's children by the same rule as the new view. Why it matters: two tools can no longer disagree about what the same issue says.

Known limits

  • The view reads the dependency sections written in issue bodies, not GitHub's native "blocked by" links. Reading native links for sequencing is proposed in the native-links card, which this release unblocks.
  • The operator's interim board still shows its own portfolio map. Retiring that map in favor of this view is an operator step on that board that has not been taken yet; the board's milestone lanes stay until the standing sequencing layer ships.
  • The check that finds epics ready to close still reads a failed child read as "no children" and leaves that epic out silently, tracked in this observation.
  • The release planner's guidance on which phrases make a hard dependency still lists "blocks" without saying which way it points, so it can disagree with the parser, tracked in this observation.

Report issues at https://github.com/cody-hutson/pmo-platform/issues, and report a suspected vulnerability privately as the Security Policy describes.

Reversibility

MODERATE / HIGH. Reverting the release merge restores the parser, both tools and the documents exactly; nothing outside the repository persists, because no milestone stores a position, the dependency mirror only ever adds links an author declared, and the view writes nothing. The two decision records are Accepted at this close, so changing what they decide now takes a superseding record, and the cost grows as later tools build on the parser's shared reading. The version tag is kept as the record that the version was claimed.


Operator and engineering detail

The view (#6398). python3 release/tools/compute-chain-head-rollup.py prints the Markdown view, and --json prints a versioned machine-readable rollup; --self-test runs offline fixtures. Each head carries its open-member count, a partition of members inside and outside its tree, its unparented members, progress, and a blocked count, and every count carries a status of measured, unmeasured or not-applicable. One head from the live read on 2026-11-08 (commit 6315b977), nodes elided:

{
  "id": "project:pipeline",
  "kind": "initiative",
  "mode": "finite",
  "members_open": 146,
  "progress": {"status": "measured", "completed": 44, "not_planned": 10, "total": 168, "percent": 26},
  "blocked": {"count": 12, "unmeasured": 0}
}

The rollup's meta block records the commit anchor, the denominator (open issues read, checked against the search total) and the status of every read it made. The epic child-set rule (native sub-issues plus label-linked issues, the carrier excluded) moved into release/tools/_epic_child_set.py, shared by the view and audit-epic-rollup-close.sh. ADR-237 records the head derivation, the strict-majority absorption rule and the standing declaration; the label taxonomy and the initiative-roadmap framework now state the standing convention.

The direction grammar (#6397). parse_dependencies in release/tools/bundle-issues-parser.py returns directed blocked_by targets only, applies the negation rule, and treats a blank line as ending a run. Gate G3-07's new Edge source paragraph in the gate-criteria spec names that function as the authority, and compute-milestone-positions.py derives positions from the same edges and carries the parse status.

The single home (#7177). ADR-236 makes the bundle parser the one home of the issue-body section extractor and the dependency heading aliases; native-dep-mirror.py loads it by path instead of keeping its own copy and exits with its infrastructure-failure code when the parser cannot load. A section ends at a level-2 or level-3 heading or a --- rule.

How it shipped. Three cards on one branch, built in engineering slices. Each Stage 5 design went through an adversarial review before the operator's scope lock. Dev Testing and QA both ran. One required check went red because three new tool files were tracked without the executable bit; two were made executable and the third, an imported module, was exempted. Plan Review returned GO with conditions: the merge-order condition was met, and the condition to refresh the pull request's description before Execute was missed and made up at this close. Releases that merged first took the ADR numbers twice, so the records were renumbered from 230 and 231 to 234 and 235, then to 236 and 237, and the release claimed v5.06. It merged at b02fa16a with a signed annotated tag; the only deploy was the rules-mirror refresh. Both decision records were ratified Proposed → Accepted at this close on the operator's per-record decision.

For full implementation detail see the Deployment Log v5.06 entry in the release log, and the release plan.

References