Auth session missing!
Customer Data Dashboard
A private customer hub for one-time public records packets, subscription posture, watched properties, source-backed packets, reviewed reports, missing information, and the next useful action. It replaces the old marketplace-style rehearsal page with the public-data product loop.
Product Command Center
The customer entry point now starts with the paid data-product loop: one-time packet requests, entitlement, watched properties, packet readiness, and reviewed report access.
Auth session missing!
Sign in and choose a plan before adding properties.
Packets stay empty until a watched property starts the source loop.
Client report preview blocked: production locked.
Customer-safe aggregate count only. Raw records and private admin notes stay hidden.
Gaps remain visible instead of being smoothed over by AI.
Subscription And Latest Packet
At a glance: current entitlement, source bundle, latest packet state, consent receipts, and next action without raw API output.
Auth session missing!
Bundle names map to reviewed Property Watch source modules, not raw public output.
No packet shell is visible for this owner yet.
Only safe consent status is shown; raw metadata stays hidden.
Packet Pipeline
Packets should read as a source-backed data product: property selected, modules requested, source review completed, AI summary bounded, and customer display approved.
Plans And Source Bundles
The visible customer product is a Buffalo/Erie public-data subscription. No provider marketplace, dispatch, ranking, or payout behavior is created here.
Monthly Buffalo permit and 311 context for one watched property.
Buffalo permits / Buffalo 311 current + legacyMonthly public-record packets for up to five properties.
Buffalo permits / Buffalo code violations / Buffalo 311 current + legacy / Erie property/tax / Erie GIS/parcelPortfolio public-data monitoring with export-ready packet structure later.
Buffalo permits / Buffalo code violations / Buffalo 311 current + legacy / Erie property/tax / Erie GIS/parcelWorkspace Routes
The customer dashboard links to the active data-product areas and keeps compatibility intake separate from subscription packet status.
Customer States
Every customer page should use the same state language for locked, empty, review-needed, staging-only, and not-ready data.
Data Boundary
DoorFrame can make scattered public records easier to understand, but it must keep the claims source-backed and cautious.
- DoorFrame can organize submitted information, reviewed source/context checks, missing data, caveats, and questions to ask.
- DoorFrame can show subscribed Property Watch status, watched property rows, source-bundle labels, packet readiness, missing information, and reviewed report previews.
- DoorFrame can summarize normalized source snapshots and explain what was checked, what was not found, and what questions remain.
- DoorFrame cannot make legal, safety, compliance, appraisal, insurance, tax, fair-price, provider-quality, recommendation, ranking, dispatch, or guarantee conclusions.
- DoorFrame cannot show raw API output directly to customers or expose private admin notes, secrets, internal access rows, or unreviewed evidence.
- DoorFrame cannot conclude legal status, safety, compliance, appraisal, tax posture, insurance risk, fair price, provider quality, provider ranking, dispatch, or contractor recommendations.