Fresh read-only PostgreSQL queries, validated controls, source schema/view, captured time, and fail-closed fallback behavior. Current examples include accepted ATM, DLS/MassGIS, and narrow CNA uses within their contracts.
Source by source · function by function · question by question
The comprehensive inventory is the backstage map of everything Whole Picture can ask, answer, connect, or still needs.
It lets the platform expand without crowding the resident doorway. Each item keeps its original source, intended meaning, current implementation, refresh behavior, validation state, limitation, and unresolved next action.
The public story begins with a resident question. The comprehensive inventory makes sure no useful question, data point, source relationship, limitation, idea, or preserved path disappears behind that simplicity.
02 · Civic capability inventory
Which parts of the whole civic system have a reporting home?
Direct answer
The architecture now has a home for direction, resident experience, work, assets, money, authority, choices, evidence, delivery, and learning.
Coverage and maturity differ. The table distinguishes a functioning reporting route from a platform capability that still needs normalized data or governing decisions.
| Business function | Resident question | Current doorway | Current state |
|---|---|---|---|
| Purpose, strategy, and measures | What is Wilbraham trying to accomplish, and how would we know? | Strategy to results | Reviewed working foundation; normalized/adopted register still needed. |
| Resident experience and learning | What are people experiencing, and what have we not yet understood? | Guided stories | Question-led architecture active; experience data varies by story. |
| Budget, revenue, levy, and household | What is the Town carrying, what pays, and what reaches households? | Town finances | Several accepted live contracts plus dated preserved bridges and explicit gaps. |
| Portfolio, program, project, and follow-up | What work is underway, how does it fit, and what must not be lost? | Work and assets | Substantial working register; completeness and normalization vary. |
| Assets and capital lifecycle | What has been entrusted, what condition is it in, and what comes next? | Assets and obligations | Candidate registers, Memorial pilot, and bounded accepted CNA projection contract. |
| Roles, authority, and accountability | Who recommends, decides, delivers, measures, and corrects? | Roles and decisions | Older working role map plus accepted decision records; current authority must be confirmed. |
| Alternatives, affordability, and readiness | What would each choice require, change, and leave behind? | Scenarios and readiness | Working scenario framework; incomplete alternatives are not ranked. |
| Growth, commerce, place, and identity | What does growth contribute and require, and what could be lost? | Growth and identity | Gross tax/revenue evidence; net public-cost/support bridge still blocked. |
| Evidence, defects, provenance, and refresh | Where did the information come from, and how trustworthy is it? | This inventory and release controls | Traceability, source inventory, defects, data assessment, freshness, and preservation active. |
| Delivery, outcomes, and institutional memory | What happened after the decision, and what should the next choice learn? | Results and learning | Architecture active; complete decision-to-actual-to-outcome bridges still developing. |
03 · Evidence authority
Which evidence can a report use—and how?
Direct answer
Evidence is organized by authority and permitted use, not by how polished the file looks.
Accepted live reporting contracts control current SQL-backed claims. Dated preserved reporting remains visible with its period and limitation. Working platform materials shape questions and architecture without being silently promoted as accepted municipal facts.
Earlier reports, source displays, calculations, questions, narrative paths, and limitations retained with original dates. They remain useful without being called current.
Source/page material that may reveal a promising fact but cannot yet support a normalized public claim. It remains inventory or follow-up.
Scorecard, portfolio, roles, asset, scenario, and learning materials that define capabilities, questions, and relationships. Their maturity and factual authority stay explicit.
Open the current source inventoryOpen the structured source registerOpen the current refresh statusOpen reporting authority and boundaries
Checking the current reporting refresh state…
04 · Reviewed platform foundations
Which files shaped the expanded platform?
Direct answer
Ten named platform references were inventoried beginning with the Balanced Scorecard and continuing through portfolio, assets, roles, scenarios, and Understanding Together.
The saved reference inventory records exact path, version/hash, review depth, platform role, useful concepts, authority, maturity, and limitations. It is the durable starting point for later platform work.
- Balanced ScorecardScorecard map, strategic lineage, plan/library traceability, and balancing choices.
- Portfolio/program/project materialsWorking portfolios, program architecture, managed work, evidence, and follow-up.
- Physical/capital and software/data asset materialsAsset stewardship, candidate registers, lifecycle, and information continuity.
- Memorial asset pilotA place-dossier pattern connecting identity, function, condition, work, evidence, and choices.
- Town Roles workbookOlder but necessary role, authority, accountability, and guidance foundation.
- BUC decision journeyScenarios, affordability, sensitivity, lifecycle, executability, civic value, evidence, and readiness.
- Understanding TogetherQuestion-led civic learning, stewardship dimensions, tradeoffs, uncertainty, readiness, reversibility, and institutional memory.
05 · Preservation and traceability
How does the platform simplify the story without losing the evidence?
Direct answer
Every public route must remain traceable to the original question, source, meaning, implementation, refresh behavior, validation result, limitation, and preserved predecessor.
v4.12 adds pages above the current reporting. It does not delete v4.11 or the earlier portal. The prior financial doorway is copied as town-finances.html; the resident story, thirty lower-level routes, accepted data snapshot, SQL, calculations, controls, and original links remain.
Complete report traceability matrixEvery preserved public question and numeric display occurrence with source and current implementation.Preservation inventoryThe retained source files and evidence paths.Lower-level report crosswalkEvery distinct preserved report and its current route.Platform expansion crosswalkHow the new strategy, work, assets, roles, scenarios, place, and inventory layers map to their foundations.Conversation-to-report UATEvery idea and design conclusion since the Balanced Scorecard discussion, with its required public location.Prior v4.11 doorwayThe accepted predecessor remains untouched and directly reachable.
Why it matters
Preservation protects the story; traceability makes improvement safe.
New data can strengthen, correct, or replace an earlier representation without erasing why the question mattered, how residents understood it, which calculation was used, or which uncertainty still needs resolution.
06 · Data quality and next actions
Where is the platform prevented, restricted, or still learning?
Direct answer
The release keeps defects, normalization needs, essential missing sources, and helpful additions separate.
Each finding names the affected question, object or missing source, evidence, user impact, severity/criticality, recommended owner or action, current report handling, and validation needed. Confirmed defects remain distinct from suspected problems and missing evidence.
PMO data defect registerCriticality shows when a source or claim is blocked, restricted, or usable with qualification.Reporting-data assessmentProblematic data; normalization needs; essential missing sources; helpful non-critical data.Reconciliation and coverageWhich report-level controls and coverage checks passed or remain unresolved.Release validationStructure, links, content, refresh, preserved paths, wording, and acceptance status.
Version, provenance, and legal record
What this release documents
Release v4.12.0 is a dated, independently developed reporting prototype built before any implied future Town role or ownership. It records its preserved predecessor, reviewed inputs, implementation crosswalk, evidence status, release notes, validation, checksums, and unresolved items. Nothing on this page represents Town adoption, official advice, deployment, or a change to official records.
Open the untouched preserved 2026 reporting portal