Display compliance
The kit's IDX/VOW controls fail closed by design. What they enforce, what they cannot, and what you must review before publishing listings.
Frontstead Kit provides technical controls for handling MLS data. Each MLS board and data agreement defines its own display, attribution, retention, and security requirements.
This page is an implementation framework. It is not legal advice, and it is not approval to publish listing data.
The safe default
Keep both flags off until you have reviewed the current agreement and verified every public read path for each enabled board:
MLS_SYNC_ENABLED=falseMLS_PUBLIC_DISPLAY_ENABLED=falseCompose and the checked-in worker environment example both use these values. Direct process deployments must set and verify the effective values explicitly — a flag you never set is not the same as a flag you verified.
The enforcement boundary
MLS_PUBLIC_DISPLAY_ENABLED must have the same effective value in the API and the MLS worker. They enforce different halves of the same rule:
- The API applies it to public PostgreSQL listing predicates, Typesense filters and scoped keys, property details, media, suggestions, collections, featured listings, and portal readiness.
- The worker applies it to media processing and property-document reconciliation.
Existing Property.media rows do not carry listing provenance. While MLS display is disabled, public responses therefore suppress shared property media conservatively; eligible non-MLS Listing.imageUrl values remain available.
Flags do not rewrite your search index
Changing the environment flag does not rewrite documents already stored in Typesense. Run the exact property reindex after every policy transition or schema upgrade, before restoring public traffic:
POST /api/search/reindex/propertiesThis is the step most likely to be forgotten, and the failure mode is listings remaining publicly searchable after you believed you had turned them off.
What you must review before launch
Confirm and document each of these. The kit cannot determine any of them for you:
- authoritative display opt-in and opt-out fields
- IDX versus VOW eligibility differences
- required disclaimer and attribution text, and its placement
- address-display restrictions
- fields that must not be exposed publicly
- media display, copying, retention, and removal rules
- sold, withdrawn, expired, and deleted listing timelines
- staging and non-production replication restrictions
- refresh frequency and outage obligations
- reviewer, agreement version, evidence, and approval date
Store board-specific agreements, legal review, and sign-off evidence outside the public repository.
Technical controls to verify
Provider adapters map board rules into normalized eligibility fields. The public API and search paths enforce eligibility independently of UI behaviour, and raw provider records are never returned by public endpoints.
At minimum, verify that:
- non-displayable listings stay excluded from public PostgreSQL and Typesense results
- manual inclusion cannot bypass MLS or account eligibility
- removing public-display permission withdraws affected documents
- required attribution fields are present before rendering
- media storage and deletion follow the approved policy
- logs and errors do not expose credentials or restricted raw records
Operations
| Action | Effect |
|---|---|
MLS_SYNC_ENABLED=false |
Stops new worker ingestion. Does not hide data already stored or indexed |
MLS_PUBLIC_DISPLAY_ENABLED=false |
Excludes MLS-sourced listings from API and search results, preserving eligible non-MLS listings |
POST /api/search/reindex/properties |
Removes stale Typesense documents after a flag change |
Disable public traffic during a policy transition until PostgreSQL and Typesense verification passes. Re-run the display verification suite after provider mapping or agreement changes.
Why it fails closed
An unregistered MLS board fails loud at config load rather than defaulting to "no attribution required." Every display gate defaults to off. Both choices cost you a deliberate step at launch, and both exist because the failure they prevent is a licensing violation rather than a rendering bug.
If you would like help working through board approval, see Pro — the kit's own SUPPORT.md is explicit that maintainers cannot provide brokerage compliance or MLS onboarding support through the issue tracker.
Next
Deploying — containers and platform specifics.