How records were obtained
The retained collection contains files received from or attributed to the Association, its Board, Associated Asset Management, and counsel; materials located in Association-facing resource areas; government and judicial source copies; email; owner-sent correspondence; delivery evidence; and screenshots or images. Source descriptions identify the located or received context without making an authenticity finding.
“Association-produced” means the file was supplied in a production or transmission attributed to the Association or its manager. It does not mean the project independently verified that the production was complete, that every component was created contemporaneously, or that the producing party adopted every statement.
Source copy versus historical native original
For preservation, an “original” is the byte-for-byte file received, downloaded, transmitted, or located in the retained collection. A newly assembled PDF of older materials is preserved exactly as received but described as a produced compilation, not as the historical native originals of its components. Working drafts, temporary processing files, and routine duplicates are excluded from the source collection unless they independently help explain a record's origin or history.
When a file's origin or receipt history cannot be established confidently, that uncertainty is recorded in the source inventory.
Source IDs and cryptographic hashes
Every retained file receives a neutral source ID. SHA-256 and SHA-512 hashes are calculated before and after the preservation copy is made; the values must match. The preserved collection, source inventory, and checksum records are also checked together. Public-document IDs connect downloads to their catalog entries.
Member-access records are not automatically governmental public records
Association records may be subject to member-access rights under governing documents or Arizona law. That does not automatically make them governmental “public records,” erase privacy or privilege concerns, or authorize unrestricted Internet publication. This project therefore uses “public” to mean published on this site, not “legally public in every context.”
For the current statutory text on Association records, consult A.R.S. § 33-1805 on the Arizona Legislature website.
Redactions, OCR, and public derivatives
The preserved source is never edited. Redaction, optical character recognition (OCR), transcription, searchable text, excerpts, or format conversion creates a separate copy. Before publication, that copy must be visually reviewed and inspected for searchable text, metadata, annotations, form fields, comments, JavaScript, attachments, embedded files, filenames, and reversible overlays.
OCR is search material, not controlling text. Private OCR is not included on the website. Public search uses privacy-reviewed OCR or deliberately curated title, summary and catalog terms associated with an approved document. It is not a complete full-text index of every file. If OCR differs from the page image, the image controls; an unsuccessful search does not establish that a subject is absent from the record.
Governing documents, the insurance certificate, and Association-level financial reports remain byte-for-byte unchanged. Their public SHA-256 equals their retained-source SHA-256. Adding reviewed catalog search terms does not change the PDF. Original professional contacts, signatures, insurance references, accounting codes, and recording marks are retained in those source copies.
Email renderings and edited letters
Published email PDFs are new text renderings, not original email files. Personal identifiers and protected details are removed before the PDF is generated. Only reviewed header fields and message text are included; full routing headers, original email HTML, remote images and embedded attachments are not included. Where only a parsed email export was available, the catalog says so rather than claiming a complete raw email.
Quoted chains and attachments may be omitted or represented by a separately cataloged record. A message does not establish that its attachments were delivered, received or complete. Review the individual transformation notes and related records for the scope of each download. Preserved raw messages and their original headers remain private.
Image-based letter copies use irreversible redactions, with searchable OCR rebuilt from the redacted pages. Other letters and proposed attachments are separately labeled text renderings with normalized formatting. Selected director-message transcripts are compared with retained screenshots; overlaps, omitted material and uncertain dates are disclosed. They are not complete platform exports. Owner-proposed forms and resolutions are identified as proposals, not adopted Association policies.
Some copies include an editorial cover explaining omissions, contrary positions or later context. The retained source is unchanged. Historical accusations and legal arguments remain the writer's positions, not findings adopted by this project. A dated retained letter is not proof of transmission; where delivery has not been verified, its catalog entry says so.
How monthly enforcement statistics are calculated
The report portion of the redacted packet is read using OCR to identify each notice row's generalized category, notice level, report date, and whether that row visibly shows a completion date. The row count is checked against the report's printed total of 108. The website uses the reviewed aggregate results of that analysis.
Rows are grouped by the date printed in the report. May covers May 29–31 and July covers July 1–28; both are partial. June is a full calendar month inside the report range. Courtesy/first notices are shown separately from second-through-fifth-level rows, whose produced notices are labeled as fine notifications. This is a count of notice rows, not household-attributable balances or proof that a charge became due. Charts, tables, and downloadable data show exact aggregate counts, including zero, one, and two. Only generalized categories are included; individual notice rows and household identifiers are not part of the downloadable data.
The count describes what the production reflects. It is not a finding that the stated condition occurred, that notice was legally sufficient, or that enforcement was consistent.
Absence, completeness, and uncertainty
“Records produced to date do not show…” describes a limit of the available evidence. It does not establish that an event never happened. A missing item may be nonexistent, outside the requested range, retained elsewhere, omitted, withheld, lost, or simply not yet approved for publication. The public library’s zero count means no approved download in that category—not that no private record exists.
Corrections and updated versions
A challenged statement is reviewed against the cited source and any new evidence. Substantive corrections are dated and explained. A changed or newly received source gets a new source ID; no source item is overwritten. Superseded public derivatives are removed from current navigation with the change documented, while their history remains recorded privately.