Quality means honest blockers
DoorFrame should make weak evidence visible as missing, stale, conflicting, sensitive, blocked, or not-displayable instead of smoothing it into a confident report.
Founder Ops
Evidence Quality Hub
A read-only quality posture surface for the first report loop. It shows what evidence can block preview readiness without claiming legal, safety, compliance, price, or provider-quality authority.
PostureReview gate
EvidenceSource-labeled
AuthorityNot claimed
IngestionBlocked
Quality Command
Use this page to see the evidence states that should create visible blockers before customer preview.
Evidence posture categories for report readiness.
No legal, safety, compliance, price, or provider-quality conclusions.
No raw public-source or API output appears here.
Every section needs evidence or an explicit missing-data reason.
Evidence quality is not authority. It keeps weak evidence visible so DoorFrame avoids unsafe conclusions before customer preview.
Evidence Quality Signals
These are review signals. They do not prove that a condition, violation, price, provider, permit, or safety conclusion is true.
A report section should not appear complete when the client input, source snapshot, admin note, action card, or missing-data reason is absent.
Supported use: create a visible missing-data blocker or follow-up question.Source snapshots need checked dates and freshness caveats before they support customer-facing source appendix rows.
Supported use: source freshness caveat, not a current-condition conclusion.When submitted context and public/context source labels disagree, DoorFrame should show the conflict as a question.
Supported use: action card or admin review queue item.Private details, raw source output, private admin notes, and hidden payloads stay internal unless explicitly customer-approved.
Supported use: customer-safe summary or blocked display decision.Unsafe, unsupported, or not-reviewed evidence should block preview language instead of becoming a confident report section.
Supported use: report-not-ready state and founder/admin review.A source may help internal review while still being inappropriate for customer display.
Supported use: source appendix omission with customer-safe missing-data language.Quality States
Quality language stays aligned with source snapshots, report readiness, and blocked-claim boundaries.
Allowed nowShow source/data-quality posture, blocker categories, missing-data reasons, and source-display readiness.
Blocked behaviorNo live ingestion, scraping, browser-direct public-record calls, customer-facing AI, database writes, automated delivery, public reports, production behavior, or raw API/customer display.
Not authorityQuality signals create review work and customer-safe questions; they do not conclude compliance, safety, legal status, fair price, permit requirement, or provider quality.
Quality Boundary
The hub is useful because it says when DoorFrame should slow down.
Source CheckedHuman Reviewed
- DoorFrame can organize submitted information, reviewed source/context checks, missing data, caveats, and questions to ask.
- DoorFrame can show whether evidence is missing, stale, conflicting, sensitive, blocked, or not displayable.
- DoorFrame can turn weak evidence into data-quality issues, action-card questions, caveats, or report-not-ready states.
- DoorFrame cannot make legal, safety, compliance, appraisal, insurance, tax, fair-price, provider-quality, recommendation, ranking, dispatch, or guarantee conclusions.
- DoorFrame cannot treat quality posture as legal, safety, compliance, permit, appraisal, insurance, tax, fair-price, or provider-quality proof.
- DoorFrame cannot recommend, rank, verify, approve, match, dispatch, or contact providers from these signals.