r365 Trust Hub

This is the starting point for anyone assessing whether r365 is trustworthy enough for their household, client, or regulatory context. These pages describe the implementation and its limitations. The source code is private; these public documents do not grant access to it.

---

Start here

System card — what r365 is, what it is not, the five rules that govern it, how every number is computed, what the engine cannot do, and the privacy model. The limitations section is intentionally generous.

Certificate explainer — what a sealed certificate contains, how a plan is independently reproduced, and what each verdict (REPRODUCED / ENVIRONMENT MISMATCH / NOT REPRODUCED / SEAL BROKEN) means.

Evidence dossier — every registered clinical and nutritional rule, its source and its review status.

Design decision: no AI model at serving time — why planning, adaptation and certificates never call a language model.

Honesty benchmark: not yet published.

---

Data and methods

Data provenance — what was inherited from Regional 365’s verification rituals, what was created new, and the verification state of each data set — and the design decisions behind the engine are documented internally. The system card summarises them, including the 2022 re-check against the Swiss federal reference values and the 2026 allergen re-adjudication.

---

Data sources

Nutrient values come mainly from the Swiss Food Composition Database, Federal Food Safety and Veterinary Office FSVO, naehrwertdaten.ch1, completed from USDA FoodData Central. Climate figures come from ADEME – AGRIBALYSE 3.2 (Licence Ouverte / Open Licence 2.0) and AYCE-earth (Eaternity). Allergen evidence contains information from Open Food Facts (ODbL). Targets and limits follow the FSVO and D-A-CH reference values and EFSA upper limits. Data sources gives each credit in full, with licence and update date, in all four languages.

---

Regulatory posture

r365 is a meal-planning tool. It is not a medical device and does not provide medical advice. The legal opinion on the intended purpose under the EU Medical Device Regulation and the Swiss Medical Devices Ordinance is a go/no-go gate before any public launch. The data protection impact assessment under the Swiss Federal Act on Data Protection is a parallel gate. See the system card’s limitations section for the full list of what is not yet in place.

The consent text is still a placeholder and must be replaced with reviewed wording before public launch; the placeholder itself does not prevent signup.

---

Verification scope

These public documents explain how r365 works; its source is private. Automated checks — linting, strict type checks and the full test suite — must pass before any change ships. This trust hub never claims ahead of them.