Three surfaces over one set of engines. The board sees everything, an owner sees their own unit, and neither of those is decided by what a page chooses to display.
Code computes every number. A model's only job here is upstream, turning a PDF into text. No figure and no quoted passage on any of these pages was produced by a model: the arithmetic in the browser is a second implementation of the Python engines, and a harness proves the two agree before anything ships.
The two implementations agreeing is not the same as both being right, so a mutation battery breaks each of them on purpose and requires the harness to notice. That is what makes a green run worth anything.
Not here. This page and everything linked from it is a demonstration over a sample association that does not exist, and the figures in it are invented.
Records that belong to a real association sit behind a login on the application, where the rules about who may read what can actually be enforced by code the reader cannot edit. Cross-association requests, an owner's own-unit scope, withheld records, rate limiting and the audit trail are all decisions a server has to make. A static page cannot make them, so it is not asked to.