ROS / Nea Polis

Artifacts & Publication Process

From canonical research state to analyses, field guides, handouts and replaceable reader PDFs.

Format is not identity: a logical field guide can have several immutable builds. Canonical registers, released views and device snapshots serve different purposes.

Canonical state / Analysis tool

Canonical Registers

Structured sources, entities, evidence, hypotheses and states. This is where research and revisions are maintained.

JSON · JSONL · YAML · GeoJSON

No original download in this site edition.

Derived output / Analysis / Review

Research, Analyses & Assessments

Baselines, compiled masters and thematic analyses make the research state readable. Their claims remain tied to registers, sources and open questions.

Markdown · HTML

Derived output / Fieldwork

Field Guides

Approved location-specific views of visible features, system transitions and open observation questions. COMPACT retains urban, extra-urban and technical profiles with FieldObservationPoints; later FULL promotion preserves existing identities.

Markdown · HTML

Derived output / Offline reading device

Field-Reader PDF

Replaceable static snapshot with build ID, temporal baseline and release reference. PDF changes are not merged back into ROS. The original reader PDFs are not included in this website bundle.

PDF

No original download in this site edition.

Derived output / Navigation device

Navigation & Geospatial Outputs

Task-specific spatial exports with provenance, temporal validity and geometry quality. Surveyed, schematic and reconstructed geometries must be distinguished.

GPX · CSV · GeoJSON

No original download in this site edition.

From revision to verified snapshot

  1. 01

    Update Research State

    Capture new observations, reference sources and review hypotheses and temporal baselines.

  2. 02

    Generate Readable View

    Derive a baseline, master document, field guide or handout from the defined research state.

  3. 03

    Review Quality & Approve

    Check references, scope, evidence status and currency; document approval.

  4. 04

    Generate Build

    Select format and device profile; record the input fingerprint and immutable build ID.

  5. 05

    Review Output

    Check structure, readability, embedded resources and device-specific limitations.

  6. 06

    Deliver Snapshot

    Replace the reader file in a controlled manner. With new evidence, the chain restarts from the canonical state.

PDF → ROS is not a return channel. New evidence is processed in the canonical model; outputs are then rebuilt. A new date alone does not prove currency.