A review is bounded
Every review names the Program, date, review type and scope actually covered. What was not observed is never inferred.
FIELD REVIEW / WORKING PROTOCOL V0.1
State only what was actually reviewed
Field Review is an independent record with a date, scope, attribution and limitations. It is distinct from operator statements, editorial verification and Program transparency, and is not safety certification, endorsement or a guarantee of continuing operations.
Observation stays distinct
A record first describes what was seen, heard or inspected, then states scope and uncertainty. A field record does not become a quality conclusion.
Limitations remain public
Visit duration, sample limits, inaccessible areas, seasonal differences and operational change remain attached to the public summary.
From permission to public summary
- 01
Pre-review
Confirm canonical Program and operator identity, permission, scope, privacy arrangements and independence disclosures; turn transparency gaps into a question plan.
- 02
Operator interview
Ask about purpose, fit, activities, daily rhythm, roles, supervision, preparation, change and emergency processes; interview content remains Operator stated.
- 03
Documentation review
Record document title, owner, date or version, permitted use and supported claim; a document’s existence does not establish implementation.
- 04
Site or Program observation
Observe only the authorized scope, avoid intrusive monitoring, and do not extend one observation to unobserved sessions or future operations.
- 05
Field Notes
Separate factual observation, interpretation and uncertainty; raw notes remain anonymized inside the protected workspace.
- 06
Post-review clarification
Reconcile conflicting dates, claims or terms with sources and the operator, record unresolved points, and retain provenance for new claims.
- 07
Internal review
A human checks scope, privacy, sources, conflicts, limitations, public findings and every media reference; AI cannot approve findings or transitions.
- 08
Public review summary
An Editor or Admin approves only the strict public projection: dates, scope, methods, exclusions, limitations and attribution—never raw notes or a whole-Program conclusion.
Minimum public record
- Review type
- States whether the work was a site visit, document review, interview or another defined review type.
- Completion date
- Shows when the protocol was completed; a past review does not automatically describe current operations.
- Scope
- Lists only places, processes, documents or activities actually covered.
- Limitations
- States what was not covered, could not be accessed or may have changed over time.
- Reviewer attribution
- Identifies who completed the record and in what role, without manufacturing anonymous authority.
- Not conducted
- Shown explicitly when no formal review is complete; absence of a record never means a pass.