Evidence before excitement
Methodology
A record earns visibility by passing a documented public-field release contract—not by receiving an attractive score.
The public pipeline
- Acquire. Retrieve a permitted official or clearly attributed public source.
- Preserve. Record source URL, retrieval time, cycle, and integrity evidence.
- Normalize. Convert only approved public fields into a stable schema.
- Check. Detect missing fields, conflicts, stale evidence, disallowed text, and duplicate records.
- Project. Publish a privacy-limited view with source, freshness, stage, and known gaps.
- Expire. Remove or mark records when freshness or evidence requirements fail.
Research stages
Source locatedA relevant source exists; record-level confirmation may still be missing.
Source recordA rights-cleared public-source row appears in the approved projection; this label is not a diligence or readiness claim.
Record matchedA fictional demonstration state used only by the synthetic interface fixture.
Needs verificationA conflict, missing field, or stale source prevents stronger use.
No opportunity score
The customer surface does not publish an investment score, expected return, bid recommendation, or claim of readiness. Research completeness describes evidence workflow—not property quality or economic merit.
Production-data gate
The current beta intentionally fails closed to a synthetic fixture. Real records may replace it only after data rights, field-level privacy, source attribution, freshness, and release-review gates are documented and passed.