# How the CivicSS™ scenario model turns ideas into a real civic choice

## A front-to-back explanation using the current BUC model

**Civic Stewardship System Atlas reference — August 25, 2026**

> **Make the real civic choices—and the differences between them—visible. Then let people decide what those differences are worth.**

## Direct answer

The scenario model is not primarily a calculator and it is not a voting tool. It is a disciplined way to take several appealing or familiar ideas and discover what the community is **actually** choosing between.

It begins with Wilbraham’s own repeatedly expressed values and public purposes. It then carries every scenario through the same service, asset, legal, regulatory, execution, civic, evidence, and financial questions. That work removes false choices, reveals hidden dependencies, and shows which risks or obligations merely move from one place to another.

Only then does the model calculate a comparable result for each surviving scenario. The difference between those results is not the answer. It is where the most important public judgment can finally begin:

> Is the financial difference and remaining risk worth what this choice preserves, changes, creates, or gives up?

That is where history, small-town character, identity, sense of place, access, control, service quality, equity, and future flexibility become the real decision—not decorative language placed beside a project price.

This is the larger purpose of the system. The necessary evidence is normally distributed across so many sources, disciplines, time periods, and ways of thinking that no person can reliably keep the complete decision in mind. CivicSS™ uses structured evidence, technology, and AI to create a shared state of knowing: what the Town has said it values, what each scenario actually requires, which apparent choices are not real, what remains uncertain, and how the viable paths differ.

The system does not decide what a community should value. It brings people to the point where human judgment can properly begin—judgment about values, identity, lived experience, hopes, priorities, and acceptable tradeoffs—with the best information reasonably available at the time.

## The connection that makes the whole model coherent

The Balanced Scorecard and the scenario model form one loop.

`Wilbraham’s stated values and public purpose`

`→ the outcomes the Town is trying to protect or improve`

`→ the real options, including delay or no action`

`→ consistent service, asset, legal, regulatory, execution, civic, and evidence gates`

`→ complete lifecycle cost, funding, household effect, and risk comparison`

`→ the remaining difference between viable choices`

`→ an explicit balancing decision grounded in Wilbraham’s values`

`→ authorization, delivery, measures, outcomes, correction, and learning`

The first three pages of the current Balanced Scorecard assemble strategic lineage from the 1963 Master Plan, 2013 Vision Report, 2025 Annual Town Report, 2026 Town Meeting and capital/CPC evidence, current meeting evidence, the Library strategy, and the current Town portfolio. They show repeated support for resident service, affordability, safety, education, reliable infrastructure, useful economic vitality, land and history, Town character, and open evidence-based government.

The fourth page—**From Shared Values to Better Decisions: Make the Balancing Choices Visible**—then explains why agreement on those broad ends does not settle a specific choice. A proposal may advance one valued end while creating consequences for another. Its five-question routine is:

1. State the public purpose.
2. Name the tensions.
3. Compare real options.
4. Show what is known.
5. Record the decision.

The BUC scenario model is an applied decision infrastructure for that routine.

The legal, regulatory, operational, and financial hurdles are not separate from the values decision. They make the values decision honest. They prevent residents from being asked whether they prefer a lower headline price, a preserved building, a consolidated service, or a new use when one of those apparent choices cannot lawfully occur, cannot preserve access, depends on missing money, or silently shifts an obligation elsewhere.

## What the resident experiences

A resident does not begin in the database or with a 30-year formula. The resident begins with a recognizable question and moves through progressively deeper perspectives. Each page should answer the question in front of the reader and create a reason to care about the next one.

### Start Here — why this system exists

The opening page establishes the central distinction:

> Public information is not the same as public understanding. Public understanding is not the same as decision readiness.

It introduces the model as a combination of evidence, provenance, reporting, scenarios, governance paths, and resident stories. Its job is not to make complexity disappear. Its job is to make the path through complexity walkable.

### Page 1 — what is the Town actually deciding?

The model first reduces six technical delivery variants to four resident-level choices:

1. **Consolidate at Memorial.** Move selected functions to Memorial and release Town Hall, Little Red School House, and the former Police/IT building. The model preserves a Town-owned version and a developer-owned leaseback version.
2. **Maintain the current arrangement.** Retain and improve the four-building arrangement.
3. **Sell or redevelop Memorial.** Dispose of or redevelop Memorial while initially retaining the other three assets.
4. **Create a Memorial community center.** Repurpose Memorial for broader community use, again preserving Town-owned and developer-owned leaseback versions.

