Provenance
The design is provenance-aware: listing discovery is intended to preserve where a business/service record came from and separate source material from public presentation.
Reusable infrastructure
Local Directory Engine
A provenance-aware approach to discovering, normalising, reviewing and maintaining local businesses, services, amenities and public-interest listings.
Public proof without exposing private operations
Local Directory Engine
This project is intentionally labelled developing infrastructure. Its current public verification is architectural rather than a claim of a complete or independently validated national directory.
Credentials, source-specific collection tactics and security-sensitive implementation details remain private by design. The public evidence claim is therefore bounded to what can actually be demonstrated safely.
Open status & verification record →Purpose
What it is trying to create.
Create a reusable directory layer that reduces stale, duplicated and inconsistent listings while keeping source context and review controls.
Intended outcomes
What success looks like.
- Reusable structured listings.
- Normalisation and duplicate reduction.
- Source-aware maintenance and review.
- Public outputs that conceal operational secrets and restricted implementation details.
Evidence status
Provenance · integrity · verification · validity
Integrity
Private implementation details, credentials and source-specific collection tactics are deliberately separated from the bounded public synopsis and output layer.
Verification
Current verification is primarily architectural and public-surface based; the site does not claim an independently validated national directory or authoritative registry.
Validity
Valid as developing infrastructure for local listing discovery, normalisation and maintenance. Public records still require source-aware review and are not statutory or exhaustive.
Evidence record: Public synopsis reviewed August 2026
Public boundary
Transparency without exposing operational secrets.
Public pages describe purpose, evidence principles and intended outputs. Credentials, private repository links, source-specific collection tactics, restricted implementation details, anti-abuse controls and other security-sensitive material are deliberately excluded.