Reference application
A documented methodological ROS case: clarify the system boundary, correct unequal terminal states, distinguish conclusions by definition from dynamical proof and make unknowns visible.
ROS v1.7.2 FULL ANALYZE, M0.6.7 baseline, assessment as of October 15, 2026. An editorial continuation dated October 16 separates the later M1a.0.2 specification.
Trace the applicationReference application
The case shows how ROS separates platform classes, physical principles, competing explanations and unverified effects—and why the assessment process itself needs a verified branching representation.
Conditional ROS FULL application using Dynamic Systems & Network Lens, LEVEL 2 and an explicit historical ROS@v1.7.2-TESTBASE pin dated October 15, 2026.
Trace the applicationReference application
The case connects political-economic analysis with failure memory: material and legal constraints, countermodels and register errors lead to concrete methodological and implementation rules.
Historical ROS FULL case with a ROS 1.6.1 baseline; adversarial revision 1.1 dated October 10, 2026 and subsequent methodological revision through 1.7.1.
Trace the applicationReference application
City, port, karst and tram are considered as interconnected, hierarchical systems—not a loose collection of tourist attractions.
Documented migration of a reference ResearchUnit to ROS 1.2.0.
Trace the applicationReference application
The Danube, terraces, settlement development, flooding, logistics and structural interventions form a counterexample to the strongly technology-focused Trieste reference.
Documented native ROS 1.2.0 ResearchUnit in FULL scope.
Trace the applicationReference application
Ling_Evo illustrates how ROS turns exploratory essays into a provenance-preserving, falsifiable and differentiatedly validated research state.
ROS FULL reconstruction of a thought-laboratory corpus created in 2024; documented research state rev1.6.
Trace the application