Identity and traceability
Artifact code, title, issuing entity, dates, family/version, source type, acquisition, and lineage can be preserved.
Supporting layer · source and evidence control
A source link is only the beginning. A responsible report also identifies the exact version and locator, the measure's scope and period, what transformation occurred, its evidence state, whether it is current for the question, and what remains unresolved.
Short answer: 410 source artifacts were registered at the August 16 database checkpoint. That historical register remains unchanged. Later accepted query layers and the August 20 catalog are documented separately below so a newer source, structure, or adoption checkpoint does not silently rewrite an earlier source-register total.
What “incorporated” means
A source can be in the database while its meaning, relevant version, relationship, or completeness is still under review.
Artifact code, title, issuing entity, dates, family/version, source type, acquisition, and lineage can be preserved.
The relevant table, footnote, member allocation, legal condition, later amendment, or missing page may still change the meaning.
The source must be current enough, scoped correctly, reconciled to related facts, and sufficient for the specific conclusion being considered.
Added after the August 16 catalog
This source family adds 56 official DLS final budget-estimate PDFs: one municipal and one regional-school report for each of 28 fiscal years.
Each source is connected to its entity, fiscal year, report type, family, version, and locator.
Labels, amounts, signs, zeros, blanks, detail rows, subtotals, and totals remain distinguishable.
Printed control rows support reconciliation without becoming additional revenue or charges.
Historical presentation gaps and unusual source signs are disclosed; none remained open or error-severity.
These are official final budget estimates. They are not actual receipts, expenditures, or cash-payment evidence. Monthly distributions and deductions, local accounting, Schedule A, audits, and District funding records are needed for those later questions.
The current Wilbraham and HWRSD figures come first; full history and boundaries follow only when useful.
Receipts, charges, net effect, source file, report type, and qualification.
Source locators, original and conformed labels, values, flow, availability, assurance, verification, and notes.
Accepted layers through August 20
The latest layers make historical tax, DOR, accounting, debt, disclosure, parcel distribution, and organization-identity evidence easier to locate. The report still uses typed and canonical facts first and preserves candidates, missingness, duplicates, and source qualifications.
17,722 observation states, 8,603 Cherry-stage states, and source-quality controls. Similar source labels are not automatically one comparable series.
The attached command expects tax-base, tax-rate, levy-limit, and FY2025 largest-taxpayer populations. Publish exact returned values only after the command is run and its transcript/output is returned.
6,701 source-linked affordability rows across nine Wilbraham/HWRSD disclosures. Candidate evidence is not automatically decision-ready.
CSKE purpose, expense, fund, facility, presentation, flexibility, and gap lenses remain distinct from the Town's source-authoritative labels.
Official DLS history, a bounded FY2026 parcel projection, a controlled reconciliation, and standardized levy sensitivity are adopted with source and calculation boundaries.
Organization names, codes, grades, and source-stated relationships improve entity resolution. They do not establish governed enrollment, finance, facility, agreement, capital, or scenario facts.
Typed canonical fact → accepted normalized observation → candidate evidence for discovery → original source and locator. If the layers conflict or remain incomplete, show that instead of selecting the most convenient number.
Affordability evidence · source and freshness strip
“Latest loaded” does not mean every observation is current for an August 2026 decision.
| Layer | Evidence date/coverage | Status | Permitted reporting use |
|---|---|---|---|
| DOR 0301 | Run 2026-08-19 02:04:24; topic coverage varies through FY2027 | Overall PASS | Historical series discovery and controlled observation reporting; not a current affordability forecast. |
| Tax 0200 | Command supplied 2026-08-18 | No returned transcript/output | Query contract and expected population only; do not publish exact returned values. |
| Disclosure 0201 | Nine Town/HWRSD documents; candidate evidence output 2026-08-18 | Discovery layer | Locate pages, lines, metrics, and mapping gaps; candidate rows do not become headline facts automatically. |
| FY2025 Town debt observations | Period end 2025-06-30 | Eight accepted normalized observations | Dated issuer-prepared unaudited disclosure-basis snapshot; not “current debt” in August 2026. |
| Affordability 0303 | Accepted 2026-08-19; FY2026 parcel projection and DLS history through FY2027 missing states | Accepted · overall PASS | Tax-base reconciliation, class composition, and standardized levy sensitivity. Not a tax bill, legal-capacity result, debt fact, or recommendation. |
| School Organization Identity 0400 | Accepted 2026-08-19 | Identity foundation | Source and entity resolution only; no governed enrollment, finance, facility, agreement, capital, or scenario use. |
| August 20 schema and backup checkpoint | Captured 2026-08-20 00:26:48 | Verified package checkpoint | Structure and custody reference. The public portal does not contain or expose the full database backup. |
| Affordability Evidence v2 | Assessment as of 2026-08-20 | Partial readiness | Legal/historical context, existing Town/HWRSD payment schedules, dated debt position, household mechanics, standardized tax-base distribution, and gap reporting; dependable remaining recurring capacity is not determinable. |
Evidence-state contract
These states are not a simple quality ranking. A source-reported figure can be authoritative for one purpose and still be incomparable to another scope.
| State | Meaning | What must be visible |
|---|---|---|
| Source reported | Reproduced from an identified source without changing the source's meaning. | Artifact/version, locator, source label, unit, period, and scope. |
| Normalized | Conformed to a controlled type or label while preserving source meaning. | Original value, rule, typed result, and any exception. |
| Reconciled | Matched across compatible records through an explicit bridge or control. | Compared totals/keys, difference, method, and control result. |
| Calculated | Derived from identified inputs. | Formula, numerator, denominator, rounding, and input evidence states. |
| Allocated | A total distributed by an identified rule. | Source total, allocation basis, period, share, and rounding. |
| Estimated | A method-based value with uncertainty. | Method, assumptions, period, range/sensitivity where material, and owner. |
| Assumed | A selected scenario input—not an observed fact or forecast. | Scenario, rationale, range, source context, and refresh trigger. |
| Conflicted | Sources or scopes disagree and no valid bridge has resolved the difference. | Both values, scopes, source dates, consequence, and resolution owner. |
| Missing | Required compatible evidence is absent. | The missing field, why it matters, owner, next source, and due date. Never substitute zero. |
Minimum measure identity
If these fields cannot be stated, the figure is not ready for a headline comparison.
Stable code, human label, value, currency/count/percent/rate, precision, and whether it is a total, balance, flow, or share.
Town, District, Wilbraham member, fund, department, asset, parcel, account, or household denominator.
Fiscal/calendar/academic period; proposed, budgeted, authorized, issued, actual, outstanding, projected, completed, or closed.
Artifact/version, locator, effective/as-of date, evidence state, formula/allocation, reconciliation, freshness, and unresolved issue.
Version and freshness
A source family can identify the current loaded version while a report still needs a newer official event, condition check, forecast, or tax certification.
Track preliminary, recommended, motion, voted, amended, restated, and superseded versions without overwriting history.
A 2021 condition assessment remains valid evidence of what was reported then; it does not establish 2026 condition or price.
A dated baseline may frame a question while a live recommendation requires current scope, cost, schedule, legal status, and operating effect.
The FY2027 final-voted budget is controlled through May 11, 2026; the FY2027 Expense Control extract is dated July 9, 2026; the latest included schema catalog was captured August 18 at 23:48:57; the Cherry Sheet final-estimate layer was accepted August 17; DOR 0301 was accepted August 18 and its supplied query transcript was produced August 19; and the principal facility condition study is dated August 23, 2021. These are not one common “as of” date.
Registers and catalogs
The full source register lets a reader follow the evidence trail; the connected-data route shows what those domains and relationships can help Wilbraham understand; the raw catalog exposes schema structure and exact counts.
See how an original artifact becomes a source record and then a structured fact, or search the complete inventory by subject, year, family, filename, or source code.
See how budgets, accounting, schools, debt, assets, parcels, grants, audits, and Town context can deepen one decision explanation.
Coverage status, runtime evidence, story placement, publication boundaries, and machine-readable control.
Exact table counts · migrations and loads · captured schema SQL.
The supporting register and database catalog describe incorporated evidence and captured structure. They do not replace official documents or prove that every relevant source is present, current, correctly interpreted, or sufficient for a live decision. Copyright © 2026 Sherie Schaefer. All rights reserved.