Follow a decision—not a document.
Connect the need, alternatives, recommendation, vote, funding, contract, spending, implementation, and result without asking one document to tell the entire story.
Journey 3 · connected-data exploration · August 16 catalog + August 17 Cherry Sheet layer
What could Wilbraham understand when its records are connected?
This route is for the Town Administrator, Town staff, boards, committees, and others who want to glimpse the breadth of information already available—and the new questions that become possible when separate records can be followed as one decision story.
Short answer: the August 16 catalog documented 382 base tables, 122 views, 410 registered source artifacts, typed measures and periods, lineage, and ten stable reporting views. The next load added a concrete example of why that structure matters: 28 years of municipal and regional-school state-aid and charge history, with every source row, printed total, exception, and reconciliation preserved. Town context and additional records can make the next answers substantially more useful.
For Town administration, staff, boards, and committees
This is a glimpse of what connected data can make possible.
The aim is not to inspect Town work from the outside. It is to bring the operational knowledge already held across Town government together with records that can preserve context, follow a choice over time, and make a public explanation easier to reproduce.
A collaborative premise
This prototype begins with a simple request: help me understand how Wilbraham's records fit together. When someone points to the right source, explains a business rule, or identifies the missing bridge between two records, the analysis becomes more accurate—and that knowledge can become reusable for the next budget, project, grant, or public question.
See what else the choice touches.
Place a building, staffing, school, debt, or service proposal beside the commitments drawing on the same money, people, assets, and future capacity.
Show why a number changed.
Separate local choices, existing obligations, timing, inflation, state or regional factors, and accounting scope so a change can be explained instead of merely reported.
Make the next data request specific.
Rather than asking broadly for “more data,” identify the exact record, relationship, business rule, or current update that would unlock the next answer.
Breadth already available
The scale matters because many different questions can now meet in one place.
Schema size is not the public value by itself. The opportunity is the ability to connect a decision to its baseline, authority, funding, future obligations, assets, services, household effect, and original evidence without losing the distinctions among them.
Domain facts, source detail, relationships, reference data, and controls.
Includes ten stable versioned reporting contracts.
Structure reduces ambiguity but does not prove business completeness.
Registration means traceability—not automatic current authority or interpretation.
Additional schema controls at the August 16 checkpoint
The catalog records 1,190 indexes, 466 check constraints, 382 primary keys, 500 unique constraints, 55 triggers, and 34 functions. The database ran PostgreSQL 18.4 at capture. These are implementation controls; report acceptance still depends on measure identity, reconciliation, freshness, and complete decision relationships.
Checkpoint boundary
Those catalog counts remain an exact August 16 snapshot. The Cherry Sheet migration was accepted on August 17 and is intentionally described separately rather than silently changing the older catalog totals.
A new, concrete example
One source family now connects 28 years of state aid, charges, printed totals, and source changes.
This is the kind of addition that can draw someone into the data: not “we loaded more rows,” but “we can now ask how state support changed, whether it kept pace, and where the local funding requirement came from.”
Wilbraham municipal C.S. 1-ER and HWRSD C.S. 2-ER final budget estimates.
Every source file is connected to its entity, period, family, version, and locator.
Totals remain controls and are not counted again as detail.
Historical source gaps and unusual signs stay visible; none remained open or error-severity in the supplied result.
What this unlocks
We can now separate general aid from reimbursements and offsets; follow Chapter 70, transportation, school-choice, charter, veterans, library, and assessment lines across time; compare them with compatible budgets and levies; and identify the exact monthly-payment or assessment bridge still needed before an estimate becomes actual revenue evidence.
See the FY2027 answer before the database
Two short equations explain the municipal and HWRSD sheets, then the reader may continue into recent and 28-year history.
Download 56 annual entity-year rows
Receipts, charges, net effect, source file, report type, and evidence qualification.
Download 1,023 controlled detail rows
Original labels and locators, conformed line items, flow and availability types, values, assurance, verification, and notes.
Start with the question you are trying to answer
The Whole Picture becomes useful when the question can travel across the records.
Begin with a short answer. Open the evidence only when you want it. Each question is labeled answered now, newly measurable, or not yet determinable so increased data does not create false certainty.
AffordabilityWhy did the tax burden change?
Separate assessment, levy, rate, and class effects.
Current baseWho carries today’s taxable value?See the current residential, commercial, and industrial shares.
Property historyHow has a parcel changed?Use MassGIS history and detailed Town/Vision cards for different purposes.
ScenarioHow might a proposed annual cost be distributed?Use an assessed-value sensitivity without predicting a tax bill.
Future obligationsWhat Town and school debt is scheduled?See the annual load through FY2040 and FY2041.
Decision capacityHow much room is there for something new?See why legal room and debt roll-off are not a complete affordability answer.
Open the complete Questions We Can Answer library → It includes the parcel-source comparison, short answers, supporting evidence, boundaries, and deeper links.
See additional connected questions already preserved in this report
What changed between proposal, vote, budget, account, spending, and outcome?
Town Meeting and accounting records can already be viewed together. An approved line-to-account bridge and service measures would let the same question continue through implementation and results.
What would one facility choice mean for the whole Town portfolio?
Assets, parcels, 2021 conditions, current accounts, projects, debt, grants, and BUC scenarios are visible. Current conditions, utilization, complete option scopes, and lifecycle costs would make the comparison far more decision-ready.
How much of a change reflects local choice, an existing commitment, or an outside condition?
Multi-year budgets, HWRSD, benefits, debt, revenue, and tax records provide a foundation. Current operating assumptions and explanatory context could distinguish timing, policy, inflation, labor, construction, state, and regional effects.
Did state aid keep pace with the costs it helps support?
The new Cherry Sheet history provides final budget-stage aid and charges for Wilbraham and HWRSD. Compatible budget, member-assessment, monthly distribution, and actual-receipt records can now turn that trend into a funding bridge.
What will still require money five, ten, or twenty years after the first vote?
Debt, pensions, OPEB, capital evidence, and recurring accounts can be brought beside a proposal. Staffing benefits, maintenance, renewal, contracts, and replacement schedules would complete the future-obligation view.
Which grant or reimbursement truly reduces Town cost—and when?
Programs, instruments, awards, and source evidence are registered. Eligibility, authorization, receipt, match, allowable use, accounting, reimbursement timing, and closeout records would show the actual Town benefit.
How does a financial choice reach households and the services they experience?
Levy, tax rates, parcel examples, budgets, and broad service classifications can frame the question. Scenario tax distributions and comparable service measures would show who pays, who benefits, and what changes.
Evidence pipeline
Every conclusion should be traceable back through six layers.
A source can be faithfully extracted and still be the wrong period or scope for a decision. Each layer adds a different control.
01Source artifact and version
02Physical extraction and locator
03Typed business fact
04Conformed period, unit, entity, and relationship
05Versioned reporting contract
06Resident, analyst, or decision view
Where did it come from?
Artifact family, version, page/line or record locator, load, and transformation notes support traceability.
What exactly does it measure?
Value, unit, entity, fund, period, accounting basis, lifecycle stage, and evidence state prevent false comparison.
Is it sufficient for this question?
A dated or partial fact can identify an issue without proving current cost, capacity, affordability, or the best alternative.
Domain map
The database is organized around connected public questions.
Counts below describe the controlled records most useful for reporting. They are not summed into a single “amount of data” score.
43 articles · 93 motions · 34 votes
Annual Town Meeting
Answers: what was proposed, recommended, moved, amended, and voted; how three budget versions relate.
Also holds: 294 budget lines, 1,764 budget facts, six source documents, 104 pages, 4,558 source lines, and 11 follow-ups.
Cannot alone answer: later spending, service outcome, or account-level actuals.
473 FY2027 accounts
Town accounting
Answers: adjusted expenditure authority, spending to the extract date, unexpended balance, department, fund, object, and analytical classifications.
Scope: 48 departments, 14 funds, 101 objects; $66.372 million across six fund families.
Cannot alone answer: service outcomes, beneficiary allocation, or responsible cuts.
Budgets · aid · enrollment · member burden
HWRSD and schools
Answers: District budget trends, category changes, reported enrollment, net state aid, member allocations, audit/disclosure facts, and District debt evidence.
Key boundary: District total ≠ Wilbraham amount; FY2026 79.9% capital allocation is not a permanent forecast.
Cannot yet answer: the next official allocation or complete cost-driver/service model.
56 documents · 28 years
Cherry Sheet aid and charges
Answers: final budget-stage municipal and HWRSD receipts, charges, line-item history, source presence, printed controls, and year-over-year change.
Control: Town and District remain separate; estimates, actual payments, budgets, and member assessments are not substituted.
Cannot yet answer: actual receipt, unrestricted availability, or the complete local-funding bridge.
20 issues · 64 positions · 112 service rows
Debt and securities
Answers: issue identity, issuer, purpose, authorization, dated positions, contractual cash flows, interim/permanent financing, and refunding relationships.
Control: prevent temporary notes and permanent takeout from being counted as two obligations.
Cannot alone answer: affordability, excluded tax effect, or project lifecycle cost.
22 assets · 30 buildings
Assets, facilities, and projects
Answers: managed asset/building identities, parcel links, civic function, five connected capital projects, project components, costs, funding, operating context, and service metrics.
Cannot yet answer: current complete utilization, condition, lifecycle plan, or every asset's total ownership cost.
17 properties · 438 recommendations
2021 capital assessment
Answers: point-in-time conditions, 147 observations, 448 schedule occurrences, source locators, and original 2022–2031 projection fields.
Control: $3.595m uninflated and $4.126m inflated are separate study measures; deferred maintenance may overlap.
Cannot answer: current condition, completed work, current bids, or approved capital plan.
197 current card records
GIS and parcels
Answers: source-card assessment, land, construction, ownership, sale, note, and parcel/account mappings.
Controlled ownership: 171 meet the Town-owned test; three name another current owner and 23 lack a current ownership row.
Cannot answer: whether a parcel is surplus, developable, unrestricted, or worth its assessed value in a sale.
48 programs · 117 instruments · 68 awards
Grants and funding
Answers: programs, instruments, eligibility/research leads, award-like records, amounts, evidence states, and source lineage.
Readiness: only five awards are explicitly received and one more reported received in the prior controlled extract.
Cannot answer: cash receipt, allowable use, match, accounting, expenditure, or closeout without lifecycle evidence.
Statements · schedules · notes
Financial reporting
Answers: audited statements, General Fund facts, note and schedule details, pensions, OPEB, capital assets, revenues, balances, and continuing-disclosure observations.
Control: audit, RSI, disclosure, budget, and calculated results carry distinct assurance states.
Cannot be substituted for: a later-year budget, current cash, or a decision-level forecast.
Readiness before ranking
Decision inputs and alternatives
Answers: which scenario types, assets, parameters, dependencies, risks, and required evidence have been identified.
Current use: preserve four BUC scenario families and expose missing inputs.
Cannot yet answer: option ranking, cost, savings, affordability, or recommendation.
410 source artifacts
Source and evidence controls
Answers: artifact families, current versions, source locators, load/migration history, normalization rules, assertions, reconciliations, gaps, and follow-ups.
Cannot prove: that registration equals interpretation, approval, completeness, or current authority.
Entities · periods · units · relationships
Conformance layer
Answers: whether records refer to the same entity, fiscal/academic period, unit, asset, parcel, project, instrument, source family, and lifecycle stage.
Purpose: make compatible joins explicit and prevent text matching from silently creating business relationships.
How domains connect
The decision is the hub; tables are supporting evidence.
A building proposal, for example, should connect authority, physical assets, current operations, project scope, sources and uses, debt, taxes, service outcomes, and follow-through without counting the same amount twice.
| Decision question | Primary domains | Required bridge | Current state |
|---|---|---|---|
| What did Town Meeting authorize? | ATM articles, motions, votes, budget versions | Article → motion → vote → budget line/funding action | Strong for 2026 ATM |
| How does the voted budget reach current accounts? | ATM budget + Town accounting | Approved budget-line-to-account mapping | 0 approved mapping rows |
| What does one facility alternative cost? | Assets, capital assessment, Town accounts, projects, debt, grants | Stable option → complete scope → annual sources/uses → obligations | Not complete |
| How does a grant reduce Town cost? | Grant lifecycle + project + accounting | Award → business subject → receipt → eligible use → expenditure → closeout | 0 award-to-subject mapping rows |
| What is Wilbraham's school burden? | HWRSD budget, member allocation, debt, Town budget | Same-period District total → official allocation → Town line | Partial / dated |
| How much did state aid reduce the local requirement? | Cherry Sheet, Town/HWRSD budgets, member assessment, actual payments | Final estimate → current budget bridge → distributions/deductions → ledger and year-end actual | Estimate history strong; actual bridge open |
| What will a home pay? | Levy, parcel, assessment, rate, exemptions | Scenario levy → certified tax base/classification → parcel distribution | Future scenario not loaded |
Why explicit mappings matter
Names that look similar do not establish a business relationship. An ATM line and a ledger account, or a grant award and a project, may differ by scope, time, amount, or purpose. The system deliberately keeps those mappings empty until a controlled relationship can be approved.
Reusable reporting surface
Stable reporting views let an answer be reused, checked, and explained.
The hardening passes through migration 0129 introduced typed canonical fields, conformed periods and units, current-source logic, readiness controls, and stable numbered views so each report does not have to rediscover the meaning of the same record.
reporting_financial_fact_v1
reporting_school_member_burden_v1
reporting_debt_issue_v1
reporting_debt_position_v1
reporting_source_artifact_current_v1
reporting_scenario_readiness_v1
reporting_budget_lifecycle_v1
reporting_grant_lifecycle_v1
reporting_capital_project_v1
reporting_gis_parcel_current_v1
How the technical layer supports the explanation
A stable reporting_*_v1 view carries agreed meaning when one exists. Typed canonical fields and approved relationships support questions not yet covered by a stable view. Raw source text remains available for lineage and unresolved review without silently becoming arithmetic, a date, a status, or a business relationship.
Non-substitution controls
Preserve the meaning of similar-looking numbers.
These distinctions make a public explanation more dependable because each measure answers a different question.
Budget ≠ actual
Spending authority is not expenditure, cash, revenue, or a year-end balance.
Levy ≠ audit tax revenue
Town-wide amount raised is not automatically the same period, basis, or collected revenue shown in an audit.
Authorization ≠ outstanding
Original principal, issued debt, current position, future interest, and annual service are distinct.
District ≠ Wilbraham
A total District budget or debt amount is not automatically the Town's member obligation.
Study estimate ≠ current cost
A 2021 projection is not a 2026 condition, bid, appropriation, or open-work balance.
Assessment ≠ market proceeds
Tax assessment is not sale appraisal, replacement cost, legal availability, or public value.
Balance ≠ recurring capacity
Free cash or stabilization can be available once without supporting a permanent annual obligation.
Null ≠ zero
An absent relationship, cost, risk, or amount remains unknown until evidence proves otherwise.
Where Town context could unlock more
Each missing connection is a focused question someone may already know how to answer.
The point is not to label the Town's data deficient. It is to show exactly which source, mapping, current update, or business rule would deepen the analysis and what new explanation that help would make possible.
Which voted line supports which current account?
The FY2027 voted schedule and July Expense Control report are both present, but map_atm_budget_line_town_account has no approved rows. Help identifying the official bridge would let a reader follow authorization into the operating record line by line.
Which Town purpose did each award actually support?
Programs and awards are visible, while map_grant_award_business_subject has no approved rows. A project, department, or account connection would show where outside funding truly reduced Town cost.
Which working assumptions best describe recurring room?
An aligned Town/HWRSD operating forecast, asset-funding practice, reserve plan, debt and exclusion schedule, and household distribution would turn separate capacity signals into a usable multi-year view.
Which records connect estimates to actual payments and local use?
The final Cherry Sheet history is now controlled. Monthly distribution and deduction reports, Town and District ledger entries, receivables, and year-end reporting would show what was actually received, where it was recorded, and how it affected the local requirement.
Which current records should anchor the BUC and Middle School choices?
Current scopes, utilization, conditions, alternatives, annual cash flows, funding, service effects, risks, legal steps, and implementation ownership would let the existing scenario families become comparable choices.
What work since 2021 is complete, open, changed, or superseded?
A current bridge from the 2021 recommendations to completed work, open work, rescoped needs, and present conditions would turn a valuable point-in-time assessment into a current capital-planning baseline.
Which measures best explain what residents and departments receive?
Broad budget and account classifications show where money sits. Comparable operating and service measures would help connect financial changes to response, access, reliability, condition, workload, and educational results.
Newly connected query layer · August 19
What changed when the newer tax, DOR, accounting, and disclosure layers were connected?
We can now ask a longer historical question, follow an estimate through stages, separate ledger placement from service purpose, and locate debt evidence without treating every document or borrowing level as additive.
History with source quality attached
17,722 observation states and three reporting views support metric discovery, Cherry-stage history, and worksheet-quality review. The 688 source-distinct metrics remain unconformed until a governed mapping is approved.
Typed tax facts before disclosure searching
The canonical-first route uses normalized tax-base, tax-rate, levy-limit, and largest-taxpayer facts before using broader disclosure evidence for historical context.
Independent analytical axes
Purpose, expense type, fund family, facility, centralized presentation, flexibility, and evidence gaps can be explored without overwriting the Town's account codes or labels.
Evidence discovery without duplicate facts
Nine Wilbraham/HWRSD disclosures and 6,701 affordability-evidence rows support source finding and gap review. Typed facts and canonical debt tables still control calculations.
The practical gain is not “more numbers.”
It is a safer path from a Town question to the exact source, qualifier, relationship, and missing connection that governs the answer.
What the connected evidence can calculate
History, dated positions, and mechanics are ready; dependable remaining capacity is not.
The reporting layer now distinguishes the questions that can be answered from those that still require Town context, a forward baseline, or governed mappings.
| Reporting question | Readiness | Why |
|---|---|---|
| Historical tax, levy, revenue, reserve, expenditure, and debt direction | Ready with series controls | DOR 0301 preserves 17,722 present/missing observation states, basis, unit, entity, period, and source. |
| FY2025 disclosure-basis Town debt snapshot | Ready as dated evidence | Eight accepted normalized observations; duplicate totals and component reconciliation are controlled. |
| Household tax mechanics | Ready as illustration | Formula and assessment bands can be shown without predicting a future bill. |
| Complete FY2027 sources-and-uses bridge | Not complete | All sources are not reconciled to the $57,018,471 General Fund on one FY2027 budget basis. |
| FY2026-to-FY2027 departmental change-and-driver bridge | Limited | Same-grain prior-year department/account detail is incomplete. |
| Dependable recurring room | Not determinable | The governed forecast, current-service baseline, future borrowing/capital scenarios, cash timing, and household/service consequences are not yet connected. |
Follow one number instead of exporting a wall of tables.
Open the resident question → measure → calculation → source → freshness → gap path →
Continue the exploration
Start with a question, then choose the depth.
The full connected-data conversation, focused evidence views, raw schema catalog, and live-schema capture remain available when a reader wants to understand how an answer was assembled.
See the breadth behind a whole Town decision
Follow one question through budget axes, buildings, grants, debt, affordability, due diligence, glossary, and technical appendices.
Middle School and BUC view
Capacity boundaries, four scenarios, asset evidence, and missing inputs.
2026 Annual Town Meeting report
Articles, motions, votes, budget versions, controlled changes, and source evidence.
Existing source connections
Detailed domain relationships, controls, gaps, and linked extracts.
Cherry Sheet story and 28-year downloads
Resident explanation, current figures, full annual history, controlled line-item extract, and the next data questions.
See how the supplied queries fit the five journeys
Coverage decisions, runtime states, resident-facing boundaries, and downloadable control matrix.
Open the August 18 summary and exact counts
Table counts · columns · constraints · views/functions/triggers.
Inspect the captured SQL schema
PostgreSQL schema-only capture from 2026-08-20 00:26:48; it is evidence of structure, not a deployment script recommendation.
New connected-data baseline · August 20
The system now connects tax history, current parcel distribution, and source identity without collapsing their meanings.
Affordability 0303 adds six core and eight GIS reporting views while leaving all ten prior stable reporting contracts unchanged. It preserves 10 MassGIS releases, 133,655 complete source records, 6,207 bounded FY2026 parcel rows, 512 normalized DLS observations, and a zero-difference conformance bridge to DOR 0301.
Aggregate tax-base and distribution evidence
The FY2026 candidate taxable real-property base reconciles to the official DLS base within −0.0049146%. Aggregate reporting avoids unnecessary owner, address, and geometry detail.
Existing debt service by year
Accepted Town and full-District HWRSD schedules preserve fiscal year, principal, interest, total, schedule version, and allocation boundaries through FY2040/FY2041.
School organization identity
School 0400 adds 15 canonical organization identities, 304 identity observations, 43 grade observations, and 5 relationship observations. It does not add governed enrollment, finance, facility, agreement, capital, or scenario facts.
Resident-facing tax-base evidence · Town and HWRSD debt-service horizon · Updated query coverage and manuals · August 20 schema summary.