# JW CV v2.5 Candidate 15 — Release Notes

**Date:** August 27, 2026  
**Release class:** Static production candidate / mobile QA + controlled applied-evidence update  
**Rollback baseline:** v2.5 Candidate 14

## Purpose
Candidate 15 is a narrow static release. It corrects the mobile Deployment History presentation and preserves the August 26, 2026 2040 South Church/community-history findings in the Applied layer as a controlled development record. It does **not** promote unresolved claims into the certified master CV.

## Material changes
- Corrected `/deployments/` mobile navigation by using the sitewide responsive navigation classes and seal dimensions.
- Added mobile-safe deployment hero spacing, buttons, content width, wrapping, and card behavior.
- Added **AE-2026-003 — 2040 South Church–Derived Applied Experience Development Queue**.
- Preserved six candidate applied domains: 2040 South Church stewardship; Veterans Services Commission; E-Business Center / E-Vision Business Center; Active Expressions Art Academy; Mary Ann Riley legacy; and longitudinal AI / technology readiness.
- Preserved explicit certification gates and controlled pending claims.
- Updated `/applied/feed.xml`, `/applied/registry.json`, `/deployments/feed.xml`, `/deployments/registry.json`, the site machine manifest, and all visible version footers.
- ORCID API/Functions remain excluded from production and isolated to the beta integration laboratory.

## Governance boundary
The supporting August 26 memorandum is a controlled working memorandum and is not a certified CV revision. Candidate 15 therefore records evidence-development status and candidate themes only. Exact dates, durations, capital amounts, quantitative business counts, formation roles, compensation status, institutional participation, and other unresolved claims remain gated.

## QA focus
1. iPhone/mobile rendering of `/deployments/`.
2. Candidate 15 footer visible sitewide.
3. AE-2026-003 visible on `/applied/` with the controlled-status warning.
4. Applied and deployment RSS feeds parse successfully.
5. No `/functions/` directory present in the static production package.