# School department journal detail, FY2023-FY2026 -- the Town's second answer to the 4 September request Covers `account-details-fy2023-fy2026-p13-school-journal.pdf`, which is **held private and never published** (below), and our redacted reading of it in `sources/data/`. ## What the document says about itself Quoted from the printed copy (every page carries the same header and footer): - **Program ID** `glytdbud`, `YEAR-TO-DATE BUDGET REPORT`, **`FOR 2026 13`** and **`JOURNAL DETAIL 2023 0 TO 2026 13`** -- the same year-to-date report as the period-13 spreadsheets beside it in `expenses/`, run with journal detail switched on, from FY2023 period 0 to FY2026 period 13 - **Report generated** `10/07/2026 21:47` -- the day after the period-13 spreadsheets (`../expenses/PROVENANCE-fy2023-fy2026-p13-school.md`, run `10/06/2026`) - **Generated by** the Town Manager, whose name the last page prints - **1,744 pages.** Page 1,743 is the `GRAND TOTAL` line; page 1,744 is `REPORT OPTIONS`, which records `Print journal detail: Y`, `From Yr/Per: 2023/ 0 To Yr/Per: 2026/13`, `Include budget entries: Y`, `Incl encumb/liq entries: Y`, `Multiyear view: D` - **Scope, read off the page headers:** fund `0100 GENERAL FUND`, school accounts only (every account string is `0100-3-...`), pages 1-679; then every school special fund -- revolving funds 1300-1315, school lunch 2200, the grant funds 2481-2962 and 4201-4604, the school capital articles 3000-3123, scholarships 8130 and 8134, and 9002 custodian special details -- pages 680-1742. 3,356 accounts. - **What a journal line carries:** journal number (year/period/sequence), effective date, source code, amount, vendor number and name, invoice or purchase-order reference, a description, and on paid invoices a check number. Payroll (`PRJ`) posts as one line per warrant per account (`WARRANT=6P23 RUN=1`), not per employee. It is a printout from the accounting system (CLAUDE.md 13a): account codes, periods, journal and warrant references, and a GRAND TOTAL the report foots itself. ## How it reached us **The Town's answer to this project's records request of 4 September 2026** to the Town Manager (`notes/reference/records-requests.csv`, id `2026-09-04-town-accountant-package`) -- the "Part 2" that row was waiting for: *"held while citizen names that appear as vendors in the special education fund are removed."* On 9 October 2026 the Town Manager sent two sample extracts of this same run (pages 1-29 and 1740-1744, the same `Report generated` stamp) asking whether it was the right type of data; TJ said yes and asked for the full report, in Excel if MUNIS could export it (`build/inbox/2026-10-09-town-manager-journal-samples/PROVENANCE.md`). The full report arrived by email from the Town Manager to TJ, with two other recipients copied, on **18 October 2026 at 9:37 PM**, as a single attachment: | delivered as | sha256 | bytes | |---|---|---| | `Report 1 with Redactions Final.pdf` | `6d5d56ee70578b54de2066a2a75969dc62069caeba20cd92902fdfe2cf50da7a` | 7,736,334 | Her email said three things worth keeping, paraphrased here: - the redactions are **mostly student-related**; - a **redaction log** will follow; - the **Excel export is still failing** -- it generates only one row -- and she may need to contact Tyler Technologies, the MUNIS vendor. **No spreadsheet came with it.** There is no URL: the report was not published, it was asked for. The request is the address. ## The Town's redactions, and what we checked about them Checked 18 October 2026: - **163 redaction overlays on 28 pages**, drawn where the text has been REMOVED from the text layer, and **3 pages (34, 643, 1080) flattened to pictures** with the redactions burned in. Every one of the 1,744 pages was tested for text sitting under a black box and none holds any (a box drawn over live text, as a control, was caught). These are real redactions, not boxes over live text. - **The redaction is incomplete on the rendered page.** Page 643 prints what reads as a child's first name and last initial in a tuition line, and part of one in the next; pages 34 and 35 print a two-letter code in a column boxed on every other line; page 1080 leaves an address fragment beside a boxed payee. The values are written down nowhere in this repository. - Vendor lines that name individuals -- game officials, reimbursements -- were not redacted by the Town and were not meant to be; its stated scope was children and citizens named in the special education fund. ## What is published, and what is not - **The PDF is held private and never published** (`sources/data/redactions.csv`). It is the Town's file and its redaction misses a child. - **What is published is our redacted reading of it:** `sources/data/munis-school-journal.csv` (every journal line) and `munis-school-journal-accounts.csv` (every account), built by `scripts/extract_munis_school_journal.py`, which states the redaction rule in its header. TJ's rule, 19 October 2026: *"remove ANYBODY who is directly named as a parent or child getting services from the school. anybody contributing to those services as vendors should be ID'd... It's associating a name to a disability that we are trying to avoid."* - Recipients are masked. Children become `[redacted]`. A family's payment becomes `individual (redacted)`, with no vendor, invoice, check or receipt number. - Providers and vendors are named: special education providers, officials, contractors, staff acting in role, scholarship recipients. - Four independent privacy reads were run on 19 October 2026. The last found nothing confidential visible. - A first redacted version failed its privacy read and was never published; it is held in `build/private/`. - **The three picture pages** were read by eye into `sources/data/munis-school-journal-image-pages.csv`, already masked. The extractor proves that reading: the three accounts those pages fall in close to the cent only with it. - **Still to come from the Town:** the redaction log, and the same report as a spreadsheet.