Provenance
Outputs are separated into internal-audit, public-build, LewesLive-import and test-review surfaces, preserving the distinction between discovered records and publishable records.
Reusable infrastructure
Local Events Engine
Reusable event discovery, validation, enrichment and publication infrastructure for local information services.
Public proof without exposing private operations
Local Events Engine
The public synopsis is backed by a confirmed repository test inventory of 544 test functions and a fail-closed public-build design that can withhold output when quality gates fail.
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 location-independent event-data engine that can discover and prepare public event information for different websites without rebuilding the workflow for every place.
Intended outcomes
What success looks like.
- Reusable event records across locations.
- Validation before public publication.
- Source-aware data and maintenance signals.
- A bounded public feed separate from private collection methods.
Evidence status
Provenance · integrity · verification · validity
Integrity
The public-build validator forbids sensitive/binary material; title blocklists, provenance requirements, enrichment flags and source-health reporting are used as publication gates.
Verification
The repository was confirmed with 544 test functions. Public builds have been withheld when quality gates fail rather than publishing incomplete output.
Validity
Valid for discovery, normalisation and publication preparation of public event information. Discovery does not guarantee an event is current, genuine or publication-safe until validation passes.
Evidence record: Engineering review 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.