The current answer is not “pick one.” It is: all four choices are clear enough to investigate, but none is ready to narrow, price, or recommend.

This page also establishes the order of reasoning: services and people; buildings and land; law and execution; civic consequences; affordability. Money is deliberately not allowed to make an unworkable or harmful configuration look reasonable.

### Page 2 — have we earned enough confidence to narrow the choices?

The readiness page turns “we need more information” into a controlled register. It repeats the scenario on every row so an answer cannot become detached from the choice it affects.

The current model reports 58 incomplete or review questions for Scenario 1, 55 for Scenario 2, 57 for Scenario 3, and 58 for Scenario 4. These are **counts of unresolved or review questions**, not performance scores and not evidence that the scenario with 55 is preferable to one with 58. A more thoroughly investigated scenario can appear to have more risks simply because more of its risks have been documented.

Each readiness row carries:

- the resident question;
- the answer available from the database today;
- the evidence status;
- why residents should care;
- what would make it ready;
- likely owner or authority;
- the consequence if it remains unresolved; and
- the governing data family.

### Page 3 — what do we really know about the buildings?

The asset-baseline page separates building identity from condition, assessed value from market value, and historical planning evidence from current scope.

For Town Hall, for example, the workbook currently shows:

- FY2026 assessed value: **$2,538,700**;
- source building area: **11,862 square feet**;
- source lot area: **4.8095 acres**;
- FY2027 partial facility adjusted budget allocation: **$53,750**;
- 2021 critical measure: **$46,591**;
- 2021 non-critical measure: **$176,908**;
- 2021 deferred-maintenance measure: **$223,499**;
- 2021 ten-year uninflated measure: **$91,306**; and
- 2021 ten-year inflated measure: **$105,859**.

Those numbers cannot simply be added. The 2021 measures may overlap. They are not a 2026 scope or price. The assessed value is not a sale appraisal. The $53,750 is a partial facility allocation, not the complete cost of owning or operating Town Hall.

This is precisely why the model does not permit a shortcut such as “sell a $2.54 million property, subtract $223,499 of repairs, and call the difference savings.” Each number must first be connected to its real meaning, date, scope, and decision use.

### Page 4 — what changes under each choice?

The scenario-summary page asks the same questions across all four choices:

- What is the core move?
- Who owns Memorial?
- What happens to current services?
- What happens to the other assets?
- What might improve?
- What could be lost or shifted?
- Why is the scenario stopped today?

This is the first true side-by-side view. It prevents each scenario from being told in its own most favorable language.

It also keeps the ownership variants visible. Scenario 1A and 4A preserve Town ownership. Scenario 1B and 4B introduce developer ownership and Town leaseback. That difference changes control, maintenance responsibility, escalation, debt, residual value, purchase and renewal rights, and the Town’s ability to exit or adapt later.

### Page 5 — what would have to be true for this to be reasonable?

The assumptions page converts broad ideas into conditions.

A scenario is potentially reasonable only when:

- every necessary service has an acceptable outcome;
- current and future asset obligations are visible;
- property and approval steps can lawfully and practically occur;
- benefits, harms, access, identity, and mitigation are explicit; and
- recurring and one-time financial obligations fit after existing necessities under credible stress.

This is not a weighted score. A scenario does not become reasonable because it has the most attractive narrative or the lowest apparent price.

### Page 6 — can the Town live within its means after this choice?

Only scenarios that survive the non-financial gates reach the affordability model.

The page uses a household-budget idea:

- reliable money coming in;
- fixed and necessary bills;
- expected increases;
- flexible capacity left;
- one-time savings or an asset sale; and
- borrowing for a large purchase.

The Town equivalent includes recurring levy, aid, receipts and fees; schools, safety, debt, benefits and required maintenance; labor, energy, insurance and other expected increases; debt and cash capacity remaining after necessities; and controlled one-time resources such as grants, reserves or net sale proceeds.

