The FY2027 General Fund remains the starting point. Affordability 0303 explains how a separately stated levy scenario could be distributed; it is not another budget total or the missing FY2027 source bridge.
Supporting layer · evidence assembled through August 20, 2026
Which supplied queries were missing from the full report?
Some were already carrying part of the story. Others were in the database but had not yet been connected to the reader question they could help answer.
Short answer: the prior query layers remain intact. Affordability 0303 and the August 20 schema checkpoint now support report-ready tax-base reconciliation and standardized distribution evidence. School Organization Identity 0400 improves source and entity context only; it does not yet support enrollment, finance, facility, agreement, capital, or scenario conclusions. Everything remains behind the five existing journeys.
Coverage review
Each query now has a clear report role.
“Added” means the query is named, placed, and bounded in the report. It does not mean every returned row is ready for a public headline.
| Query or evidence family | Prior report state | What Portal v3.7.0 adds | Runtime / evidence state |
|---|---|---|---|
| Cherry Sheet final estimates · 0300 | Resident story, FY2000–FY2027 history, connected-data and source treatment | Retained without rewriting; connected to the DOR legislative-stage bridge and query map | Accepted canonical final-estimate layer; estimates are not actual cash |
| DOR consolidated year series · 0301 | No named 0301 layer | Historical observation, Cherry-stage, and source-quality access added | Accepted output supplied; 22 read-only result sets ended in OVERALL PASS |
| FY2025 tax normalization · 0200 | Current DLS concepts and later FY2026 levy controls, but no 0200 query map | Normalized tax base, tax rates, levy-limit walk, and largest-taxpayer drill-down identified | Migration appears in the captured catalog; command supplied; no returned 0200 transcript/output was supplied, so exact returned values are not published |
| Disclosure affordability and debt · 0201 | Older debt explanations and technical extracts | Canonical-first query hierarchy, nine-disclosure discovery layer, and debt double-count controls added | Migration appears in the captured catalog; guidance supplied; candidate evidence is not automatically a canonical fact |
| Town accounting classification · 0014 | Classified technical extracts and catalog objects | Query guide surfaced as the bridge from ledger location to purpose, expense type, facility, flexibility, and evidence gaps | Migration and eight classified views appear in the captured catalog; CSKE labels are analytical, not Town classifications |
| Affordability parcel, tax base, rate, and levy · 0303 | Available after immutable Portal v3.5.0; not adopted | FY2026 candidate-base reconciliation, aggregate class composition, standardized levy sensitivity, source controls, and report-builder queries | Accepted v0.2.1 transcript ended OVERALL PASS after shadow, live, replay, and post-replay checks; six core and eight GIS views added; prior stable contracts unchanged |
| School Organization Identity · 0400 | Available after immutable Portal v3.5.0; not adopted | Entity/source identity boundary added to connected-data and query guidance | Accepted identity foundation; no stable reporting view and no governed enrollment, finance, facility, agreement, capital, or scenario facts |
| Full backup and schema catalog | August 18 checkpoint | August 20 00:26:48 checkpoint added and used for query-to-object checks | Exact captured structure and verified PostgreSQL custom-format backup checkpoint; the portal does not publish the backup or claim a local restore |
The user stories remain in control
The same evidence answers a different question in each journey.
Journey 2
What choices may be ahead?
Once an option is costed, its annual levy or annual debt-service amount can be tested across assessed values. Incomplete choices remain unranked.
Tax history, parcel distribution, source provenance, and school organization identity now connect without collapsing the boundaries among official facts, calculated sensitivity, and identity-only evidence.
A levy-affecting request can carry its amount, recurring treatment, fiscal-year timing, distribution sensitivity, service effects, alternatives, and uncertainty through every handoff.
Journey 5
How should FinCom use the evidence?
Use the accepted denominator for transparent sensitivity, then test recurring balance, debt timing, cash, capital, household burden, services, and alternatives. Sensitivity is not advice.
Reporting now built · Portal v3.7.0
The queries now support an Affordability Evidence v2 walk-down.
The result stays behind the five journeys and answers what the new evidence can measure without overstating what remains unknown.
Historical financial context
Tax, levy, revenue, local receipts, expenditure, reserve, debt, parcel, state-aid, and selected school series with missingness controls.
FY2025 Town debt snapshot
Eight accepted normalized observations, duplicate-total control, and a visible $55,000 component reconciliation gap.
Tax-base distribution
The reconciled FY2026 candidate base supports neutral illustrations per $1 million of stated annual levy without predicting an actual bill.
Dependable remaining capacity
The complete FY2027 funding bridge, current-service forecast, forward portfolio, cash timing, and household/service effects are still missing.
What financial room can Wilbraham see—and what can't the current evidence determine? →
New historical layer · DOR 0301
What can the newer DOR query help us ask?
It broadens the historical evidence available for taxation, revenue, spending, reserves, debt, parcels, state distributions, community context, and selected school measures. The source-qualified series must still be selected one at a time.
Missing states remain distinct from 5,205 explicit literal zeros.
Similar labels are not combined until entity, basis, unit, scale, and meaning are governed.
The query can show how an estimate moved without loading a second copy of the final fact.
These links prevent a final 0301 stage row from being added to the canonical Cherry Sheet 0300 detail.
DOR history does not by itself establish a current Town forecast, actual household burden, complete capital plan, sustainable operating capacity, service consequence, or recommended decision.
New access pattern · disclosures and debt
Begin with the borrowing question—not the document count.
The same borrowing can appear in an official statement, audit, continuing disclosure, debt schedule, and refinancing document. Those are sources about one obligation, not five debts.
What transaction occurred?
Keep original principal as issuance history. It is not current outstanding debt.
What remained on one date?
Use a complete, non-overlapping dated population and disclose anything without a supported position.
What is due each year?
Keep principal, interest, total debt service, entity, version, and tax treatment visible.
What replaced what?
Do not count a bond anticipation note beside the rollover or bond that took it out.
Those rows can help locate historical context and gaps. A number becomes a definitive public fact only after its metric, period, unit, basis, assurance, entity, duplicate treatment, and canonical-source status are resolved.
Latest captured structure
The query map now points to the August 20 catalog checkpoint.
This is a technical inventory captured at 2026-08-20 00:26:48. It records the accepted database state through Affordability 0303 and School Organization Identity 0400.
Open the schema summary · inspect migrations and loads · inspect exact table counts.
Before a query result becomes a report statement
Keep the controls that make the result understandable.
Name the measure.
Carry entity, period, scope, stage or basis, unit, scale, source, and relationship.
Missing is not zero.
Use a left join or a separate coverage test so incomplete issues or series do not disappear.
Do not add levels twice.
Issue and security, final Cherry stage and canonical fact, embedded audit and original audit must not be double counted.
Evidence is not automatically a fact.
Use candidates to discover and review. Use canonical or governed facts for definitive calculations.
Downloadable control
Keep the coverage decision auditable.
Query coverage matrix
One row for every supplied query family, its prior state, new report placement, runtime status, and publication boundary.
Five-journey story map
Why each query was placed where it was—and the resident-first points that must not regress.
Supplied commands and reporting guides
DOR, tax, Town-accounting, Cherry Sheet, and debt/disclosure query materials remain behind the user stories for reproducibility and future report work.
DOR 0301 supplied transcript control
SHA-256, start and finish time, population signature, 22-result-set count, and final OVERALL PASS status.
Accepted query and use manual
Report-builder examples, source controls, standardized distribution method, and required qualifications.
Identity data-use manual
Bounded organization identity queries and explicit non-inference controls.