Ingestion & reconciliation
How the complete evidence record was processed — precisely.
This is an honest, stage-by-stage account. It distinguishes files received from files opened, hashed, deduplicated, classified, content-reviewed, dossiered, published, restricted, and still pending. It does not claim the corpus is fully published.
Scope of the counts
The 397 count is the number of manifest ROWS across the two evidence-package manifests plus the standalone Crest manifest. Because the 80 public Crest documents are listed in more than one manifest, 397 counts those cross-listings. It EXCLUDES the 227 entries in the separately supplied CONFIDENTIAL ZIP, which were quarantined and NOT opened.
Files received (manifest rows)
Across Part 1, Part 2, and the standalone Crest manifest; includes cross-listed rows.
Confidential-ZIP entries (separate)
Quarantined. NOT opened, inspected, hashed by us, reconciled, or checked for broken attachments.
Entries enumerated (names/sizes listed)
Manifest rows read; ZIP directory entries listed.
Binary files individually opened & content-reviewed by this site
The curated substantive records. The 75 public Crest docs are published from source with verified hashes but not yet visually content-reviewed.
Files with a SHA-256 fingerprint
Supplied per-file in the manifests. Independently re-hashed by us: the 2 ZIP containers (matched) and the Assessment PDF.
Deduplicated → unique canonical records
92 exact-duplicate hash groups; 212 duplicate occurrences.
Classified by evidence type
Each manifest row carries an evidence class adopted here.
Individual dossiers created
98 full dossiers (95 public/analysis + 3 restricted) + 196 sanitized metadata-only dossiers.
Published public dossiers
Includes 75 individual public Crest documents + 20 curated records.
Metadata-only dossiers (contents withheld)
3 restricted collections + 196 per-file metadata pages (existence + safe metadata disclosed).
Canonical records (two evidence packages) still without a page
Every deduplicated record in Part 1 & Part 2 now has at least a metadata-only dossier. The 227 confidential-ZIP entries remain undossiered by design.
Reconciles: Part 1 + Part 2 unique canonical = 98 full + 196 metadata-only = 294 dossiers, 0 remaining. The 227 confidential-ZIP entries are excluded and remain quarantined.
Version families
Grouped 81 · manually compared 0. Grouped automatically by filename stem + differing hash. None individually compared yet → treat as ‘possible version family — review pending.’
OCR
Flagged 25 · verified 0. Nothing OCR-flagged is quoted until visually verified.
Restricted
Do-not-publish 67 · review-and-redact 16.
Revision labels (reconciled)
Operational status — must clear before production
Corrections mailbox (corrections@therealwoodtracehoa.com)
Awaiting operational confirmationNot yet tested for receipt, reply path, spam handling, monitor identity, or retention. No external test will be run without the mailbox owner's authorization.
Master evidence archive durability
Not yet on durable storageOriginals currently sit in the app intake folder (excluded from the public web server). This is not confirmed persistent, backed-up, access-controlled, or disaster-recoverable. A durable, access-controlled archive is required before relying on it as the only copy.
Confidential ZIP (227 entries)
Quarantined — NOT opened or inspectedNot reconciled, not verified, and not confirmed free of broken attachments. Statements inside it are not used.
Our own corrections
Accountability includes accountability for our own work.
Current management certificate identified
PreviousThe site referenced only the September 7, 2021 Community Solutions management certificate.
CorrectedThe current recorded certificate is October 27, 2025 (Montgomery County #2025110172, Crest / Carolyn Bonds); the 2021 copy is now labeled legacy/superseded.
Reason: The recorded 2025 certificate was located in the evidence corpus. · Discovered August 27, 2026 · Corrected August 27, 2026 · Changed: Website language only (no PDF change).
Supporting record / affected page →Withdrew ‘Crest public tables were empty’ implication
PreviousEarlier framing implied Crest's public document tables were empty.
CorrectedCrest's tables are JavaScript-loaded from public APIs and were available on the capture date.
Reason: A non-JavaScript capture can appear empty though records were present. · Discovered August 27, 2026 · Corrected August 27, 2026 · Changed: Website language only.
Supporting record / affected page →Added the $150 MDZ Construction agenda item
PreviousMDZ Construction was not documented by a primary record on the site.
CorrectedAdded the August 25, 2026 agenda item; documents the job/amount only, not ownership, bidding, or wrongdoing.
Reason: Primary agenda located in the public Crest capture. · Discovered August 27, 2026 · Corrected August 27, 2026 · Changed: New record + finding link.
Supporting record / affected page →Documented the capitalization-fee difference
PreviousNo fee comparison was published.
CorrectedPresented $300 (certificate) vs $600 (2026 public API) as a record-to-record difference, not wrongdoing.
Reason: Two Crest-published records state different amounts. · Discovered August 27, 2026 · Corrected August 27, 2026 · Changed: New analysis record.
Supporting record / affected page →Distinguished gate capability from proof
PreviousGate surveillance was referenced without the primary capability source.
CorrectedAdded the Front Gate FAQ as a capability description; capability is not proof of current biometric use or unlawful surveillance.
Reason: Primary FAQ located in the public capture. · Discovered August 27, 2026 · Corrected August 27, 2026 · Changed: New record.
Supporting record / affected page →Preserved the Rachel Schmutz written/verbal distinction
PreviousProvenance of the 2025 GL and the attributed phone statement were not separated on the site.
CorrectedRecorded her as transmitting custodian of the 2025 GL while keeping the attributed telephone statement separate and attributed, not asserted.
Reason: Evidentiary-distinction requirement. · Discovered August 27, 2026 · Corrected August 27, 2026 · Changed: New restricted metadata record + finding note.
Supporting record / affected page →MDZ Construction — Montgomery County registrant identified (▒▒▒▒▒▒)
PreviousEarlier framing said no Montgomery County MDZ Construction filing was located and that MDZ ownership was entirely unresolved.
CorrectedMontgomery County assumed-name certificate DBA #202200841 (filed March 16, 2022) identifies ▒▒▒▒▒▒ as the individual registrant of MDZ Construction. It does not list ▒▒▒▒▒▒ and does not, by itself, establish joint ownership or unlawful conduct.
Reason: A primary government record (hash-verified) was supplied and located. · Discovered August 27, 2026 · Corrected August 27, 2026 · Changed: New primary-record dossier + finding, party, and timeline updates; address-redacted public derivative.
Supporting record / affected page →Reclassified the Montgomery County “No Results” search
PreviousAn initial Montgomery County quick search returned no results, supporting an inference that no DBA existed.
CorrectedThat quick search was incorrectly scoped (department=RP, full-text/OCR disabled). It is reclassified as an incomplete initial search superseded by the located DBA #202200841. The original capture is retained for transparency, not deleted.
Reason: A correctly-scoped assumed-name search located the certificate. · Discovered August 27, 2026 · Corrected August 27, 2026 · Changed: Reclassified capture; correction published; original preserved.
Supporting record / affected page →Kept the Harris County MDZ Construction record separate
PreviousThe Harris County MDZ Construction (▒▒▒▒▒▒) was treated as the only located MDZ registration.
CorrectedThe Harris County certificate P122958 (2019, ▒▒▒▒▒▒, Pasadena) is preserved as a separate filing — different county, registrant, date, and location — not contradictory to the Montgomery County certificate.
Reason: Two distinct county filings use the same assumed name. · Discovered August 27, 2026 · Corrected August 27, 2026 · Changed: New dossier (source PDF pending); party added (▒▒▒▒▒▒).
Supporting record / affected page →Ingested the Oct 2025–Jul 2026 financial-statement series
PreviousThe site referenced the 2025 GL but not the monthly balance sheets / income statements.
CorrectedAdded 18 hash-verified primary financial statements (10 balance sheets, 8 income statements) as individual dossiers with reported/classified language and the October YTD-deficit reconciliation ($332,099.58). October 2025 income statement and June 2026 income statement are outstanding.
Reason: Supplied financial-statement release verified against its manifest. · Discovered August 27, 2026 · Corrected August 27, 2026 · Changed: 19 financial dossiers (18 verified + 1 pending), financial timeline, collection.
Supporting record / affected page →Licensing question classified as unresolved (not proof of unlicensed work)
PreviousNo licensing analysis existed.
CorrectedAdded TDLR negative-search dossiers and a contractor-licensing & pool-regulation finding. A negative TDLR search is expressly NOT treated as proof of unlicensed or illegal work; the compliance question is unresolved pending work scopes, performer identities, subcontractor records, and a plumbing-board search.
Reason: TDLR captures supplied; Texas pool/electrical framework applied with official sources. · Discovered August 27, 2026 · Corrected August 27, 2026 · Changed: 2 TDLR dossiers + new finding + licensing table + records-request items.
Supporting record / affected page →Financial Governance Pack ingested; October income verified; meeting chronology added
PreviousThe October 2025 income statement was owner-reported/pending; there was no reserve-study record and no 2025–2026 board-meeting chronology; the 2025 GL and Aug 25 agenda had no served source file.
CorrectedVerified the Financial Governance Pack (archive + all 35 files hash-matched). Flipped the October 2025 income statement to hash-verified with a served PDF; added the 2023 Reserve Study baseline (4.7% funded) and 11 board/annual-meeting dossiers with a chronology and records-review flags; attached the 2025 GL and Aug 25 agenda PDFs. June 2026 income statement and the full post–July 7 2025 GL remain outstanding.
Reason: Controlled evidence update supplied and verified. · Discovered August 27, 2026 · Corrected August 27, 2026 · Changed: 1 record verified + 12 new dossiers + meeting timeline + evidence-request updates.
Supporting record / affected page →Source hierarchy for conflicts
When records conflict, we show every competing record and rank weight by this order — never silently choosing one and hiding another.
- 1Executed and officially recorded instruments
- 2Original government, Association, management, vendor, and financial records
- 3Contemporaneous emails, notices, recordings, and meeting records
- 4Website captures and screenshots
- 5Attributed homeowner observations and statements
- 6Analytical summaries, AI-generated material, and inferences