Handout / ros-field-handoutResearch note

ROS in the Field

One research state, three device roles.

A brief handout distinguishing analysis, field reading and navigation, and describing the field guide lifecycle.

  • ROS
  • handout
  • artifact lifecycle
01

Intent

Research must be usable in the field without turning a reading device into a second, contradictory knowledge store.

02

Analysis Device

Registers, sources, hypotheses, Markdown views and manifests reside here. New observations are assessed and revisions made here.

03

Field Reader

It holds an approved static PDF snapshot. Its build ID and reference date indicate provenance; the file may be replaced upon a new release.

04

Navigation Device

It receives suitable geospatial exports separately. A field sketch or schematic line thereby does not become surveyed geometry.

05

Update

New evidence changes the Research State. This is followed by regenerating the view, approval, PDF build and visual review. PDF modifications are not imported back into ROS.

06

Control Question

Before use, check: which ResearchUnit does this output belong to? Which build and reference time does it represent? Have critical states become outdated?

07

COMPACT: Focused Field Research

COMPACT_URBAN, COMPACT_EXTRA_URBAN and COMPACT_TECHNICAL retain the pure field-guide pathways. Sources, observations, states, open questions and FieldObservationPoints remain canonical. Hypotheses, graph closure and signal/index analysis are not automatically mandatory. Promotion to FULL adds records while preserving existing UIDs.