ROS / Nea Polis

Architecture & Research Model

Identity, provenance, evidence and time form the foundation; an optional systems lens adds topology, states, flows and feedback loops.

Execution modes: COMPACT & FULL

AUTO selects the mode; COMPACT retains the field-guide mode, while FULL serves systematic research. In current usage these execution modes are called MODE. Domain scope (such as architecture) and method_profile (such as system_reading) are separate axes. The historically named scope profiles remain compatible.

COMPACT

COMPACT_URBAN
Urban · Urban structure, historical layers, architecture, material condition, infrastructure and field survey strategy.
COMPACT_EXTRA_URBAN
Extra-urban · Terrain, geology, hydrology, vegetation, interventions, accessibility and field observations.
COMPACT_TECHNICAL
Technical · Motivation, design, functional roles, physics, operation, safety and lifecycle of a technical system.

FULL

FULL_GENERAL
General Research · Evidenced source substrate, systematic analysis, hypotheses, countermodels and traceable research iteration; modules and gates selected by scope.
FULL_NIS
News Intelligence · Time-series event and information analysis in the shared research state, with signal/index layer, SARM integrity checks and separately maintained speculative claims.

COMPACT does not automatically require hypotheses, countermodels, graph closure, adversarial analysis, signal/index analysis or ResearchIteration chains. Sources, observations, states, open questions and FieldObservationPoints remain traceable; inapplicable gates are not errors.

UID-stable promotion

ROS@latest → ROS@v1.7.2 according to the global resolver and ROS Bridge. NIS/SARM 1.1 RC1 adopts the applicable core, while BIS 0.3.1 and NP-SIC 1.0.0 remain unchanged. New snapshots and ArtifactBuilds use the internal ROS schema 1.7.2; historical 1.7.1 pins/bytes are preserved and expanded only through explicit migration. Diagrams bind to the upstream source projection, not the state hash produced after they are added. Promotion does not prove native event replay or production adapters.

ROS — research model layersCommon Meta-Kernel; Canonical Research State; Systems, Space & Time; Optional Dynamic Systems & Network Lens; Causal Coverage & Feasibility; Intervention & Feedback; Canonical Projection & Register Integrity; Conditional Process Flowcharts & Semantic Review; Approval & Delivery. Detailed descriptions are available under Architecture.01Common Meta-Kernel02Canonical Research State03Systems, Space & Time04Optional Dynamic Systems & Network Lens05Causal Coverage & Feasibility06Intervention & Feedback07Canonical Projection & Register Integrity08Conditional Process Flowcharts & Semantic Review09Approval & Delivery
  1. Common Meta-Kernel
  2. Canonical Research State
  3. Systems, Space & Time
  4. Optional Dynamic Systems & Network Lens
  5. Causal Coverage & Feasibility
  6. Intervention & Feedback
  7. Canonical Projection & Register Integrity
  8. Conditional Process Flowcharts & Semantic Review
  9. Approval & Delivery

Layer 01

Common Meta-Kernel

Shared rules for identity, provenance, time, relationships and artifacts underpin ROS and the separate BIS. SourceOrigin, SourcePerspectiveProfile and knowledge_time add source locations and source independence.

  • UID / Source / SourceLocator
  • SourceOrigin / SourcePerspectiveProfile
  • knowledge_time / CrossReference

Layer 02

Canonical Research State

ResearchQuestion and CollectionScope define the task. SubstrateAssembly organizes the substantiated source material; claims, constraints, mechanisms and hypotheses remain distinct. ResearchIteration preserves the path by which findings emerged. COMPACT omits unnecessary FULL obligations. Predictions, falsifiers, negative evidence and validation close the empirical revision loop; Ontology Diversity tests alternative descriptive frameworks.

  • ResearchQuestion / CollectionScope
  • SubstrateAssembly / ResearchIteration
  • Claim / Hypothesis / Countermodel
  • Prediction / Falsifier / Validation

Layer 03

Systems, Space & Time

ResearchUnit, System, Subsystem and Component define the scope. Weighted coverage prevents a well-documented part from standing in for a comprehensively studied overall system. Time-valid geometries and operational states distinguish planned, historical and current conditions.

  • ResearchUnit → System → Subsystem
  • OperationalState / valid_time
  • SpatialAssertion / MaterialCondition

Layer 04

Optional Dynamic Systems & Network Lens

Following a positive Applicability Gate, ROS can describe a system as S=(G,X,F,U,D,Θ,P): topology, states, flows, exogenous inputs, delays, time scales and observation projection. LEVEL 0–3 ranges from implicit to formal/numerical. The lens is optional and does not impose a mandatory graph on existing research objects.

  • Applicability Gate / LEVEL 0–3
  • G / X / F / U / D / Θ / P
  • Topology change / State transition / Feedback
  • Domain-System Graph ≠ Epistemic Research Graph

Layer 05

Causal Coverage & Feasibility

CausalCoverageAudit checks material drivers, countermodels and scope boundaries. ConstraintEvaluation and FeasibilityAssessment operationalize HARD/SOFT/UNKNOWN; CausalIdentification records claim-specific levels M0–M4, while ImpactLedger records countervailing effects.

  • causal_coverage_audit
  • constraint_evaluation / feasibility_assessment
  • causal_identification / impact_ledger

Layer 06

Intervention & Feedback

Intervention and Monitoring connect states with observed effects. ActorGraph and AdversarialAssessment add adversarial scrutiny. The signal/index layer preserves raw data, time windows and derivation provenance; NIS uses the same research state.

  • Intervention / MonitoringSeries
  • ActorGraph / AdversarialAssessment
  • Signal / Index / DerivationEdge

Layer 07

Canonical Projection & Register Integrity

Immutable EventHistory → one active MaterializedResearchState → complete CanonicalRegisters → ArtifactBuild. QG-RS-01 checks references, IDs, prediction immutability and fingerprints; QG-RT-01 prevents unreviewed acceptance of adversarial criticism. The website data model is an editorial view, not a ROS engine.

  • state_projection / register_integrity_assessment
  • QG-RS-01 / QG-RT-01
  • projection_seq / event_head_hash / canonical_fingerprint

Layer 08

Conditional Process Flowcharts & Semantic Review

ROS 1.7.2 adds an applicability decision, a typed process specification and a versioned SVG/text build derived from an upstream source projection. QG-FC-01..04 check materiality, derivation, semantics and artifact quality. Process graphs, domain-system graphs and epistemic research graphs remain distinct; diagrams create no new evidence.

  • FlowchartApplicabilityAssessment
  • FlowchartSpec / FlowchartBuild
  • QG-FC-01..04 / QG-AR-01

Layer 09

Approval & Delivery

Logical artifacts and immutable builds remain separate. Manifests, input fingerprints, temporal baselines and quality states make it traceable which research state produced an output.

  • Artifact / ArtifactBuild
  • Fingerprint / Manifest
  • Freshness / Release

Explore methods in depth

MethodDocumented state

Research Operating System

ROS makes the research process traceable: research questions and collection lead to a documented substrate from which analysis, hypotheses and iterations emerge. ROS 1.7.2 adds context-dependent process diagrams bound to the source state to the consolidated Research State, with separate semantic and artifact checks.

v1.7.2
Open method
MethodActive method

Substrate-Based Hypothesis Formation

Explanations begin with what a system must materially sustain: resources, energy, geometry, tools, logistics, labor and institutional capacity. Narrative interpretations are only then tested against this substrate.

v1.0
Open method