Helpful questions, not unsafe conclusions
Trust readiness means every customer-facing packet/report section has a source basis, caveat, review status, and clear blocked-claim boundary.
The reusable DoorFrame trust boundary for Property Watch packets, source labels, privacy, production lock, subscription billing scope, and blocked authority claims.
DoorFrame should feel useful because the boundary is clear, not because it overclaims.
Trust readiness means every customer-facing packet/report section has a source basis, caveat, review status, and clear blocked-claim boundary.
Submitted info, reviewed source context, and questions to ask.
Authority, provider selection, and raw-source conclusions stay blocked.
Authenticated, reviewed-only, read-only packets.
Subscriptions allowed; marketplace money blocked.
This is the can-say and cannot-conclude contract for the unified surface: useful questions, reviewed evidence, privacy, and locked unsafe claims.
The same language should be reused by report previews, source appendix rows, action cards, and customer workspace states.
DoorFrame can organize what the customer submitted: watched address, property label, selected source modules, quote/work text if provided, timeline, concern, files/links metadata, and consent.
DoorFrame can show source labels, checked dates, caveats, freshness posture, normalized summaries, and customer-display decisions after review.
DoorFrame can turn evidence gaps into careful questions, action cards, missing-data notes, source caveats, and next steps.
DoorFrame cannot conclude legal, safety, compliance, appraisal, insurance, tax, fair-price, permit-required, provider-quality, recommendation, ranking, dispatch, or guarantee claims.
DoorFrame cannot verify, approve, rank, recommend, match, contact, or dispatch providers from customer reports or quality signals.
DoorFrame cannot show raw API/public-source output directly to customers or treat public/context records as a current-condition conclusion.
Property Watch packets and report previews stay authenticated, owner-scoped, reviewed-only, and read-only. Raw admin notes, raw API output, and private metadata stay hidden unless approved in customer-safe wording.
Production remains locked until a separate production promotion gate passes with explicit human approval.
Stripe subscriptions are allowed only for DoorFrame data products. Provider payouts, Stripe Connect, escrow, dispatch payments, marketplace fees, refunds automation, and production revenue recognition stay blocked.
Trust posture is a product feature: it tells the customer what DoorFrame can safely help with and where it must stop.
This is the compact boundary pattern other pages should reuse instead of rewriting trust language route by route.