# Whole Picture — Future Enhancements

**Last updated:** August 29, 2026  
**Purpose:** Sherie’s durable, at-a-glance list of material Whole Picture work that remains.  
**Boundary:** This is an internal product-development list—not a Town plan, public promise, recommendation, release authorization, or deployment authorization.

The first-page **Future enhancements** link in internal working versions should open a concise HTML view of this list. Keep the link small and visually quiet at the far right of the ribbon. Do not include the internal page or link in a public or Cloudflare package unless Sherie expressly authorizes it.

## Resident-story connections still incomplete

1. **Goals → Budget → Work → Results.** Establish accepted relationships among strategy, accounts, implementation, measures, resident outcomes, and learning. See `WP-PMO-024` and `WP-PMO-026`.
2. **Projects → Assets → Complete lifecycle.** Connect condition, need, authorization, funding, contracts, spending, completion, maintenance, and current status. See `WP-PMO-021`, `WP-PMO-022`, `WP-PMO-023`, and `WP-PMO-025`.
3. **Budget accounts → Resident portfolios.** Assign each dollar once without hiding shared Townwide costs or confusing enterprise funds with the General Fund. See `WP-PMO-013`, `WP-PMO-014`, and `WP-PMO-018`.
4. **Commercial activity → Public cost and value.** Connect gross contribution, incentives or Town support, direct and shared public costs, service effects, obligations, and results. See `WP-PMO-007`, `WP-PMO-010`, and `WP-PMO-011`.
5. **Place → Resident experience.** Establish stable, privacy-safe geography and resident-experience contracts before publishing location comparisons. See `WP-PMO-001`, `WP-PMO-002`, `WP-PMO-003`, and `WP-PMO-028`.
6. **Decision → Authority → Follow-through.** Show who may decide now, what was authorized, how implementation proceeded, what changed, and who remains accountable. See `WP-PMO-016`, `WP-PMO-019`, `WP-PMO-020`, `WP-PMO-026`, and `WP-PMO-027`.

The complete evidence, limitation, owner, severity, workaround, and retest requirement for every dependency remains in `PMO-DATA-DEFECT-REGISTER.md`. Missing is not zero. A listed enhancement is not automatically ready, authorized, funded, or assigned.

## Product and release work

- **Resolve the presentation lineage.** `CURRENT-VERSION.md` and `00-CURRENT-WHOLE-PICTURE` currently name v4.17.0 while later local candidates carry additional reporting and interaction work. Do not silently move the pointer. Verify the intended successor, complete release QA, and obtain Sherie’s authority before changing current pointers or preparing a deployment.
- **Keep interaction language consistent.** Small navy top-right arrow means a card opens another page; heavy gold arrows show story flow; plus/minus expands or closes content; flat boxes without an action cue are information only.
- **Keep Special Reports substantive.** Once a resident chooses a Special Report, provide the complete developed story rather than another thin doorway.
- **Complete preserved-content review.** Use `PRESERVED-CONTENT-REFLECTION-AND-RETIREMENT-REGISTER.md` and `SPECIAL-REPORT-DECOMMISSION-REVIEW-CANDIDATES-v4.17.0.md`. Only Sherie may authorize removal of an exact preserved artifact.
- **Repeat final QA for every successor.** Validate story flow, numbers, links, accessibility, keyboard behavior, 375px mobile, 200% zoom, print/PDF, responsive tables, overflow, focus, contrast, console, provenance, disclosure, manifest, and checksums.

## Ownership and handoffs

- Whole Picture owns only its broad connected-reporting product.
- Resident Briefs, Affordability, Capital Management, the System Atlas, the 2027 Budget Process, loaders, UAT, database architecture, Master Control, Git, and deployment remain separate roles or products.
- Whole Picture may consume accepted artifacts and provide specialist content or reusable components through governed handoffs. It does not silently take ownership or change another role’s package.
- Resident Brief releases v0.3.0 and v0.4.0 remain immutable under their transferred owner.

## Maintenance rule

Update this file when Sherie adds, completes, changes, or explicitly retires a material enhancement. Keep the HTML view short; this Markdown file and the linked defect, decision, and preservation registers carry the durable detail.