The present BUC model defines 13 financial parameters, but only one is populated: a **30-year analysis horizon**. The other 12—including sale proceeds, renovation cost, annual program revenue, annual lease revenue, annual new property-tax revenue, disposition delay, annual carrying cost, and clearance cost—remain not loaded. Therefore, affordability is honestly displayed as **not calculable** for every scenario.

The page does contain useful Townwide context:

- FY2027 final-voted General Fund authorization: **$57,018,471**;
- HWRSD assessment and debt within it: **$33,094,675**, or approximately **58.0%**;
- other General Fund purposes after that arithmetic subtraction: **$23,923,796**;
- FY2026 maximum levy including exclusions: **$50,069,014**;
- FY2026 actual Townwide levy: **$48,746,259.34**;
- controlled unused-levy-capacity figure: **$1,322,755**;
- historically certified FY2024 free cash: **$4,125,286**; and
- audited debt outstanding as of June 30, 2024: **$12,745,767**.

These are surrounding portfolio facts. They are not BUC capacity or funding.

### Page 7 — what changes when the world changes?

Sensitivity is not a decorative low/base/high chart. It asks what happens when housing values, sale values, borrowing rates, construction prices, lease charges, labor, energy, insurance, school obligations, state aid, or pension pressures change.

The current workbook can show a standardized distribution of each additional $1 million of Townwide levy across aggregate FY2026 assessed-value bands. Under its uniform candidate-base allocation, the average eligible parcel effect is approximately:

| Assessed-value band | Eligible parcels | Band assessed base | Average parcel effect for each additional $1 million of levy |
| --- | ---: | ---: | ---: |
| Under $250,000 | 654 | $72,005,812 | $40.64 |
| $250,000–$399,999 | 1,952 | $656,371,720 | $124.11 |
| $400,000–$599,999 | 2,354 | $1,132,113,709 | $177.51 |
| $600,000–$999,999 | 843 | $603,221,524 | $264.11 |
| $1 million and over | 100 | $245,622,922 | $906.58 |

This is not an actual bill, a forecast, a capacity result, or a recommendation. It is an aggregate distribution reference. A BUC scenario still needs an annual Town funding amount and a controlled levy-to-household bridge before this reference can become a scenario impact.

### Page 8 — which obligations remain, transfer, or are newly created?

The lifecycle page follows responsibility over time. It asks what the Town will own, lease, operate, insure, renew, transfer, guarantee, or later need to replace.

Selling a building does not automatically eliminate an obligation. The cost can reappear as rent, a replacement facility, transition work, loss of future control, retained access responsibility, or a lower sale price. Retaining a building does not automatically preserve value if necessary work continues to be deferred.

### Page 9 — can the Town lawfully and practically carry it out?

The executability page identifies prerequisites, responsible authorities, sequence, stop points, and fallbacks. An attractive idea cannot proceed merely because the financial model produces a favorable number.

This is where the Senior Center access example becomes a controlled decision condition.

### Page 10 — who gains, who loses, and what must be protected?

The civic-value page makes service continuity, public access, historic identity, traffic, parking, neighborhood effects, equity, affordability, future flexibility, and accountability visible across every scenario.

These consequences are intentionally open rather than scored. For each one, the model should eventually state:

- the people or place affected;
- the current baseline;
- what changes;
- the mitigation or benefit commitment;
- the responsible owner;
- how it is funded;
- how it will be measured; and
- what triggers correction.

This page is where Wilbraham’s strategic lineage returns to the decision. The Town’s stated concern for small-town character, history, shared places, senior services, access, affordability, useful growth, and future flexibility becomes a set of observable decision consequences.

### Page 11 — what evidence is actually present?

The evidence snapshot shows database coverage without implying completeness. The current model contains:

- 4 resident-level scenario families;
- 6 delivery variants;
- 6 working versions with no effective date;
- 4 explicit potentially blocking property issues;
- 12 required property investigations, all not started in the reviewed snapshot;
- 13 financial parameter definitions, with only the 30-year horizon populated;
- 78 scenario-readiness diagnostic rows; and
- 466 current source artifacts available through the cited provenance surface.

This page also distinguishes present, partial, review-required, unresolved, unspecified, not linked, and not loaded.

### Page 12 — where could the model create false confidence?

The evidence-observations page identifies the most material ways a polished scenario could mislead:

