← EvidenceSupporting record: dated activity & continuous review

Evidence activity

Living evidence systems.
Not static websites.

Collection is automated where appropriate. Verification, human judgement, protected review and repeatable comparison remain part of the operating model.

Recurring automationHuman reviewVersioned evidencePublic + protected
Repeat
CollectValidateCompareReviewSeparateArchive

Continuous evidence cycle

Every run should leave the next run something trustworthy to compare.

01Collectscheduled source retrieval
02Validateintegrity & completeness gates
03Comparesuccessive evidence states
04Reviewhuman judgement where required
05Separatepublic vs protected material
06Archiveretain release evidence

Current operating picture

Different cadences. One evidence discipline.

Dates and figures are tied to the stated release or review period — never presented as permanently live facts.

Companies House IntelligenceRecurring national-scale review
Public redacted + protected review
Air Quality ObservatoryWeekly evidence cycle
Validation gated + protected review
Vaping26Active research
Re-checkable evidence pipeline
UK Fusion EvidenceActive research observatory
Human verification required
SCC StocksOperational research service
Risk gates + human review
LewesLiveOperational local platform
Validated upstream publication
Local Events EngineReusable infrastructure
544 confirmed test functions
Local Directory EngineDeveloping infrastructure
Public/private boundary

Why the protected layer matters

Redaction is a governance control, not missing evidence.

Some analytical artefacts are unsuitable for unrestricted publication because they contain sensitive, unresolved, implementation-specific or unredacted material. Mature SCC Nexus projects can therefore preserve fuller review evidence while publishing only what has passed the appropriate public gate.

That separation is part of the integrity architecture.

See provenance, integrity, verification & validity →