Methodology
The data decides — we don't. Every input, weight, and data vintage is public; every property is graded by the identical rules; the changelog is visible.
Accountability unit: the operator
We grade the operator, with buildings as children. Reputation aggregates up the graph (building → owning LLC → operator → parent), so it survives building rebrands and aggregates across a portfolio. Google rates a building name; nobody rates the operator across its Austin properties. Every edge in that graph is published only after it is verified against primary records (Travis Central Appraisal District, Texas SOS, the operator's own site).
Conditions — city records, not testimony
We ingest four Austin open datasets nightly:
| Dataset | Socrata ID | Role |
|---|---|---|
| Austin Code Complaint Cases | 6wtj-zbtb | Primary signal |
| Repeat Offender Registrations | 86z9-i27i | Escalation flag |
| Repeat Offender Deficiencies | ge82-ij4h | Detail |
| Repeat Offender Activity | 5yf8-fm7j | Detail |
The asymmetric scoring rule
Complaint-based enforcement systematically under-reports, because tenants fear retaliation. So we score asymmetrically: a high complaint count is strong evidence of problems; a low count is weak evidence of quality. The absence of complaints is never rewarded as if it were proof of good conditions.
Fact vs. analysis
Facts are public records reproduced accurately with links (complaint counts, ROP status, court filings, permit dates). Anything derived — scores, classifications, deltas — is labeled "WCII analysis" with the computation shown. We never assert a legal conclusion; where a practice resembles a regulated category we say "pattern consistent with…" and link the rule and the FTC's reporting channel.
Scores are not published yet
No composite letter grade is computed or shown until the scoring weights are set deliberately and published here. This prototype shows raw city-record aggregates only.
Data vintage & changelog
Every page states when its data was captured. Snapshots are committed nightly to a public repository, so the full history is an audit trail.
v0.1 (July 2026) — ingestion pipeline and conditions data established; scoring weights not yet set.