- treating a working configuration as a Town proposal;
- treating an assumed action as approved;
- treating an incomplete service inventory as complete;
- treating 2021 planning evidence as current scope;
- treating a partial facility allocation as full ownership cost;
- treating undocumented constraints in other scenarios as proof that no constraints exist;
- treating a missing scenario value as zero; or
- treating an assessed value as a sale appraisal.

The page’s strongest lesson is that a scenario with more documented risks may be better understood—not necessarily worse.

### Page 13 — what research changes the most decisions?

The research page orders evidence work by decision leverage. It begins with the common service and building baseline, then current condition, then triggered legal and site questions, then scope and design, lifecycle and operating cost, governance and authority, comparable ownership/leaseback terms, funding and household effect, resident evidence, and assigned research ownership.

This prevents the process from spending money on a headline project estimate before it knows what must be built, preserved, moved, or legally accomplished.

### Page 14 — what is the responsible sequence?

The decision schedule separates a knowable sequence from unsupported calendar dates:

0. Define the choices.
1. Establish services and the current baseline.
2. Confirm that each property action can occur.
3. Define what each scenario actually requires.
4. Identify the potentially feasible choices.
5. Test affordability only for the survivors.
6. Prepare the public and reviewing-body explanation.
7. Verify who may decide and by what vote.
8. Implement, monitor, and correct the authorized commitment.

Each stage has a continue condition and a stop or fallback rule. Dates remain unknown until owners, dependencies, and durations exist.

### Page 15 — how does the workbook ask the database better questions?

The last page keeps the technical material behind the resident story. It teaches a reusable query shape:

`decision subject + scenario + question + value + unit + source + as-of date + evidence status + confidence + conflict + owner + next action`

It also documents a read-only Excel-for-Mac ODBC path using the `CSKE_Local` system data source. Credentials are not embedded. Refreshing the current landing table returns six working scenario-version rows.

Importantly, the workbook states that the small live landing table proves the connection path; it does **not** mean all resident-facing pages automatically rebuild themselves from refreshed data. That remains a technical maturity gap.

## One issue followed through the whole model: Senior Center parking and access

The possible sale of Town Hall makes this an excellent example because it looks small beside a multi-building transaction but can change the entire scenario.

### 1. The initial idea

Scenario 1 proposes consolidating selected municipal functions at Memorial and releasing Town Hall, Little Red School House, and the former Police/IT building. Scenario 1A models Town-owned consolidation; Scenario 1B models developer ownership and Town leaseback.

At this level, Town Hall appears to be one of three properties that might produce value or reduce building exposure.

### 2. The asset evidence

The model knows Town Hall’s source identity, FY2026 assessed value of $2,538,700, source building area of 11,862 square feet, lot area of 4.8095 acres, partial FY2027 facility allocation of $53,750, and historical 2021 planning measures.

None of those values answers whether the Senior Center depends on Town Hall land for vehicles, ADA access, emergency access, utilities, drainage, or parking. None is a title examination, legal survey, engineered access design, current appraisal, or complete ownership cost.

### 3. The reasonableness condition

Page 5 states the condition plainly: **Senior Center access survives Town Hall disposition.**

The database answer is `UNRESOLVED`. The required evidence is a title/access audit and a permanent engineered and legal solution.

This moves the question from “Can we sell Town Hall?” to “Can we sell Town Hall without impairing another public service or creating an unfunded replacement obligation?”

### 4. The execution gate

Page 9 records two explicit Scenario 1 requirements:

- In Scenario 1B, Senior Center access must be protected before `BUNDLE_FOR_DISPOSITION`.
- In Scenario 1A, it must be protected before `SELL`.

Both are categorized as `ACCESS`, both are `UNRESOLVED`, both are potentially blocking, and the failure outcome is `ACTION_UNAVAILABLE`.

The model preserves real fallbacks rather than forcing a yes/no answer:

- place permanent rights over the conveyed parcel;
- retain or subdivide the access corridor;
- create enforceable shared-access and parking rights;
- construct independent access;
- exclude Town Hall from the transaction; or
- abandon the Town Hall disposition.

### 5. The civic consequence

Page 10 asks whether consolidated activity and Senior Center access can work safely. The answer must consider hours, ADA routes, vehicle movements, emergency access, parking demand, affected residents, neighborhood effects, and the durability of any mitigation.

