Nea Polis / Research & Knowledge
Nea Polis is at the heart of kalina.labs: the integrated system of ROS, BIS and NIS. Research and local AI workflows connect questions, sources, analysis and verifiable results.
SYSTEM / 01 ROS and BIS are coupled. NIS extends ROS as a domain module.
Nea Polis is the main focus. Research provides methods and results; AI & Knowledge develops controlled processing for them. Small software tools are developed alongside for personal use or as proofs of concept.
The overall system
Shared rules for identity, provenance, time, relationships and artifacts link the components. Their domain models and version statuses remain independent.
Research Operating System
Research questions, substrate, evidence, hypotheses and iteration. ROS 1.7.2 extends causal and canonical research architecture with context-dependent process diagrams bound to source states; MODE, domain scope and diagram semantics remain distinct.
State 1.7.2 · Documented state
Explore componentIndependent coupled system
OrganizationArchetype, applicability, metrics, roles, lineage and economic relationships. Shared meta-kernel, separate domain semantics; version remains 0.3.1.
State 0.3.1 · Active
Explore componentDomain module within ROS
Events, information spaces, SARM integrity sensors and time series within the shared ROS Research State. The Speculative Layer and Narrative Delta are documented separately as a methodological decision.
State Migration 1.0 · SARM 1.1 / RC1 · Experimental
Explore componentEvidence over claims
Three works connecting method, analysis and technical infrastructure.
Persistent, traceable and revisable Research State. ROS 1.7.2 adds context-dependent process diagrams bound to source projections, with SVG/text alternatives and separate semantic/artifact checks, to causal coverage and canonical projection.
Explore systemA thought-laboratory corpus of 14 German-language essays originating in 2024 was transformed using ROS into hypotheses, evidence runs, negative findings and explicit validation statuses.
Open researchLocal-first prototype featuring task normalization, model routing, worker roles, a critic and validated delivery contracts.
View case studyOperating model
A repeatable sequence instead of an invisible creative leap.
Record the phenomenon, system boundary and open question.
Stabilize terminology, sources, units and temporal reference points.
Make dependencies, constraints and feedback explicit.
Test language syntax, browser APIs, layout and actual device behavior separately; technical consistency does not constitute empirical model validation.
Feed findings back across projects and domains.
Preserve originals, derive editorial editions and govern access separately; do not backdate missing research provenance.
Versioned output
Cross-reference
Methods, tools and publications are connected. The graph makes their dependencies visible.
