# Conversation-to-report UAT

Release: `CSKE-Whole-Picture-v4.12.0-20260825`

Scope: every user idea and agreed design conclusion in the active conversation beginning with the Balanced Scorecard discussion. This is a release-acceptance control, not a narrative summary.

Status vocabulary:

- `PASS` — the idea is visible in the public reporting and the named route was checked.
- `PASS-CONTROL` — the idea belongs in the backstage inventory/control layer and is reachable from the public reporting.
- `OPEN` — implementation or verification remains.
- `BOUNDARY` — the idea is represented as a question or capability, but an answer cannot be promoted because evidence is incomplete or not accepted.

## UAT matrix

| UAT | Conversation idea or agreed conclusion | Required expression in the new reporting | Implementation target | Status |
|---|---|---|---|---|
| UAT-001 | Begin at the top: strategy, mission, objectives, measures, and relationship to master plans. | A resident-readable direction-to-results route, not a workbook dump. | `index.html`; `strategy-to-results.html` | PASS |
| UAT-002 | Strategy should reach budgets, not sit beside them. | Trace purpose → outcome → objective → measure → plan commitment → work → budget/resource → result. | `strategy-to-results.html` | PASS |
| UAT-003 | The Balanced Scorecard is a beginning, created recently, and is not yet mature. | Use it as a reviewed working foundation; do not present it as a complete or Town-adopted strategy. | `strategy-to-results.html`; source boundary | PASS |
| UAT-004 | The next level is portfolio/program/project. | Explain the hierarchy in ordinary language and connect it to the strategy and budget story. | `portfolio-assets-and-work.html` | PASS |
| UAT-005 | Show the current portfolio of work and follow-up. | Make current work, ownership, status, dependencies, and follow-up part of the platform capability. | `portfolio-assets-and-work.html`; comprehensive inventory | PASS |
| UAT-006 | Distinguish Run-the-Town work from Change-the-Town work. | Explain continuing service work versus project/change work without falsely classifying unaccepted dollars. | `portfolio-assets-and-work.html`; `town-finances.html` | PASS |
| UAT-007 | Capital requests should connect to a complete asset inventory. | Show the chain from request/recommendation to asset identity, condition, lifecycle, project, funding, and result. | `portfolio-assets-and-work.html` | PASS |
| UAT-008 | Current spending should connect to future obligations. | Show how today's service, maintenance, project, borrowing, and deferral choices create later bills and work. | `portfolio-assets-and-work.html`; `town-finances.html` | PASS |
| UAT-009 | Recommendations should connect to supporting evidence. | Make evidence lineage and decision-readiness a visible step, not a technical appendix only. | `decisions-and-scenarios.html`; `roles-and-decisions.html` | PASS |
| UAT-010 | Missing information should become explicit follow-up. | Name the missing item, why it matters, who should obtain it, and the gate it affects; missing never means zero. | All new routes; `comprehensive-inventory.html` | PASS |
| UAT-011 | Technical financial material should become explanations residents can understand. | Use household language for income, regular bills, savings, credit, one-time money, and future payments without distorting finance. | `index.html`; `town-finances.html`; preserved resident story and reports | PASS |
| UAT-012 | Assets include physical/capital assets and software/data assets. | Treat buildings, land, infrastructure, equipment, software, and data as entrusted assets with different stewardship needs. | `portfolio-assets-and-work.html` | PASS |
| UAT-013 | Asset-management materials are early foundations, not a finished authoritative inventory. | State maturity and source boundary; do not infer completeness, ownership, condition, or current status. | `portfolio-assets-and-work.html`; `comprehensive-inventory.html` | PASS |
| UAT-014 | The Memorial asset pilot demonstrates a place dossier pattern. | Show how one place can connect identity, use, condition, work, cost, evidence, and future options without making the pilot the whole Town. | `portfolio-assets-and-work.html`; `growth-and-identity.html` | PASS |
| UAT-015 | The older Town Roles workbook is necessary. | Include decision rights, recommendation, authorization, delivery, measurement, reporting, and correction. | `roles-and-decisions.html` | PASS |
| UAT-016 | Older role guidance may not be current. | Preserve it as working reference and require controlling-source confirmation for current authority. | `roles-and-decisions.html`; source boundary | PASS |
| UAT-017 | Scenarios are a favorite and were the starting point before the need for Whole Picture became clear. | Give scenarios a visible role after baseline/evidence and before readiness/decision; retain their exploratory value. | `decisions-and-scenarios.html`; `index.html` | PASS |
| UAT-018 | Whole Picture exists to support the final decision, not replace the scenarios. | Show Whole Picture as the evidence and context around scenario comparison. | `decisions-and-scenarios.html` | PASS |
| UAT-019 | A scenario is not a recommendation. | Use working-scenario language and prohibit ranking incomplete alternatives. | `decisions-and-scenarios.html`; boundaries | PASS |
| UAT-020 | Alternatives need a common comparison frame. | Compare outcome, service, assets, capital, recurring cost, financing, household effect, place, timing, risk, authority, evidence, and reversibility. | `decisions-and-scenarios.html` | PASS |
| UAT-021 | Understanding Together should be read and its carefully developed language used where appropriate. | Incorporate its question-led learning, stewardship, readiness, civic-value, reversibility, and learning language in Sherie's voice. | All new routes | PASS |
| UAT-022 | “Before communities decide together, they benefit from learning to understand together.” | Use as a governing explanation of the platform's purpose. | `decisions-and-scenarios.html` or `roles-and-decisions.html` | PASS |
| UAT-023 | “Understanding does not require agreement.” | Keep this as a visible civic posture. | `index.html`; decision route | PASS |
| UAT-024 | “What important parts of the picture have we not yet understood?” | Use as a readiness/follow-up question. | `decisions-and-scenarios.html`; inventory | PASS |
| UAT-025 | “The goal is not to eliminate tradeoffs. The goal is to understand them.” | Use in the alternatives/tradeoffs explanation. | `decisions-and-scenarios.html` | PASS |
| UAT-026 | “Stewardship asks, ‘What has been entrusted to us?’” | Use to connect identity, assets, public money, knowledge, and future responsibility. | `portfolio-assets-and-work.html`; `growth-and-identity.html` | PASS |
| UAT-027 | “The past teaches. The present decides. The future inherits.” | Make the intergenerational consequence visible. | `index.html`; decision and place routes | PASS |
| UAT-028 | “Decision Support does not replace human judgment. It strengthens it.” | State that Whole Picture supports, not makes, community decisions. | `decisions-and-scenarios.html` | PASS |
| UAT-029 | “Compared by what?” | Make denominator, criteria, and common comparison basis explicit. | `decisions-and-scenarios.html`; evidence pages | PASS |
| UAT-030 | “The best time to decide is when understanding is ready—not simply when the agenda is.” | Connect evidence readiness to decision timing. | `decisions-and-scenarios.html`; `roles-and-decisions.html` | PASS |
| UAT-031 | “Every decision teaches the next.” | Add outcomes, lessons, correction, and institutional memory after delivery. | `strategy-to-results.html`; `roles-and-decisions.html` | PASS |
| UAT-032 | “The goal is not to produce one person's version of Wilbraham. The goal is to help Wilbraham recognize itself.” | Use as a boundary against a one-person or one-place platform identity. | `growth-and-identity.html` | PASS |
| UAT-033 | Explain the platform front-to-back without making a resident inspect every artifact. | One concise platform promise plus a visible connected path and optional drill-through. | `index.html` | PASS |
| UAT-034 | Do not turn the public front door into a comprehensive source catalog. | Keep guided questions primary; inventory is a separate backstage doorway. | `index.html`; `comprehensive-inventory.html` | PASS |
| UAT-035 | Preserve the hard work already completed. | v4.11 remains untouched; its financial doorway, resident story, 30 routes, evidence portal, data, calculations, and original links remain in v4.12. | Preservation crosswalk; `town-finances.html`; reports | PASS-CONTROL |
| UAT-036 | The new work should be part of Whole Picture, with separate spaces where depth would overwhelm the front door. | One platform with guided journeys, reusable evidence rooms, and a separate comprehensive inventory. | Entire IA | PASS |
| UAT-037 | The platform is for Wilbraham, not only the Center. | Public name and scope are townwide; no route calls the platform “Wilbraham Center.” | All public routes | PASS |
| UAT-038 | Wilbraham Center is where Sherie lives and where the work started. | Preserve the Center as the named origin story. | `index.html`; `growth-and-identity.html` | PASS |
| UAT-039 | The Center is a historic residential area with some commercial buildings; proposed expansion raised concern about identity. | Tell this as the origin case, carefully and without turning concern into an established Town motive or outcome. | `growth-and-identity.html` | PASS |
| UAT-040 | Decisions should show the balance between identity and other benefits or burdens. | Compare financial, service, place, identity, traffic/infrastructure, and future consequences together. | `growth-and-identity.html`; scenario frame | PASS |
| UAT-041 | What is lost may not be recreatable. | Treat reversibility and irreplaceability as decision criteria. | `growth-and-identity.html`; `decisions-and-scenarios.html` | PASS |
| UAT-042 | All pictures in Understanding Together are Wilbraham Center pictures. | Record their provenance and constrain any use to Center origin/case-study context, not generic Wilbraham imagery. | `growth-and-identity.html`; source methodology | PASS |
| UAT-043 | A decision for the whole Town should not make one place's distinctive value invisible. | State the townwide/place-sensitive decision principle. | `growth-and-identity.html` | PASS |
| UAT-044 | Ask: How can Wilbraham change, invest, and grow without losing things residents value and cannot recreate? | Use as the central growth-and-identity resident question. | `growth-and-identity.html`; front-door link | PASS |
| UAT-045 | Commercial growth should be evaluated by what it contributes and what it requires. | Connect gross tax/revenue, public cost, infrastructure, services, incentives/support, household effect, and unknowns. | `growth-and-identity.html`; `town-finances.html#commercial` | PASS |
| UAT-046 | Place decisions should ask who experiences the effects. | Include geography, residents, businesses, travelers, service users, and future residents where evidence supports them. | `growth-and-identity.html` | PASS |
| UAT-047 | Some choices can be adjusted later; others permanently change the place inherited. | Make reversibility visible before readiness/approval. | `growth-and-identity.html`; `decisions-and-scenarios.html` | PASS |
| UAT-048 | Reviewed-file inventory should be saved for future platform use. | Keep and link the file-level reviewed inventory created under `00-PLATFORM-REFERENCE`. | `comprehensive-inventory.html` | PASS-CONTROL |
| UAT-049 | The inventory must begin with the Balanced Scorecard and include all subsequently reviewed platform materials. | Present all ten reviewed items with purpose, role, authority, maturity, and limitations through the saved inventory. | Reviewed file inventory; `comprehensive-inventory.html` | PASS-CONTROL |
| UAT-050 | Comprehensive inventory can expand source by source and business function by business function without disrupting user-facing reporting. | Add a separate inventory doorway organized by civic function and source/control type. | `comprehensive-inventory.html` | PASS |
| UAT-051 | The platform may later be commercialized and work created before Town service must be documentable. | Preserve versioned release, provenance, reviewed inputs, authorship/legal notices, timestamps, checksums, and no claim of Town ownership/adoption. | Release controls; footer; inventory | PASS |
| UAT-052 | Quiet legal and trademark material must remain present but not dominate. | Small gray/dark footer outside the storytelling hierarchy. | All public routes | PASS |
| UAT-053 | Headings should not yell or consume the page. | Modest responsive headline scale throughout the new platform packet. | `assets/platform.css`; all new pages | PASS |
| UAT-054 | Navigation should keep readers oriented as they drill down. | Stable left rail, Level/breadcrumb bar, up/home actions, related paths, and bottom sources. | All new routes; existing Level 3 routes | PASS |
| UAT-055 | Do not use the word “Hide.” | No public UI wording that suggests blame; use “See,” “Open,” “Close details,” or “Return to summary.” | All public routes | PASS |
| UAT-056 | The visual direction is navy, dark/light blue, slate, cream, and warm white. | Apply the agreed quiet palette; reserve red for real errors only. | `assets/platform.css` | PASS |
| UAT-057 | Progressive disclosure should work for residents, new hires, specialists, and C-level readers. | Direct answer → evidence → why it matters → limits → sources, with optional detail. | All new routes | PASS |
| UAT-058 | Whole Picture is not merely a report or dashboard. | Describe and demonstrate it as a connected civic decision system and top-level doorway. | `index.html`; platform scope document | PASS |
| UAT-059 | The source inventory needs to include new accepted sources and reviewed platform references with distinct authority. | Keep accepted DB/source contracts separate from working planning/reference artifacts. | `CURRENT-SOURCE-INVENTORY.md`; `comprehensive-inventory.html` | PASS |
| UAT-060 | The comprehensive scope must not invent data or silently discard unresolved questions. | Preserve traceability, defects, data assessment, source limitations, and original report links. | Release controls and inventory | PASS |
| UAT-061 | Every report must say it is a CivicSS analytical working draft, not an official Town or Finance Committee report, and must state the review/approval gate exactly. | Place Sherie's complete wording quietly outside the primary storytelling hierarchy on every public template. | All eleven public HTML templates; `.review-disclaimer` | PASS |
| UAT-062 | CivicSS is not federally registered yet and should use the pre-registration mark. | Use `CivicSS™`, never `CivicSS®`, in the current draft; keep the mark quiet and outside the story. | All eleven public HTML templates; release notes | PASS |