This is not merely a legal closing condition. It concerns dignity, aging in place, service continuity, safety, and trust—all values already present in Wilbraham’s strategic lineage.

### 6. The financial consequence

No access-solution amount is loaded today. That missing value must remain missing—not zero.

When evidence becomes available, the model should distinguish among:

- an independent-access construction cost paid by the Town;
- a reduction in gross or net sale proceeds caused by an easement or retained corridor;
- engineering, survey, title, legal, permitting, drainage, lighting, maintenance, and snow-removal costs;
- delay and carrying cost while the issue is resolved;
- a developer obligation that may reappear in the lease price; and
- the long-term value and enforceability of the access right.

The same physical solution can therefore affect capital cost, transaction proceeds, annual operating cost, timing, legal risk, control, and service quality differently in Scenario 1A and Scenario 1B.

### 7. The scenario outcome

If permanent access is established, its cost, risk, timing, and operating responsibility become part of the relevant Scenario 1 result.

If access cannot be established or the solution is unacceptable, the Town Hall sale is not available in that configuration. The scenario must use a fallback, be revised, or stop.

This is how a parking/access question can change the financial result, the list of feasible options, and the final preservation and identity choice without ever being reduced to “just a parking issue.”

## What the final scenario number should mean

The current workbook does **not** yet produce a final dollar result for any BUC scenario. It is important to say that directly. The current 55–58 readiness counts are not those results, and affordability is expressly not calculable because 12 of 13 financial parameters lack values.

The intended end state should produce a comparable financial result for each scenario family and retain the delivery variants where ownership changes the answer.

At minimum, each result should include:

1. **Thirty-year net Town resource cost.** The complete cost of capital, transition, operation, lease obligations, renewal, mitigation, retained obligations, and exit—less controlled net proceeds, eligible outside funding, and scenario revenue.
2. **Annual Town cash path.** The amount required in each fiscal year, showing debt service, rent, operating subsidy, one-time spending, revenue, and timing separately.
3. **Peak and recurring annual burden.** The amount that must be sustained rather than financed once.
4. **Household impact range.** A scenario-linked distribution by funding type and assessed-value band, with representative-household and affordability context where supported.
5. **Low, base, and high cases.** Construction, rates, sale timing/value, operating cost, lease escalation, revenue, and other material uncertainties.
6. **Residual and control position.** What the Town owns or controls at the end of the horizon and what renewal, purchase, exit, guarantee, or replacement exposure remains.

A conceptual lifecycle equation is:

`net lifecycle resource cost`

`= current and new capital work`

`+ transition and continuity cost`

`+ operations, subsidy, maintenance, lease and renewal obligations`

`+ access, mitigation, clearance, carrying and exit obligations`

`− controlled net sale proceeds`

`− eligible and available grants, CPA or partner funding`

`− supported program, lease or tax revenue attributable to the scenario`

The technical implementation must avoid double counting. For example, a Town-owned capital asset’s project cost and the principal portion of its debt service are two views of the same financed resource—not two separate economic costs. The model should show lifecycle resource cost and taxpayer cash timing separately. It also should not call a 30-year total “net present value” unless a controlled discount-rate and dollar-basis method is added.

The target comparison should eventually look like this:

| Resident-level scenario | Delivery distinctions retained | Current financial result | What must be true before a number is published |
| --- | --- | --- | --- |
| Scenario 1 — Consolidate | 1A Town-owned; 1B developer leaseback | Not calculable | Services fit; access/title/property actions; renovation and transition scope; proceeds; debt or lease terms; lifecycle and household bridge |
| Scenario 2 — Maintain | 2A current arrangement | Not calculable | Current condition; exact improvements; full operating and renewal cost; funded phasing; service measures |
| Scenario 3 — Sell/redevelop Memorial | 3A disposition/redevelopment | Not calculable | Function outcomes; defined redevelopment; authority and timing; appraisal and net proceeds; transition and retained obligations |
| Scenario 4 — Community center | 4A Town-owned; 4B developer leaseback | Not calculable | Program/operator; code and site scope; capital or lease terms; annual subsidy/revenue; access, equity and lifecycle |

