ProgramForgeFischer Product LabOpen the demo

Portfolio demonstration · read-only · synthetic data

On track. Blocked.
Decide this cycle.

Which cross-team initiatives hold, what is stalled, and what leadership must call — from the same records the brief is built on.

Open the demoSee how it decides
Open the ProgramForge portfolio demo
programforge · portfolio / cycle
DEMOSynthetic snapshot · 27 Jul 2026

Portfolio health

P0 At Risk: Atlas dual-region cutover, Critical exposure closure

5 on track3 at risk2 blocked deps4 open decisions
Portfolio healthAt Risk

Blocked initiatives

Critical-path dependencies that can miss the date.

Critical path
Atlas dual-region cutoverShared sandbox hardeningBlocked
Failover drills require a stable lower environment for dry runs.
dep-001 · owner S. Brooks
Critical path
Shared sandbox hardeningRegression confidence upliftBlocked
Flaky sandbox refreshes invalidate automation baselines.
dep-007 · owner S. Brooks

Leadership must decide

Open calls on the register this cycle.

Open
Accept temporary compensating control for Identity SSO?Office of the CISO · due 2026-07-29
dec-001
Requested
Make telemetry checklist a hard CAB gate this quarter?CTO Office · due 2026-08-05
dec-002
Open
Re-sequence East failover drill after sandbox refresh?SVP Platform Engineering · due 2026-07-31
dec-003
Requested
Fund a second shared integration sandbox?Director Platform Ops · due 2026-08-07
dec-004

Initiative bands

Deterministic health from the seeded program set.

Atlas dual-region cutover P01 blocked critical-path dependency
At Risk
Zero-downtime release kit P1No hard-gate signals; milestones and readiness on track
Healthy
Shared sandbox hardening P11 blocked critical-path dependency
At Risk
Production telemetry standard P0No hard-gate signals; milestones and readiness on track
Healthy
Governed AI productivity pilots P1No hard-gate signals; milestones and readiness on track
Healthy
Critical exposure closure P02 critical open RAID items
At Risk
Regression confidence uplift P2No hard-gate signals; milestones and readiness on track
Healthy
Release coordination tower P1Capacity pressure 125% of stated capacity
Healthy

How it decides

Health is a pure function. Same records, same band. No model in the loop.

  1. 01Score

    Each initiative starts at 100. Critical RAID, overdue milestones, blocked critical-path dependencies, failed gates, stale evidence, and capacity pressure deduct — and every deduction is written into reasons[].

  2. 02Gate

    Hard rules override the arithmetic. A blocked critical-path dependency, or two or more open critical RAID items, forces At Risk even if the residual score still looks polite.

  3. 03Weight

    The portfolio is priority-weighted — P0×3, P1×2, P2×1. Any P0 At Risk pulls the book to At Risk. Same seed, same band. No editor, no model.

  4. 04Brief

    The leadership pack is a pure function over those records: what moved, what is blocked, and which calls must land this cycle. Export is local Markdown and CSV.