## Verification evidence by route

- `index.html`: platform promise, guided pathways, connected decision path, eight dimensions, Center-origin/townwide boundary, reusable evidence rooms, uncertainty, source inventory, quiet disclaimer.
- `strategy-to-results.html`: `#direction`, `#lineage`, `#resources`, `#measures`, `#learning`, and `#boundary`.
- `portfolio-assets-and-work.html`: `#work`, `#hierarchy`, `#assets`, `#future`, `#request`, and `#gaps`.
- `roles-and-decisions.html`: `#question`, `#roles`, `#gates`, `#delivery`, `#memory`, and `#limits`.
- `decisions-and-scenarios.html`: `#purpose`, `#whole`, `#compare`, `#afford`, `#ready`, and `#learn`.
- `growth-and-identity.html`: `#question`, `#origin`, `#contribution`, `#requires`, `#experience`, and `#reversible`.
- `comprehensive-inventory.html`: `#purpose`, `#functions`, `#sources`, `#references`, `#controls`, and `#gaps`.
- `town-finances.html`, `resident-story.html`, `reports/index.html`, and the 30 parameterized routes in `reports/report.html`: complete carried-forward financial and preserved-report packet with revised orientation and required disclaimer.
- Controls: `PLATFORM-SCOPE-AND-INFORMATION-ARCHITECTURE.md`, `records/PLATFORM-EXPANSION-CROSSWALK.csv`, `CURRENT-SOURCE-INVENTORY.md`, `REPORTING-DATA-ASSESSMENT.md`, `PMO-DATA-DEFECT-REGISTER.md`, and the top-level reviewed-file inventory.

## Final acceptance procedure

1. Read the active conversation again from the Balanced Scorecard comment through the authorization to build v4.12.
2. Compare every user comment and every agreed design conclusion with the matrix above.
3. Add any missing idea as a new UAT row; do not silently fold it into a vague row.
4. Inspect the named implementation target.
5. Mark `PASS`, `PASS-CONTROL`, or `BOUNDARY` only with a precise page/control location.
6. Run text checks for townwide naming, forbidden “Hide” wording, legal notice presence, headings, links, preserved-original links, and source-boundary language.
7. Render and inspect every new page and the existing resident/report drilldowns.
8. Release only when no `OPEN` row remains.