Public Observatory hardened
The public presentation was rebuilt around evidence status, falsifiability, accessible navigation and the one-way publication boundary, without adding unsupported scientific claims.
SCC Nexus · Research Observatory
UPF26 tests whether a single ultra-processed-food category conceals meaningful differences between packaged foods. Evidence, rules, classification, composition and reviewer judgement remain separate so uncertainty stays visible.
Current status
UPF26 is currently a methodology and evidence infrastructure project. The public dashboard distinguishes readiness from findings and refuses to turn incomplete evidence into apparent certainty.
Prospective pilot
The pilot is designed around deliberately difficult boundaries rather than a convenient sample. Case 0001, which motivated the project, is excluded from the prospective endpoint because it influenced methodology design.
The project continues only if the richer dimensions are reproducible and materially informative.
| Criterion | Threshold |
|---|---|
| Complete auditable evidence trails | ≥18/20 |
| Exact blinded reviewer agreements | ≥16/20 |
| Confirmed material-discordance cases | ≥4/20 |
| Different discordance types | ≥2 |
| Unexplained rule conflicts | ≤2 |
Methodological architecture
UPF26 keeps source evidence, transcription, deterministic rule firing, classification and human review distinct. Ambiguity is an output state, not a reason to invent a confidence percentage.
Source material and transcribed facts remain traceable so later judgements can be audited back to the underlying evidence.
Versioned rules can emit NOVA 1–4, unresolved 3/4, rule conflict or insufficient evidence. Determinative conflicts fail closed.
Two reviewers assess the same locked evidence and methodology independently. Reconciliation creates a new record and does not overwrite either review.
evidence completenesstranscription certaintyrule determinacyreview state remain a vector rather than being collapsed into a single confidence score.
Live public evidence
Automated daily, weekly and monthly bibliographic snapshots are available with retrieval, screening, source-error and provenance fields. They are discovery records, not peer-reviewed synthesis or formal pilot findings.
Read prospective endpoints, stop/go criteria, unresolved submission blockers and the distinction between methods and empirical results.
Inspect published daily, weekly and monthly screened-in records, archived snapshots and explicit source-quality caveats.
Discuss possible technical and research partnerships without disclosing private evidence, partner details or unvalidated claims.
Project record
Public evidence monitoring is operational; the prospective pilot, manuscript author declarations, method freeze and independent scientific review remain open tasks.
The public presentation was rebuilt around evidence status, falsifiability, accessible navigation and the one-way publication boundary, without adding unsupported scientific claims.
The public repository became a publication surface only. Private working records remain in the research source; approved output is copied after validation.
Protocol, append-only schema, deterministic engine, blinded-review model, adversarial pilot registry, stop/go analysis, tests and CI were established.
Affiliation
UPF26 is developed within SCC Nexus: Search · Corroborate · Communicate. Methodological challenge, corrections and research collaboration are welcome.
Use the same canonical route for general enquiries, research collaboration, corrections, provenance amendments, privacy and accessibility.
| Purpose | Route |
|---|---|
| General / collaboration | hello@sccnexus.co.uk |
| Correction / provenance | hello@sccnexus.co.uk |
| Privacy / accessibility | hello@sccnexus.co.uk |
For corrections, identify the page or case, the statement or data point, the proposed amendment and the strongest available source.