## Why the difference between scenario numbers is the beginning—not the end

Once comparable numbers exist, the model should not automatically rank the least-cost scenario first.

Suppose two scenarios differ by a defensible 30-year amount. The community can then ask:

- What service improvement or loss accompanies that difference?
- What historic place or recognizable character is preserved or irreversibly changed?
- Who gains access and who loses it?
- Which scenario retains public control or future flexibility?
- Which risks are transferred, and which only appear to be transferred?
- What mitigation is enforceable?
- Does the less expensive choice depend on optimistic proceeds, incomplete lease terms, or a larger tail risk?
- Does the more expensive choice protect a public value Wilbraham has repeatedly said matters?
- What result would make the difference worth paying—or not worth paying?

This is the purpose of the fourth Balanced Scorecard page. The system should make the legitimate tension visible rather than hide it inside a recommendation.

The final decision record should therefore preserve two connected but distinct products:

1. **The comparable financial and risk result.** What each viable scenario costs, when, under what assumptions, with what household and portfolio consequence.
2. **The public-value balancing record.** Which shared ends were advanced or burdened, which consequences were accepted, which mitigation was required, who made the decision, and what measure will show whether the promised result occurred.

The financial model narrows the ambiguity. It does not erase the civic choice.

## Technical implementation

### 1. Evidence and source layer

The source layer preserves official records, supplied materials, dates, authority, file identity, source hashes, processing status, and limitations. A material scenario claim should be traceable to the exact evidence that supports it.

### 2. Canonical subject layer

Buildings, parcels, addresses, civic functions, funds, authorities, and other subjects receive stable identities. Source-reported names and values remain preserved rather than silently overwritten.

### 3. Scenario configuration layer

The current model uses:

- `scenario_family` for the four resident choices;
- `scenario_variant` for the six delivery forms;
- `scenario_version` for dated working configurations;
- `scenario_asset_action` for retain, maintain, renovate, sell, bundle, leaseback, repurpose, or other actions;
- `core_ref_civic_function` and `scenario_function_assignment` for service continuity;
- `scenario_delivery_component`, `scenario_leaseback_term`, and `scenario_risk` for ownership and delivery terms; and
- explicit status fields so working, assumed, contingent, unresolved, approved, and unknown are not conflated.

### 4. Feasibility and execution layer

`scenario_execution_requirement`, `property_constraint`, and `property_constraint_investigation` carry prerequisites, blocking potential, required-before actions, responsible authorities, evidence status, failure outcomes, and fallbacks.

The access example is implemented here. It is not merely narrative text: it is associated with the affected scenario variants and actions and can prevent the configuration from advancing.

### 5. Asset and lifecycle layer

Capital assessment properties, recommendations, observations, schedules, accounting allocations, asset registers, work completion, current condition, useful-life assumptions, and renewal windows should establish the obligations each scenario retains, transfers, or creates.

Historical source measures remain separate. Missing and zero remain distinct.

### 6. Financial-input and calculation layer

`scenario_parameter_definition` supplies consistent parameter names and units. `scenario_parameter_value` should carry the scenario, numeric/text value, assumption status, source, as-of date, basis, and low/base/high case.

The calculation engine should produce auditable annual schedules before summaries. Important intermediate values—gross proceeds, transaction cost, clearance cost, access mitigation, debt or lease payments, operating changes, renewal, residual value, and household allocation—should remain visible rather than being hidden inside one formula.

### 7. Evidence-status and readiness layer

The reporting layer must preserve states such as:

- `WORKING`;
- `ASSUMED`;
- `PRESENT`;
- `PARTIAL`;
- `REVIEW_REQUIRED`;
- `UNRESOLVED`;
- `UNSPECIFIED`;
- `NOT_LINKED`;
- `NOT_LOADED`; and
- `NOT_TRIGGERED`.

These are not interchangeable. A not-triggered sale-proceeds question in a retain scenario differs from a missing sale-proceeds value in a disposition scenario.

### 8. Reporting and progressive disclosure layer

Resident pages should lead with the direct answer, then evidence, importance, limitations, and source drill-through. Technical tables and query contracts remain available without forcing every reader to begin there.

The model should let a resident move in both directions:

- downward from public purpose to the source record; and
- upward from one source fact to the scenario, consequence, decision stage, and public value it affects.

