TRUST / PUBLIC METHOD

How we handle Program information

We do not compress trust into stars, quality scores or safety badges. Provenance and verification explain how we know; transparency explains what families can currently understand; Field Review explains what was actually reviewed or observed during a defined period.

01

Operator stated

Facts and explanations from an authorized Program representative keep their source label. A submission does not enter the public record until editorial review and publication.

02

Source confirmed

SUMMERCAMP checks a specific field against a current, traceable official or authoritative public source. A source supports only what it actually states.

03

SUMMERCAMP classification

Ontology classifications such as activity, environment, challenge and learning intention remain editorially independent. Operators may supply facts but cannot publish editorial judgment.

METHOD / 01

From information to public record

  1. 01

    Information arrives

    Founder field records, public research, official sources and operator submissions retain their own source identity.

  2. 02

    Fields are reviewed

    Editors compare current value, proposed value, evidence and limitations field by field instead of assigning a mysterious Program score.

  3. 03

    Canonical publication

    Only accepted fields enter the canonical Program record. Discovery, Advisor, Search and public exports read that published version only.

  4. 04

    Ongoing maintenance

    Operator-confirmation and editorial-review dates remain separate. Stale information enters a review queue; it is not automatically treated as false.

METHOD / 02

Unknowns, conflicts and scope

Unknown
Missing information remains unknown. It does not mean no, low risk or unsuitable.
Source conflict
When operator and public sources disagree, we record the conflict and compare freshness and scope. If unresolved, the public record expresses uncertainty.
Field record
Contextual first-hand observations may be field evidence, but are not called a ‘Field Review’ before a formal protocol is completed. Founder connection never raises status automatically.
Risk information
We may explain whether risk-management information is unknown, limited, available or reviewed. We do not provide a safety rating or guarantee future outcomes.
Program transparency
Ten domains show what information is available, partial or not yet available. They are not a quality, safety or compliance score.
Field Review
Describes only a review actually completed with a published date, scope and limitations. When none occurred, the record says not conducted.