DoorFrame Source Library

The public-data catalog behind Property Watch. It organizes Buffalo, Erie County, NYS, and federal source families, API readiness, freshness, caveats, and customer-display policy without exposing raw API output.

Open Property Watch

ModeSource catalog

Customer displayReviewed only

First adapterBuffalo permits

Raw outputHidden

Source Command

The source library proves which public/context sources are useful before DoorFrame automates anything.

Unified v4 source area

Public APIs become useful only after normalization and review

Source families are organized here as packet evidence policy: what can be checked, how fresh it is, what caveats apply, what customers may see, and what claims remain blocked.

Tier 1 families6

Buffalo/Erie source families shown with policy and caveats.

Display ruleReviewed

Customer packets need approved customer-safe source snapshots.

First adapterPermits

Buffalo permits is the first API-backed source loop.

Packet sectionsCited

No quiet packet sections without evidence or missing-data reason.

Create packetAttach sources to watched properties.Map to packagesSee which packet sections sources support.Review qualityCheck missing, stale, conflicting, and blocked evidence posture.Review in adminAttach reviewed source snapshots in the cockpit.

Source Families

These cards describe the first source/data shelf. They are policy rows plus adapter-readiness signals, not raw API output.

manual intakeClient-submitted quote/work context

Role, property address, work category, quote/scope text, vendor info if provided, timing, concern, files/links metadata, and consent.

Freshness: Checked at intake and again during founder review.
Policy: Can support submitted-info and missing-data sections after review.

Tier 1 validation sourceBuffalo permits

Manual official-source lookup candidate for permit/scope questions and source appendix context.

Freshness: Record freshness must be shown with checked date and caveat.
Policy: Questions to ask only. No permit-required or compliance conclusions.

Tier 1 validation sourceBuffalo code violations

Manual public-context lookup candidate for noticed items and data-quality gaps.

Freshness: Depends on official source freshness and manual checked date.
Policy: Context and follow-up prompts only. No safety or compliance conclusions.

Tier 1 validation sourceBuffalo 311 current and legacy

Manual public-context lookup candidate for neighborhood/service history questions.

Freshness: Current and legacy source dates must be separated.
Policy: Can support context notes and questions. Cannot prove current condition.

Tier 1 validation sourceErie County property/tax and GIS/parcel

Parcel/property context candidate for address normalization, owner/public parcel cues, and map context.

Freshness: Needs source label, checked date, and official-query method.
Policy: Can support property context notes. No appraisal, tax, insurance, or legal conclusions.

questions onlyHigh-caution business/registry sources

Rental registry, contractor registration, business records, and public-work contractor records require higher caution.

Freshness: Use only with explicit caveats and review status.
Policy: Questions to ask only. No provider recommendation, verification, ranking, approval, or quality conclusion.

Source Display Policy

The source library should keep DoorFrame useful without leaking raw records or turning context into conclusions.

Source CheckedHuman Reviewed

What DoorFrame Can Say

DoorFrame can organize submitted information, reviewed source/context checks, missing data, caveats, and questions to ask.
DoorFrame can document official source URL, access method, query fields, freshness, caveats, and customer-display policy.
DoorFrame can use reviewed source snapshots to support packet summaries, questions, missing-data flags, source appendix rows, and context notes.

What DoorFrame Cannot Conclude

DoorFrame cannot make legal, safety, compliance, appraisal, insurance, tax, fair-price, provider-quality, recommendation, ranking, dispatch, or guarantee conclusions.
DoorFrame cannot show raw public-source output directly to customers or imply a source is customer-ready before normalization, review, and blocked-claim checks.
DoorFrame cannot conclude legal compliance, safety, permit requirements, fair price, property value, insurance risk, tax posture, or contractor quality.

Normal runtimeSource-policy cards, adapter-readiness signals, and honest blocked states only.

Automation gateAdapters write to fetch logs and review queues first; raw source rows never go straight to customers.

Customer packetsEvery customer packet section must cite reviewed evidence or show an explicit missing-data reason.