### 9. Refresh and validation layer

The current proof of concept uses a read-only `CSKE_Local` ODBC path and a six-row scenario-version landing table. Credentials are not embedded. The query path should fail visibly when data is unavailable or schema expectations change.

A mature implementation should refresh every SQL-backed number from accepted reporting contracts, display source object and as-of time, reconcile counts and totals, preserve fallback state, and prevent an unaccepted object from silently entering resident reporting.

### 10. Decision, delivery, and learning layer

After a choice is authorized, the model should not end. It should record:

- who decided and under what authority;
- what was authorized and funded;
- conditions, fallbacks, and mitigation commitments;
- implementation owner and milestones;
- actual cost and outcome evidence;
- service and resident effects;
- correction triggers; and
- what the next decision should learn.

That closes the Balanced Scorecard management loop.

## Limitations and unresolved questions

1. This explanation describes the preserved BUC Resident Decision Journey v1.6, whose scenario snapshot is dated August 16, 2026 and connected evidence review is dated August 20, 2026.
2. The current workbook is an independent prototype, not a Town of Wilbraham system, adopted recommendation, official financial model, legal conclusion, or approval record.
3. The six scenario versions are `WORKING` and have no effective date.
4. Twelve of thirteen current scenario financial parameters have no values. No BUC scenario result, tax effect, or affordability conclusion is currently supportable.
5. The current readiness counts are diagnostics, not scores or rankings.
6. Pages 1–14 are a controlled reviewed snapshot. The current ODBC landing table does not automatically rebuild every resident page.
7. The 2021 capital evidence is historical and requires a completed/open/superseded/rescoped/current-condition bridge before it can become current scenario scope.
8. Assessor snapshots are not appraisals, title evidence, legal surveys, certified bills, or proof of usable program area.
9. The latest accepted CNA narrow projection work became available after the workbook’s August 20 evidence review and is not silently treated here as though v1.6 already adopted it.
10. The Balanced Scorecard labels the historical source as the **1963 Master Plan**. Sherie referred to “1964” in the discussion that produced this insight. The intended historical citation should be reconciled rather than silently normalized.
11. Civic consequences are not currently supported by a complete scenario-linked resident evidence or enforceable mitigation package.
12. The final end-result definition still requires a controlled dollar basis, inflation/escalation treatment, discounting decision if present value is desired, debt-versus-resource-cost presentation, residual-value method, and household-allocation contract.

## Sources and methodology

This explanation was developed by reading every sheet, populated cell region, and available formula in the preserved workbook; visually reviewing all 16 workbook sheets, including the four-part readiness register; tracing the Town Hall/Senior Center access issue across the assumption, execution, civic, research, schedule, asset, financial, and database pages; and reading all four pages of the preserved Balanced Scorecard workbook.

Primary source artifacts:

- **CSKE BUC Resident Decision Journey v1.6 — August 20, 2026**  
  SHA-256: `73ba2eed565f0bca38491a87b3300d444310a17a033c1c8dc20969d5e0ed7f0a`
- **Wilbraham Balanced Scorecard — August 24, 2026**
- CSKE source and reporting surfaces identified inside the BUC workbook, with their stated evidence-status and decision-use boundaries preserved.

No database state, source workbook, Town record, deployment, or external control state was changed in producing this explanation.

---

**Preserved source workbook:** [`CSKE-BUC-Resident-Decision-Journey-v1.6-20260820.xlsx`](source-snapshots/20260825/private-local-only/07-scenarios/CSKE-BUC-Resident-Decision-Journey-v1.6-20260820.xlsx)

**Preserved Balanced Scorecard:** [`Wilbraham-Balanced-Scorecard-Four-Print-Pages-Share-Copy-20260824.xlsx`](source-snapshots/20260825/private-local-only/01-strategy/Wilbraham-Balanced-Scorecard-Four-Print-Pages-Share-Copy-20260824.xlsx)

*CivicSS analytical working draft—not an official Town or Finance Committee report. Prepared from identified public and supplied sources for discussion and review. Source data has not been independently audited or certified by Sherie Schaefer. Do not use for an official presentation until the supporting data has completed the appropriate Town review and approval process, including Finance Committee review when applicable.*